On Mon, Feb 08, 2010 at 11:24:56AM -0800, Lutz Schumann wrote: > > Only with the zdb(1M) tool but note that the > > checksums are NOT of files > > but of the ZFS blocks. > > Thanks - bocks, right (doh) - thats what I was missing. Damn it would be so > nice :(
If you're comparing the current data to a snapshot baseline on the same pool, it just means you need to compare more checksums (several per file), it doesn't invalidate the idea. There may also be other ways of checking quickly that the file data is unmodified since snapshot X, but again it will require looking at zfs internals. This is far from the first use case for an official interface to get at this kind of data. It's quite similar to the question of how to verify send|recv integrity from yesterday, for example. As yet I don't know of a concrete proposal of what such an interface should look like (since there's nothing to borrow from POSIX), let alone an implementation. It more complicated if you're comparing checksums against an external baseline reference (such as from a build) because block sizes and checksum algorithms may vary between pools. However, as you note, that's already catered for by existing tools, so they could work together. -- Dan.
pgp3k63UrsurG.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
