On Oct 15, 2013, at 1:23 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > After changing the default subvolume, I can't mount a nested subvolume with a correct relative pathname to the default subvolume; it can only be mounted by absolute path or subvolid. > > Setup: > 3.11.4-302.fc20.x86_64 > btrfs-progs-0.20.rc1.20130917git194aa4a-1.fc20.x86_64 > dir = a directory, sub=a subvolume, nested=a subvolume; set-default is top level 5 > > > # mount -o subvol=dir/sub /dev/vda1 /mnt > # btrfs subvol list /mnt > ID 263 gen 140 top level 5 path dir/sub > ID 264 gen 140 top level 263 path nested > > # btrfs subvol set-default 263 /mnt > # umount /mnt > # mount -o subvol=nested /dev/vda1 /mnt > mount: mount(2) failed: No such file or directory > # mount -o subvol=/nested /dev/vda1 /mnt > mount: mount(2) failed: No such file or directory > > # mount -o subvol=/dir/sub/nested /dev/vda1 /mnt > [works] > # umount /mnt > # mount -o subvolid=264 /dev/vda1 /mnt > [works] > Further both of these work and produce the same results # mount -o subvol=/dir/sub/nested /dev/vda1 /mnt # mount -o subvol=dir/sub/nested /dev/vda1 /mnt I think that's wrong, unless set-default is effectively deprecated. Is it? /dir/ and dir/ are not the same thing, but even with set-default 263 both of those work as if they were the same thing. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
