On Oct 15, 2013, at 2:50 PM, David Sterba <dsterba@xxxxxxx> wrote: > On Tue, Oct 15, 2013 at 01:23:44PM -0600, Chris Murphy 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. > > The path to subvol= is always taken as absolute, no matter if the path > starts with / or not. Looks like this changed with the 3.2 kernel " Subvolumes mountable by full path", I thought that was in addition to relative rather than a total change in behavior. Good to know. Is the idea that subvolume set-default only affects mount -o defaults behavior and nothing else? 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
