• subtext@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        2 years ago

        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.

        • Peasley@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          2 years ago

          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.

          • Avid Amoeba@lemmy.ca
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            2 years ago

            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.

            • Peasley@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              2 years ago

              I’ve successfully recovered data from ext4 on a broken drive on one occasion. I agree it would have been better to have backups so lesson learned I suppose. Still if I’d been on ZFS root with no mirror I’d have been even more SOL

    • ozymandias117@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 years ago

      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