Hacker News Reader

Comment by colechristensen | Hacker News Reader

Back in the day XFS was great and worked excellently and was quite resilient, performant, etc. etc... until it wasn't. If it got too full or somehow corrupted beyond its capacity to recover then you were just screwed and it was very difficult to actually get your data back. Like it had a much higher threshold for being shitty and was great before you hit that threshold but after you hit it it was much worse than ext2/3 or whatever else I was using. Something around 80% full and it started to get awful and you risked losing your entire filesystem.

I'd have real reservations about knowingly using it again these days because of bad experiences, though this bias is based on really old experiences which are quite possibly no longer relevant.

View on HN

I have two bad XFS experiences that stick out in my memory. I like XFS, don't get me wrong.

I ran XFS on our Linux distribution/package mirror. We ended up having some sort of error and the filesystem wouldn't mount, so I tried running the fsck. After around a day, it bombed out with out of memory. I scrounged around, took down another server or two to max out the memory on the mirror server and eventually was able to get it to complete the fsck in a couple more days.

For a while I ran XFS on my laptop. This was some Thinkpad that had fancy-pants graphics, and the graphics drivers made the system quite unstable It would oops every 2-4 hours of normal use. XFS had this bad habit at the time (long since fixed, IIRC) of reverting files to HOURS old data after the reboot.

A peer of this comment mentioned btrfs. Around the same time I played around with btrfs. For around a year I ran a couple of my company laptops on btrfs with zero problems. Then, after one set of updates, both of them completely corrupted their filesystems. I stopped using it, hoping that btrfs would fairly quickly stabilize, but have never ended up going back to it. I love the idea of btrfs, but am a bit gun-shy.

I used Reiser extensively for map tile file-systems, largely because their idea of a "small file" was 1-2 orders of magnitude smaller than most other filesystems. This particular use case was full world tiles, and a lot of them were solid blue (oceans, you know), I want to say 37 bytes. My current gig puts tiles on XFS and it works great for that.

ZFS is a filesystem that has never let me down. Performance can often be spotty, especially if you think you can use dedup, but I've had some pretty bad things happen to ZFS volumes and have never lost data on one of them. It's really the only place I'll put archive data. I've run a lot of backup servers using ZFS, even back in the days of zfsfuse, and it's just been a workhorse. Even in early days when zfsfuse had some pretty obscure bugs and would choke about every month or two. Kudos to the zfs+fuse developers, they quickly tracked down every issue I ran into once I had a stress test use case going.

EXT has been a real workhorse too. I've lost data, rarely, but considering it's 99% of the filesystems I've run over the decades... Pretty good track record.

Veritas vx on HP-UX was like a space age filesystem back in the mid '90s, but also was kind of painful. My memories of it are just vague and bad.

I'd love to have HAMMER under Linux. :-)

Ok, discuss!

I’ve been running btrfs on my laptop and workstation since 2015 and haven’t had any issues. I get all the advanced FS functionality I want without needing to worry about kernel versions or any of the other hassle of setting up ZFS.

In many ways ZFS feels like the last hurrah of “traditional” file systems. The fact that ZFS finds itself without genuine alternatives isn’t because it’s just that good, it’s because industry players have moved on. If all you need is a monster file server or a local data archive, sure, use ZFS.

> file server or a local data archive

thats all you want from a fs, isn't it?

everything else is temporary data, living in memory.

With btrfs, interestingly enough never lost data, but got volume stuck to read only mode (fsck didn't help) multiple times over the years.

On sad note qgroup qouta (it is fancy qouta - you can limit disk usage per subvolume basis https://btrfs.readthedocs.io/en/latest/btrfs-quota.html#perf... sounds much more positive than real impact :/ although didn't test with latest kernel ) starts struggle when there are load using 5 users (using docker containers with jupyterhub) and when load goes near 10 docker instances, new docker container creation literally crawls - start taking minutes

Back in the early 2000s I had XFS zero out some files on power outage. Well known bug at the time. Fixed soon but retained the branding.

What a time. People would recommend ReiserFS back then. Big fan club.

Yes, it was very annoying and it happened even to files that were open only for reading, not for writing.

For me, /etc/fstab was zeroed a couple of times, which lead to a bricked system (before 2000).

Fortunately, this bug was eventually solved and I have been using XFS for more than twenty years on a great variety of hardware, with excellent results and no data loss whatsoever.

Reiser and XFS were totally opposite in design. Reiser was born for being fast with tons of small files, suitable for your KDE desktop with lots of software/kparts/plugins installed.

XFS was created to manage big multimedia files, such as uncut/unedited RAW photos and videos.

That sounds like the experience a lot of people had with BTRFS (unfortunately).

Yep, ENOSPC and BTRFS are old friends

In my experience enabling the finobt (free inode btree) setting made for a better experience under consistent capacity pressure. Context: CentOS 7, 7 TB RAID-10 SSD with ~100million files and ~4% churn rate per day, in production above 80% full for most of 5 years. Twice we experienced an XFS issue but xfs_repair got the FS back online and intact.

Reply on news.ycombinator.com