this post was submitted on 15 Sep 2023
495 points (96.3% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
55085 readers
281 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The calculations necessary to rebuild a failed drive from parity data stored on the other drives means that for the duration of the time that the array is being rebuilt (aka "resilvered"), you'll have high activity on the other drives. So during that time there's an increased chance that a drive that was already on the brink of failure is pushed over the edge. If that happens, your data is gone. Like I said it depends on your risk tolerance. You may not feel like it's worth it in your situation. I personally only run a raidz1. I accept the risk that entails, just as people who use raidz2 accept the increased risk that entails over raidz3. There's no limit to the amount of redundancy you can add. The level of redundancy that's needed is a decision that only you/your organization can make.
well, I never tought of data loss prevention in this way. Thanks.