4 ms·

You're not benefiting from it as much as you could be; others have mentioned scrubbing That will read all of the data from the storage device(s) checking for c

You're not benefiting from it as much as you could be; others have mentioned scrubbing That will read all of the data from the storage device(s) checking for coherency. In the case of redundancy (ie: RAID1) and corruption/rot, would use the other copy to make things whole Beyond that and trim, most of what's in here is fairly specific. ie: avoiding ENOSPC or dealing with array changes edit: I think running this more than ~monthly is overzealous... and only really meaningful if you have redundancy If memory serves, the checksums are validated when you read things anyway - so I question doing passes too aggressively. I'll accept a bit for bitrot

londons_explore 3y ago
Thing is, the drive itself typically is in a much better position to protect against bitrot. Both SSD's and spinning metal drives have ECC bits stored with the data, and the drive can detect when the data was read easily or required lots of error correction applied. And then based on that they can make the optimal call of how often to read data to see it it is 'nearly rotted' and needs a rewrite. The filesystem has no knowledge of any of that, so has to do dumb periodic scans.