On Tue, 08 Jan 2013 08:27:51 +0100 Florian Philipp <li...@binarywings.net> wrote:
> > This is a filesystem task, not a cronjab task. Use a filesystem that > > does proper checksumming. ZFS does it, but that is of course > > somewhat problematic on Linux. Check out the others, it will be > > something modern you need, like ext4 maybe or btrfs > > > > AFAIK, ext4 only has checksums for its metadata. Even if the file > system would support appropriate checksums out-of-the-box, I'd still > need a tool to regularly read files and report on errors. > > As I said above, the point is that I need to detect the error as long > as I still have a valid backup. Professional archive solutions do > this on their own but I'm looking for something suitable for desktop > usage. rsync might be able to give you something close to what you want easily Use the -n switch for an rsync between your originals and the last backup copy, and mail the output to yourself. Parse it looking for ">" and "<" symbols and investigate why the file changed. This strikes me as being a very easy solution that you could use reliably with a suitable combination of options. -- Alan McKinnon alan.mckin...@gmail.com
