On 9 May 2017, Brad Campbell stated: > On 09/05/17 17:58, Nix wrote: >> md doesn't repair the corruption, even though on RAID-6 it could. > > Patches are *always* welcome. Oh good. I might well look at that. >> but one wonders how many disks actually *do* this. It's hard to >> tell because sector sparing is so quiet: it's not always even reflected >> in the SMART data, AIUI. > > Decent SAS drvies do it routinely *and* they tell you in the SMART > data how long it has been since the last scrub, how long it is until > the next scrub and how many errors it has silently corrected over the > drive life. You get what you pay for. Enterprise SATA drives appear similar except that they don't do the scrubbing automatically: you have to trigger a SMART self-test. (I'm wondering if that's enough, and perhaps I can ignore RAID scrubbing entirely, except that if something *does* go wrong I won't know.) Of course I haven't yet owned a drive that has ever deigned to give a nonzero sector-sparing value in any of its SMART info, and I've been using allegedly-enterprise drives (first SCSI, then SATA) for about fifteen years now. I've had disk failures without warning, and non-failed disks with both read and write errors that would not go away, but that SMART reallocation value just stayed stuck at zero through all of it. I'm wondering if smartctl is even reading the right field, but it's hard to imagine how it couldn't be... -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
