(Most of the technical reasoning were already discussed so I won't repeat them here). And jolting for new technical reasons finds only these..
What if the fs is not only for kernel to mount, but also a boot partition for grub? Do you need to check the grub2 version? Check if this is a /boot partition?
In the above context, which is better.. this : mkfs.btrfs -O ^skinny-metadata,^mixed-bg,^extref,^raid56,^no-holes btrfs-convert -O ^skinny-metadata,^extref,^no-holes or this: mkfs.btrfs -O comp=<X> btrfs-convert -O comp=<X> X = some number below 2.7.37 OR grub2 (planned) (thanks to you, to bring this up). ?
Recently I just encountered such problem. Latest xfs-progs makes xfs version 5 by default, but grub2 can't handle version 5 yet in latest stable version. Then system can't even boot into grub2.
Good example. Appears that user didn't know what latest features to disable? so to be compatible with grub2 ? OR they have to read couple of grub documents to fix. Imagine the pain while using btrfs-convert. That means you need to restore Hope you have not deleted the ext_saved subvol. And then again run btrfs-convert.
Did you see Dave trying to add such grub2 version based probe to change mkfs.xfs features? No, just because that's not the way things should be done.
So what was fix in this case ? Or is there any fix-patch rejected ? Cheers, Anand -- 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
