Timeline for How to get error detection and correction on a single hard drive on linux (with btrfs or other methods)
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 25, 2023 at 3:52 | comment | added | aggregate1166877 | A big issue with RAID5 these days is that recovering a failed disk actually destroys the other "healthy" disks very often. It's especially prevalent with spinning disks over 2TB. A restore is basically guaranteed to destroy at least one other disk if each disk is 10TB spinning. I've actually seen 3 disks fail in sequence on a RAID5 restore, causing nearly a week of downtime. Source: my own experience (though I have seen some write-ups about it). Unsure how SSD is affected. | |
| Mar 27, 2023 at 9:09 | comment | added | Tim Small | RAID5 is able to: 1. Recreate lost data from one data member. 2. Detect corruption on one member (but not be able to tell you which one is corrupted). ... as such you could argue that it doesn't offer any meaningful error correction in the context that the author is talking about. | |
| Sep 19, 2022 at 18:51 | comment | added | Rucent88 | For storing files that aren't read/written often, that's a really creative idea! | |
| Aug 29, 2019 at 21:47 | comment | added | RalfFriedl | It would also give you bad performance. | |
| S Aug 29, 2019 at 21:25 | review | Low quality posts | |||
| Aug 29, 2019 at 22:55 | |||||
| S Aug 29, 2019 at 21:25 | review | Late answers | |||
| Aug 29, 2019 at 21:47 | |||||
| Aug 29, 2019 at 21:10 | review | First posts | |||
| Aug 29, 2019 at 21:17 | |||||
| Aug 29, 2019 at 21:08 | history | answered | Franziscus | CC BY-SA 4.0 |