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.
_______________________________________________
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
