On Thu, 13 Jul 2023, Samuel Sieb wrote:
On 7/13/23 21:08, Michael Hennebry wrote:
If you really want a warning and all else fails,
use your own checksums.
Have a process walk the filesystem.
If a file is open for writing, skip it.
If a file is older than the recorded checksum,
test the checksum.
Write a new checksum.
Where to put the checksums is left as an exercise for the reader.
If you're using btrfs, everything is automatically checksummed at all times.
But I don't know what this will warn you of in this case. SSDs usually fail
suddenly with no warning. It's very unlikely that you will get corrupted
data.
I was expecting that there would be some time between
the first corrupt block and an irreparable filing system.
From subsequent reading, there is,
but the SSD does a good job of hiding corrupt blocks.
A better tactic would be to ask the SSD how many spare blocks it has left.
That assumes one can ask the SSD and that one does it before
the flash translation layer is corrupted by a bad block.
--
Michael hennebry@xxxxxxxxxxxxxxxxxxxxxx
"Occasionally irrational explanations are required" -- Luke Roman
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
