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?
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
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]
Why was this upvoted? It’s AI slop giving definitions for acronyms that aren’t in this thread and not even related to backups.
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.
Detection is completely broken because it finds terms that aren’t anywhere in the thread, even as substrings.
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.
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.