On Thu, Aug 08, 2013 at 05:13:49AM -0700, Christoph Hellwig wrote: > On Wed, Aug 07, 2013 at 04:51:46PM -0400, Josef Bacik wrote: > > Not possible, this will break other things as subvolumes have their own > > inode > > space, it will confuse applications that get multiples of an inode number > > for > > different devices with the same st_dev. Each subvolume has it's own > > anonymous > > dev to segregate things. Thanks, > > Yes, it's the same old issue of btrfs volumes misbehaving, and the > solution is still the same as 5 years ago: make sure each subvolume > has it's own sb, vfsmount and gets automounted, similar to what nfs4 > does for this case.
This won't work, try having 10000 subvolumes with dirty inodes and do sync then go skiing, you'll have time :). Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
