#backup #integrity

bin+lib integrity-checker

integrity checker for backups and filesystems

1 unstable release

Uses old Rust 2015

0.1.0 Jul 1, 2018

#5 in #integrity


814 lines

Backup Integrity Checker Build Status Build Status

This tool is an integrity checker for backups and filesystems.

What it Does

  • Given a directory, the tools constructs a database of metadata (hashes, sizes, timestamps, etc.) of the contents. The database itself is of course checksummed as well.

  • Given two databases (or a database and a directory) the tool iterates the entries and prints a helpful summary of the differences between them. For example, the tool highlights suspicious patterns, such as files which got truncated (had non-zero size, and now have zero size) or have other patterns that could indicate corruption (e.g. the presence of NUL bytes, if the file originally had none). Surfacing useful data while minimizing false positives is an ongoing effort.

What's it Good For?

Here are a couple sample use cases:

  • Backup integrity checking: Record a database when you make a backup. When restoring the backup, compare against the database to make sure the backup restore function has worked properly. (Or better, perform this check periodically to ensure that the backups are functioning properly.)

  • Continuous sync sanity checking: Suppose you use a tool like Dropbox. In theory, your files are "backed up" on a continuous basis. In practice, you have no assurance that the tool isn't modifying files behind your back. By recording databases periodically, you can sanity check that directories that shouldn't change often are in fact not changing. (Note: For this to be useful, the tool has to be very good at minimizing false positives.)

    This also applies to any live filesystem. Consider that a typical user will maintain continuity of data across possibly decades of hardware and filesystem upgrades. Every transition is an opportunity for silent data corruption. This tool can provide peace of mind that integrity is preserved for long-lived data.

The tool is designed around an especially stable database format so that if something were to happen, it would be relatively straightforward to recover the contained metadata.


See the format description.


Corpus: Linux 4.16.7 source (4403 directories, 62872 files, 890 MiB)

Machine: 2016 MacBook Pro 2.7 GHz Quad-Core i7

Configuration Time (s) BW (MiB/s)
No Hash 0.8832 1007.7
SHA2-512/256 1.3128 677.9
Blake2b 1.3034 682.8
SHA2-512/256 + Blake2b 1.8119 491.2


  • Isn't this better served by existing tools? ZFS, Tarsnap, etc. should never corrupt your data.

    Well, it depends. Not all users have access to a filesystem that checksums file contents, or to a machine with ECC RAM, and even the ones that do may experience filesystem bugs. In general, defense in depth is good, even with relatively trustworthy tools such as ZFS and Tarsnap. Also, in the continuous sync use case, even with backups, it can often be difficult to be assured that you haven't been subject to silent data corruption. This tool can be part of a larger toolkit for ensuring the validity of long-term storage.


  • Measure performance and see if any of the major components (e.g. the checksums) are CPU-bound and can be made to run any faster
  • Check the results on real-world backups and see if anything can be done to surface useful data while minimizing false positives
  • Rewrite check subcommand to report results interactively, instead of synchronously building an entire database in memory
  • Review the output of check/diff and consider if it can be made more helpful
  • Decide what metadata, if any, to save. Ideas:
    • Contains NUL bytes
    • Contains non-ASCII bytes
    • Is encodable as UTF-8 or other formats
    • Line endings (certain VCS tools like to munge these)
    • Is a symlink (Dropbox likes to forget this one)
    • Has extended attributes or resource forks or other unusual features
    • File name capitalization differs (might indicate trouble with a case-insensitive file system)
    • Multiple files with names that differ only in capitalization (might indicate trouble with a case-sensitive file system)
    • Differs in permissions (might indicate trouble with file system that doesn't track permissions)
  • Unit/integration tests
    • Test top-level command workflows
    • Test that database checksums work (i.e. modification to database or checksum results in error)
    • Test long-term stability of the format (i.e. older databases can be read and used)
  • Add a -v flag that shows verbose diffs
  • Add flags to configure the ignore crate (i.e. include or exclude paths)


~141K SLoC