On Wed, Sep 23, 2015 at 09:19:38PM +0800, Qu Wenruo wrote: > > From the UI point, we proposed to add a specifier that would route the > > property to either subvolume or the filesystem: > > > > $ btrfs prop set -t filesystem bgtype raid0 > > $ btrfs prop set -t subvolume bgtype raid1 > > BTW, is btrfs going to support different chunk/bg type for subvolume?! People have been asking for that for years. > I thought data/meta/system chunk types are all per filesystem level, > and was planning to use superblock to record it... Any superblock change like that will lead to backward incompatibilities worse than just storing some key:value as an extended attribute. Older kernels will just ignore the constraints but will be still mountable/usable. > If really to support that, does it mean we will have different meta/data > type for each subvolume? > That's a little too flex for me.... btrfs design is ready for this kind of flexibility. The hard task is to stay sane and offer somethig flexible yet manageable. -- 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
