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.
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.
At least this time it has a few terms that people might not know. Usually it just spasms obvious trivialities.
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.
AI isn’t just LLM.
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.
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
@Zeoic You are both correct. Chess was chosen as an early problem domain for work on first-order logic-based programming. That certainly was considered AI. People really interested in chess later abandoned logic programming in favor of brute-force, highly parallel special purpose hardware. That was not AI.
“Expert systems” (I hate that term) are application area of “Pattern-Directed Inference Systems” (PDIS). Rule-based systems are just one type of PDIS. For example, “Constraint Satisfaction” is another powerful AI technique often used in resource optimization and scheduling systems.
https://www.chessprogramming.org/Artificial_Intelligence
" the term ‘artificial intelligence’ was coined by John McCarthy in the proposal for the 1956 Dartmouth Conference [4] . In its beginning, Computer Chess was called the Drosophila of Artificial Intelligence. "
Expert Systems:
https://en.wikipedia.org/wiki/Expert_system "In artificial intelligence (AI), an expert system is a computer system emulating the decision-making ability of a human expert.[1] "
Chatbots in AI:
https://liacademy.co.uk/the-story-of-eliza-the-ai-that-fooled-the-world/
https://en.wikipedia.org/wiki/Eugene_Goostman
I didn’t say Lisp was AI. I said it was a language used for AI.
@Blue_Morpho @selfhosted Thanks for posting this. Some interesting articles that I didn’t know about. The Wikipedia article on expert systems needs some work. Apart from editing, the content is fine but incomplete, and the citations are not the best. I may take a crack at contributing, or I might take a nap. The 80s-90s were my prime years as a developer of intelligent systems, including but not limited to knowledge based expert systems. One of the most successful AI tools I co-invented was SHINE, still in use today.
https://en.wikipedia.org/wiki/SHINE/_Expert/_System