3 ms·
Just to make it clear. raid-5/6 mdadm arrays does the right thing when repairing/checking/scrubbing data. It writes the correct data if one of the drives has a
by babas 13y ago
Just to make it clear. raid-5/6 mdadm arrays does the right thing when repairing/checking/scrubbing data. It writes the correct data if one of the drives has a corrupted block.
https://raid.wiki.kernel.org/index.php/RAID_Administration https://raid.wiki.kernel.org/index.php/RAID_Administration
How often does this happen? According to what I have been reading, without ECC RAM and without ZFS, your machines get roughly one corrupt bit per day. In other words, that could be a few corrupt files per week.
This is complete nonsense without more data to back it up.
- IgorPartola 13y agoHere is one of the sources: http://linas.org/linux/raid.html http://linas.org/linux/raid.html
- GalacticDomin8r 13y ago> Just to make it clear. raid-5/6 mdadm arrays does the right thing when repairing/checking/scrubbing data. This is inherent to RAID-5/6. Doesn't really have anything to do with mdadm other than mdadm implements RAID-5/6. And now you probably have a write hole.
- GalacticDomin8r 13y agoJust to make it clear: on raid 5/6 parity isn't checked on reads, so to get your "right thing when repairing/checking/scrubbing data" you'd have to do a full parity rebuild. This isn't anything like what ZFS does.