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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
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.