I currently have a secondary pool (with raidz2) that I was originally going to use for my important documents, such as storage for Paperless-ngx, as raidz offers corruption detection and repair. The pool is encrypted.

However, I’m concerned about rebuild times (it’s a pool of 4 22TB drives). Is btrfs a better choice for this use case, or should I just go with raidz like I originally planned?

Edit: I should have mentioned that I already have 4-3-2 backups configured - I’m primarily interested in the “self-healing” aspect of ZFS so that I don’t have to recover from backups unless necessary, and to resolve corruption on the fly without me having to notice that a file is corrupt.

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    3
    ·
    edit-2
    44 minutes ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    HTTP Hypertext Transfer Protocol, the Web
    IP Internet Protocol
    RAID Redundant Array of Independent Disks for mass storage
    SSL Secure Sockets Layer, for transparent encryption
    TLS Transport Layer Security, supersedes SSL
    VPN Virtual Private Network
    ZFS Solaris/Linux filesystem focusing on data integrity
    nginx Popular HTTP server

    6 acronyms in this thread; the most compressed thread commented on today has 15 acronyms.

    [Thread #314 for this comm, first seen 25th May 2026, 11:10] [FAQ] [Full list] [Contact] [Source code]

    • Blue_Morpho@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      3
      ·
      8 hours ago

      Why was this upvoted? It’s AI slop giving definitions for acronyms that aren’t in this thread and not even related to backups.

      • homik@slrpnk.net
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 hours ago

        At least this time it has a few terms that people might not know. Usually it just spasms obvious trivialities.

      • Zeoic@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        7 hours ago

        It isn’t AI, you can take a look at the source code for it from the url it provides. Obviously the detection needs some tweaking, but extra acronyms in the list doesn’t really hurt anything when the other half are relevant.

        • Blue_Morpho@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          4 hours ago

          Detection is completely broken because it finds terms that aren’t anywhere in the thread, even as substrings.

          AI isn’t just LLM.

          • Zeoic@lemmy.world
            link
            fedilink
            English
            arrow-up
            3
            ·
            4 hours ago

            It wasnt even LLMs until the public took the term and changed it lol. Unless you are calling every algorithim ever made AI these days, this isnt AI.

            • Blue_Morpho@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              4 hours ago

              Chess programs were AI. Expert systems which were regular logic were AI. Lisp was an AI language. Chat bots were AI.

              This is a bot which makes it a type of AI and it’s really inaccurate.

              • Zeoic@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                53 minutes ago

                uhm, no? Literally none of that was considered AI. Even chatbots, people weren’t calling them AI until LLMs came around and were stuck in them. Lisp is a language USED for AI research, that doesn’t make it AI itself.

                This bot is most definitely not even close to what people consider AI