On 2020-06-19 5:31 a.m., Roman Mamedov wrote: > On Fri, 19 Jun 2020 10:08:43 +0200 > Daniel Smedegaard Buus <danielbuus@xxxxxxxxx> wrote: > >> Well, that's why I wrote having the *data* go bad, not the drive > > But data going bad wouldn't pass unnoticed like that (with reads resulting in > bad data), since drives have end-to-end CRC checking, including on-disk and > through the SATA interface. If data on-disk is somehow corrupted, that will be > a CRC failure on read, and still an I/O error for the host. > This used to be my assumption as well. However, since I started using BTRFS in more places, I have recorded 3 instances of BTRFS detecting corruption that was completely unnoticed by Drive or system, before finally hitting an SSD that knew it was hitting an error. That's a pretty small anecdote in the grand scheme of things, and I'm sure Zygo can give something that more closely resembles a real statistic.... But I'm left to admit that silent corruption from drives / I/O controllers is far more prevalent than I used to think.
Attachment:
signature.asc
Description: OpenPGP digital signature
