@EdBoatConnoisseur I'm using ZFS. It's about the only filesystem you can completely trust to actually keep data integrity (and if all else fails it'll tell you your file isn't the way it's supposed to be).

Also, it has support for RAID. Btrfs RAID 5/6 still isn't stable. ZFS has RAID 5, 6, and even 7!

ZFS has over a decade of proven stability under its belt and it has always prioritised data integrity.

Btrfs literally had a bug in a "stable" release just a few years ago that'd corrupt your filesystem and make data retrieval virtually impossible.

Don't get me wrong, I like a lot of the features of Btrfs. I use it on my personal desktop. I just don't trust it for production use. The stability just isn't there.

As for deduplication, hopefully reflinks will eventually make their way into ZFS. For now you're kind if stuck with online deduplication. At least offline file deduplication is still possible via hash match + hardlinks.

For fedi, I'd argue that's more than good enough.

Actually, I might go back to $uuid/$filename because I prefer raw filename to serving $sha256.$extension?name=$filename and hoping the client respects the Content-Disposition headers (Husky does not).

I can easily use something like fdupes or jdupes to deduplicate via sha256 and hardlinks with a wheely cronjob.

https://github.com/adrianlopezroche/fdupes

https://github.com/jbruchon/jdupes

Actually, I think I might set that up over the weekend.

Anyway, yeah, ZFS for me. It wasn't until I actually learned how to ZFS and actually started using it that I understood what all the hype was about.

@shibao and @lanodan were extremely helpful in helping me set it up and understand ZFS. You can ask me as well as I now have a decent grasp on it and can help keep you from falling into some of the same pitfalls I feel into (and still haven't gotten around to correcting).