atom feed14 messages in org.kernel.vger.linux-btrfsdefault subvolume abilities/restrictions
FromSent OnAttachments
C Anthony RisingerMay 18, 2010 11:50 pm 
krei...@libero.itMay 19, 2010 4:56 am 
C Anthony RisingerMay 19, 2010 7:01 am 
Chris BallMay 19, 2010 7:20 am 
C Anthony RisingerMay 19, 2010 7:54 am 
Goffredo BaroncelliMay 19, 2010 10:57 am 
C Anthony RisingerJun 11, 2010 10:24 pm 
C Anthony RisingerJun 12, 2010 4:06 pm 
David BrownJun 12, 2010 5:22 pm 
C Anthony RisingerJun 12, 2010 6:06 pm 
C Anthony RisingerJun 13, 2010 10:46 am 
C Anthony RisingerJun 18, 2010 2:01 pm 
Hubert KarioJun 29, 2010 6:20 am 
Goffredo BaroncelliJun 29, 2010 8:23 am 
Subject:default subvolume abilities/restrictions
From:C Anthony Risinger (anth@extof.me)
Date:May 18, 2010 11:50:08 pm
List:org.kernel.vger.linux-btrfs

hi,

i'm working on an initrd hook [http://aur.archlinux.org/packages.php?ID=33376] to support non-volatile system rollbacks (promoting a temporary rollback snapshot to the new active/default). when the system is installed to the default/"." subvolume (as many users probably initially do), it is more difficult/messier to manage system state; there are empty folders in each "child" snapshot where a subvolume used to exist (this seems like BUG to me, dir should not exist?) in the default subvolume. these grow/vary with time. to work around this and for cleaner implementation, i'll intend to permanently boot a named subvolume [__active] (though its contents may be swapped out). ultimately, i have to tell the user to manually remove the old junk (/usr, /etc, /var, etc...) from the default subvolume (since its really in the /__active subvolume)

moving along to a question... can the default subvolume be swapped/removed/renamed/popped/shifted?

what would have been useful, would be the ability to generate an empty, parent subvolume to _contain_ the current one, and rename it to __active. btrfs gives rise to a "subroot" structure; the structure beneath the root.

is something like this possible or can be added?

an alternative idea i had was "promoting" a subvolume to be the new root, and anything "above" the new root is lost/forgotten. then i could create the subroot structure in a subvol, snapshot the default subvol to where i want it, and promote the subvol to be the new root. like a permanent pivot_root/chroot.

great stuff,

C Anthony