I wound up causing a major outage of my services and destroying my home dir

Re:I wound up causing a major outage of my services and dest... by butlerm on Friday February 18, 2022 @07:45AM (#30385045)

Not sure how well this works out in practice, but if one drive returns a read error for a sector and the other returns the corresponding sector without an error, it should be a simple matter to trust the latter. Of course that assumes that storage corruption occurred after uncorrupted data was written to disk.

Modern drives have rather large per physical sector checksums to detect the occurrence of these errors and presumably retry a couple times before returning an I/O error if configured correctly.

In addition a good I/O bus should have error detection checksums for data in transit, and good hardware should have ECC RAM as well.

[ Parent | on HN ]

Re:I wound up causing a major outage of my services and dest... by zootboy on Friday February 18, 2022 @11:45PM (#30394493)

Indeed. That's why I specified /silent/ corruption. If the stack returns an explicit error, that is correctable (assuming the other disks don't error and return the correct data).

Sadly, a large number of SSDs (and nearly all cheap USB thumb drives / SD cards / eMMC devices) will happily return silently corrupted data.

[ Parent | on HN ]