ZFS hits memory hard and sometimes can bring out latent deficiencies in that hardware. on non-optimal hardware its a bit of a hardware torture test in its own right.
having said that, EXT4 and XFS are wonderful unless you need zfs/btrfs.
ZFS is really nice. I started experimenting with it when it was being introduced to FreeBSD, around 2007-2008, but only truly started using it last year, for two NASes (on Linux).
It’s complex for a filesystem, but considering all it can do, that’s not surprising.
Not recommended for single-disk root partitions. This is a mistake I’ve made myself. Recovery tools are non-existant on ZFS so non-parity setups are inherently risky. If you have root setup on at least raidz1 with at least 2 disks you are fine.
Personally I wouldn’t consider recovery as an option at all because it could easily be unavailable because the SSD failed. Instead, I tend to add a mirror drive and/or keep frequent backups where that’s not possible. So from that perspective ZFS is equivalent to Ext4, which I currently use. I’d prefer ZFS over it for it’s data verification, snapshotting and datasets features.
So should ext3 be deprecated for the same reason? Seams it also has the 2038 problem.
https://en.wikipedia.org/wiki/Ext3
Thanks for that! which made me read https://en.wikipedia.org/wiki/Ext3#ext4 Maybe high time for myself to learn more about ZFS.
I love ZFS but support for it on Ubuntu seems haphazard. It works fine for non-root drives.
I’ve tried running it as my root partition and just gave up after it fucked up my bpool dataset too many times.
Dis you use the ZFS setup built into the installer?
Yup. It booted fine but after a few reboots, bpool somehow got corrupted and refused to boot. It happened repeatedly after several reinstalls.
ZFS hits memory hard and sometimes can bring out latent deficiencies in that hardware. on non-optimal hardware its a bit of a hardware torture test in its own right.
having said that, EXT4 and XFS are wonderful unless you need zfs/btrfs.
Always run 3-4 passes of Memtest86+ on any newly acquired hardware/RAM modules.
ZFS is really nice. I started experimenting with it when it was being introduced to FreeBSD, around 2007-2008, but only truly started using it last year, for two NASes (on Linux).
It’s complex for a filesystem, but considering all it can do, that’s not surprising.
Same here lol, just read through ext{2…4} as well as Btrfs and Bcachefs (and B Trees of course). What a wonderful unplanned deep dive.
Bcachefs sounds awesome
ZFS is boss. I’m already using it for storage. Need to learn how to use it for
/.Not recommended for single-disk root partitions. This is a mistake I’ve made myself. Recovery tools are non-existant on ZFS so non-parity setups are inherently risky. If you have root setup on at least raidz1 with at least 2 disks you are fine.
Personally I wouldn’t consider recovery as an option at all because it could easily be unavailable because the SSD failed. Instead, I tend to add a mirror drive and/or keep frequent backups where that’s not possible. So from that perspective ZFS is equivalent to Ext4, which I currently use. I’d prefer ZFS over it for it’s data verification, snapshotting and datasets features.
The ext4 driver can read ext2/ext3 partitions while supporting the 2038 time issue
The only change here is the driver loading the filesystem
Ext3 support is already only available through the ext4 driver
If I recall correctly, ext3 is ext2 with journalling on top, so they can’t really get rid of ext2 without also ditching ext3.