Bitrot is a huge issue if you care about your data. This program aims to make the silent corruption a little less silent for those irreplaceable memories.
- CentOS / RHEL 6 64 bit
- CentOS / RHEL 7 64 bit
- Debian 7 Wheezy 64 bit
- Debian 8 Jessie 64 bit
- SUSE Linux Enterprise Server 12 64 bit
- Ubuntu 12.04 Precise 64 bit
- Ubuntu 14.04 Trusty 64 bit
- Ubuntu 16.04 Xenial 64 bit
go get github.com/kormoc/bitrot-scanner
Generally the best way to handle this is to run
bitrot-scanner via cron on a cadence that matches the importance of your data.
This mode will create checksums for any files missing them and validate any checksums that exist. Useful if you want to create checksums and validate on the same schedule.
bitrot-scanner --progressBar /path/to/directory/1 /path/to/directory/2 ...
Splitting the creation of the checksums from the validation works best on large datasets that often have new files being created. This allows a rapid creation of new checksums, but allows the validation to happen on a different schedule.
Create checksums for files missing them
bitrot-scanner --lockfile=/var/run/bitrot-scanner.pid --skipValidation /path/to/directory/1 /path/to/directory/2 ...
bitrot-scanner --lockfile=/var/run/bitrot-scanner.pid --skipCreate /path/to/directory/1 /path/to/directory/2 ...
By default, we use
sha512, however you can use multiple hashes (
md5,sha512). This allows you to migrate between hash types if you desire.