Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RAID1 correction #6

Open
Piskvor opened this issue Mar 20, 2019 · 1 comment
Open

RAID1 correction #6

Piskvor opened this issue Mar 20, 2019 · 1 comment
Assignees

Comments

@Piskvor
Copy link

Piskvor commented Mar 20, 2019

RAID 1 is mirroring one disk with a bit-by-bit copy of another disk.

This is by convention only: the marginal utility of an additional disk drops rapidly, therefore no COTS solutions above 2 disks. I run 3-disk RAID-1 arrays, exactly for correcting errors on n-1 disks (also, if one disk in a 2-disk array fails, the other one practically tends to fail soon after, whatever the reason - from suddenly bearing the whole load? from being similar in age? from being from the same production batch?).

More-disks RAID 1 is merely impractical for archival, with its costly requirement for disk redundancy: it kind of works, but it's not the right tool for the job (as opposed to availability for currently-used data).

However, your point with "no detection of silent corruption" has merit. I suggest an addition to the RAID 1 paragraph:

While it's possible to have multiple disks in a RAID 1 array, you are paying a multiple of the storage price, with the same storage capacity as with a single disk, without a commensurate increase in resilience. In other words, not very efficient.

@lrq3000
Copy link
Owner

lrq3000 commented Apr 9, 2019

Hello @Piskvor , thank you for the suggestion, this will be added :-) This was indeed the point, thank you for clarifying!

In this set of tools, both mirroring and error correction methods are provided at the file level, because people tend to use mirroring a lot (it's easier to put in place), but indeed error correction is a lot more efficient but more complex, this tool set was aimed at making the process simpler :-)

@lrq3000 lrq3000 self-assigned this Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants