On Mon, Sep 05, 2011 at 03:51:29PM +0200, David Sterba wrote: > Hi, > > On Mon, Sep 05, 2011 at 12:13:25PM +0200, Björn Kalkbrenner wrote: > > Then i tried to > > "mount -o subvolumeid=256 /dev/mapper/root /home" (id of home subvol) > > and the content of my home is back... > > this is a known limitation and a fix is pending in Josef's development > tree > > http://git.kernel.org/?p=linux/kernel/git/josef/btrfs-work.git;a=commit;h=4fbb149dfc7454d0f233fa8e5b9167f3645c8fcc > > > "Btrfs: fix how we mount subvol=<whatever> > > We've only been able to mount with subvol=<whatever> where whatever was > a subvol within whatever root we had as the default. This allows us to > mount -o subvol=path/to/subvol/you/want relative from the normal > fs_tree root. Thanks," > > currently, the /home subvolume is searched inside the volume set by > 'set-default'. When you change it to an alternative root snapshot, the > '/home' subvolume lookup fails as you've seen. > > The patch changes it so that the subvolumes are always looked up to the > original default root subvolume (I don't know of a better name, internal > id 5 or alse selectable by subvolid=0).
I've always tried to refer to it as the "top level" or "subvolid=0". Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Always be sincere, whether you mean it or not. ---
signature.asc
Description: Digital signature
