----- Original Message ----- > From: "Theodore Ts'o" <tytso@xxxxxxx> > To: "Mike Fleetwood" <mike.fleetwood@xxxxxxxxxxxxxx> > Cc: "Andrew Martin" <amartin@xxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx > Sent: Tuesday, September 24, 2013 9:57:24 AM > Subject: Re: Data Integrity Check on EXT Family of Filesystems > > On Mon, Sep 23, 2013 at 11:00:09PM +0100, Mike Fleetwood wrote: > > > > Here's a couple of integrity checking tools to consider: > > tripwire - http://sourceforge.net/projects/tripwire/ > > aide - http://aide.sourceforge.net/ > > I use cfv myself to create checksum files. Note that using CRC > checksum is plenty if you are just worried about random corruption > caused by hardware errors (i.e., memory bitflips, hard drive > hiccups). > > Using a cryptographic checksum ala tripwire is useful if you are > worried about malicious attackers trying to modify files without your > noticing. Cryptographic checksums do take more CPU time, though. > > Cheers, > > - Ted > Ted, Thanks for the suggestion about cfv - it looks like it should work well for efficiently checking large trees and detecting random corruption. I like that the -r option stores the checksums recursively in each directory, that way you can also choose to only check a particular subtree. Mike, thanks for the other suggestions as well. I've used tripwire before but had not considered using it in this context due to its focus on security and intrusion detection. Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
