On Wed, 12 Aug 2020 15:16:37 +0100 Nix <nix@xxxxxxxxxxxxx> wrote: > On 11 Aug 2020, Roman Mamedov stated: > > For the FS considerations, the dealbreaker of XFS for me is its inability to > > be shrunk. The ivory tower people do not think that is important enough, but > > for me that limits the FS applicability severely. Also it loved truncating > > currently-open files to zero bytes on power loss (dunno if that's been > > improved). > > I've been using XFS for more than ten years now and have never seen this > allegedly frequent behaviour at all. It certainly seems to be less > common than, say, fs damage due to the (unjournalled) RAID write hole. > > I suspect you're talking about this: > <https://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_see_binary_NULLS_in_some_files_after_recovery_when_I_unplugged_the_power.3F>, > whicih was fixed in *2007*. No, it was not nulls inside files, but files becoming zero bytes in size. Like reported here https://bugzilla.redhat.com/show_bug.cgi?id=845233 Or maybe https://access.redhat.com/solutions/272673 too (don't have an account) Maybe also fixed since 2012. If so, good for you. > Shrinking xfs is relatively irrelevant these days: if you want to be > able to shrink, use thin provisioning and run fstrim periodically. The > space used by the fs will then shrink whenever fstrim is run, with no > need to mess about with filesystem resizing. It also means you can't practically remove drives from that 16-drive RAID6 if you go with XFS. Cannot shrink the filesystem, cannot reshape to fewer disks. Cannot switch to a different disk enclosure with fewer slots. Would you suggest to patch that up with running an array-wide Thin volume as well? Will not work, as the LVM thin backing volume *itself* cannot be shrunk either. And even in more suitable conditions, thin has its own overheads and added complexity. Well, if we are to mention something positive about XFS, it's another major Linux FS other than Btrfs (which is not everyone's cup of tea for its own reasons), that now got support for reflink copies (cp --reflink). Backing up file-based VMs can be done online and atomically now, like with LVM. And in general, it's the next-best thing to Btrfs snapshots, but in a mature and all-around high-performing FS. -- With respect, Roman
