md5 of a filesystem / verifying filesystem integrity after dump/restore operation
Hi all, Does someone know how to reliably run a checksum of sorts on a filesystem, to be able to verify filesystem integrity after a restore from dump level 0 has occurred? Thanks, Ruben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: md5 of a filesystem / verifying filesystem integrity after
Hi all, Does someone know how to reliably run a checksum of sorts on a filesystem, to be able to verify filesystem integrity after a restore from dump level 0 has occurred? Unless you made a checksum of everything before doing the dump and made absolutely no changes, there is no way that I know of. Even some little things such as block arrangements being a little different after a restore - irrelevant to the integrity of the files - would make a checksum come out differently if the whole filesystem were checksummed. You can do an fsck(8) and see if there are any problems in file pointers.But, that is hardly worth bothering with since it is done at boot time anyway and it doesn't check the content of the files, only the pointers/chains. On some versions of dump either older or from other sources (vendors) dump had a verify flag that would read back everything and check it with what is on disk. I don't see it in FreeBSD's dump. Anyway, it was almost useless since the system would have to be down for the whole dump and the whole verify pass. Most people do dumps with the system up and running and in this case the files can change during the dump and verify times, thus making verify always fail. It is a rare system that can afford to be down long enough to do even a single user mode dump, let alone adding on the verify.So, it doesn't surprise me to see that option gone. jerry Thanks, Ruben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: md5 of a filesystem / verifying filesystem integrity after
Jerry McAllister [EMAIL PROTECTED] wrote: Hi all, Does someone know how to reliably run a checksum of sorts on a filesystem, to be able to verify filesystem integrity after a restore from dump level 0 has occurred? snip the potential problems with dump/md5 Could you use something like tripwire (which does an md5 of each file on the filesystem and stores them in a database for later verification)? I think tripwire only checks executable files, but the approach should work with all files. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: md5 of a filesystem / verifying filesystem integrity after
Bill Moran wrote: Jerry McAllister [EMAIL PROTECTED] wrote: Hi all, Does someone know how to reliably run a checksum of sorts on a filesystem, to be able to verify filesystem integrity after a restore from dump level 0 has occurred? snip the potential problems with dump/md5 Could you use something like tripwire (which does an md5 of each file on the filesystem and stores them in a database for later verification)? I think tripwire only checks executable files, but the approach should work with all files. Hey Bill, Jerry, You can also use AIDE for that... :-) and indeed tripwire -- Kind regards, Remko Lodder |[EMAIL PROTECTED] Reporter DSINet|[EMAIL PROTECTED] Projectleader Mostly-Harmless |[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: md5 of a filesystem / verifying filesystem integrity after dump/restore operation
On Wed, 23 Jun 2004, Ruben Bloemgarten wrote: Hi all, Does someone know how to reliably run a checksum of sorts on a filesystem, to be able to verify filesystem integrity after a restore from dump level 0 has occurred? Tripwire and its ilk live in the ports system. The base system utility, mtree, also has this capability, although you'll have to fiddle with its options to get it to work. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ You see what happens when you have fun with a stranger in the Alps? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: md5 of a filesystem / verifying filesystem integrity after
Jerry McAllister [EMAIL PROTECTED] wrote: Hi all, Does someone know how to reliably run a checksum of sorts on a filesystem, to be able to verify filesystem integrity after a restore from dump level 0 has occurred? snip the potential problems with dump/md5 Could you use something like tripwire (which does an md5 of each file on the filesystem and stores them in a database for later verification)? I think tripwire only checks executable files, but the approach should work with all files. But, of course, you still would have to have all the checksums done before the dump was done (or at least before a disk failed or was otherwise smotched) if you wanted to verify a restore. jerry -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
