broken-tree filesystem issue possibly fixed. It still thinks /srv exists when it doesn't and the built-in fs check thinks everything is fine, but whatever. At least it shouldn't randomly decide it has no free space anymore.
Timeline
Post
Remote status
Context
5
@phnt this is terrifying man. What good is a filesystem if you can't trust it with your data
@shinyoukai @feld The only BSD I would trust with my data is FreeBSD on ZFS. And maybe Dragonfly with Hammer. Except these two I don't think there's been many attempts to even have UFS journaled. You can do it with GEOM on FreeBSD somehow, but why bother when you have ZFS. Both {Open,Net}BSD have a habit of nuking filesystem on power failure.
@phnt @feld @shinyoukai i'd run ZFS if it wasnt due to it being OOT and also the fact it doesn't use the linux VFS memory system (idk if it'll error out when doing memory intensive stuff)
@mischievoustomato @phnt @shinyoukai the ZFS ARC will give memory back to the OS, it's just not unified with the normal kernel VFS cache. Here's one of my servers
Replies
5
@feld @phnt @shinyoukai my laptop is a general pupose machine. I might consider ZFS when I upgrade my storage/laptop
@mischievoustomato @feld @shinyoukai You can change the Arc max size even on Linux. The only issue I'm aware of is that Arc isn't in memavailable.
https://github.com/openzfs/zfs/issues/10255
https://github.com/openzfs/zfs/issues/10255