>> mtree(8) with -K sha1digest might be enough, and is in the base >> system. >It's a bit more complicated. You have a bitrot if the file checksum >changed >AND the modification time hasn't changed. Files that are updated will be >reported as corrupted, which may be boring. >If you have archiving static data, the mtree method works though.
There is also ./archivers/par2cmdline which lets you create redundancy for files. It is a lot higher in system (above file system), so you would need to make scripts to use frequently. It also doesn't create redundancy for filesystem's metadata. It would not harden your file system.
