View Single Post
wicket's Avatar
Posts: 634 | Thanked: 3,266 times | Joined on May 2010 @ Colombia
#17
Originally Posted by Zeta View Post
Surprising ?

Yeah btrfs can probably recover a lot more than a few bits (never looked at how it works), but what he is saying for "non trivial amount of errors", doesn't seem wrong, and is related to Hamming distance (https://en.wikipedia.org/wiki/Hamming_distance), and in particular things like this quote "Thus a code with minimum Hamming distance d between its codewords can detect at most d-1 errors and can correct ⌊(d-1)/2⌋ errors.".

Did I missed something obvious ?
I don't claim to know all the ins and outs of Btrfs and I was unaware it uses Hamming distance to detect errors. Thank you for enlightening me.

The basics of volume management are that checksuming is used to detect errors and then the data recovery depends on what type of RAID you have configured. In the case of RAID1, the data is corrected by copying it from a valid mirror disk. In the case of RAID5, the correct data is calculated using the parity check. This has absolutely nothing to do with the length of the checksum. Btrfs can rebuild your whole disk if it has to as long as there is sufficient redundancy in place.

Or am I missing something?
__________________
DebiaN900 - Native Debian on the N900. Deprecated in favour of Maemo Leste.

Maemo Leste for N950 and N9 (currently broken).
Devuan for N950 and N9.

Mobile devices with mainline Linux support - Help needed with documentation.

"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
 

The Following User Says Thank You to wicket For This Useful Post: