On 11/01/18 03:07, Dave Chinner wrote: > XFS comes from a different background - high performance, high > reliability and hardware RAID storage. Think hundreds of drives in a > filesystem, not a handful. i.e. The XFS world is largely enterprise > and HPC storage, not small DIY solutions for a home or back-room > office. We live in a different world, and MD rarely enters mine. So what happens when the hardware raid structure changes? Ext allows you to grow a filesystem. Btrfs allows you to grow a filesystem. Reiser allows you to grow a file system. Can you add more disks to XFS and grow the filesystem? My point is that all this causes geometries to change, and ext and btrfs amongst others can clearly handle this. Can XFS? Because if it can, it seems to me the obvious solution to changing raid geometries is that you need to grow the filesystem, and get that to adjust its geometries. Bear in mind, SUSE has now adopted XFS as the default filesystem for partitions other than /. This means you are going to get a lot of "hobbyist" systems running XFS on top of MD and LVM. Are you telling me that XFS is actually very badly suited to be a default filesystem for SUSE? What concerns me here is, not having a clue how LVM handles changing partition sizes, what effect this will have on filesystems ... The problem is the Unix philosophy of "do one thing and do it well". Sometimes that's just not practical. The Unix philosophy says "leave partition management to lvm, leave redundancy to md, leave the files to the filesystem, ..." and then the filesystem comes along and says "hey, I can't do my job very well, if I don't have a clue about the physical disk layout". It's a hard circle to square ... :-) (Anecdotes about btrfs are that it's made a right pigs ear of trying to do everything itself.) Cheers, Wol -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
