Matthew Ahrens wrote:
It sounded to me like he wanted to implement tripwire, but save some time and CPU power by querying the checksumming-work that was already done by ZFS.Bady, Brant RBCM:EX wrote:Actually to clarify - what I want to do is to be able to read the associated checksums ZFS creates for a file and then store them in an external system e.g. an oracle database most likelyRather than storing the checksum externally, you could simply let ZFS verify the integrity of the data. Whenever you want to check it, just run 'zpool scrub'.Of course, if you don't trust ZFS to do that for you, you probably wouldn't trust it to tell you the checksum either!
(Otherwise, the CPU would have to checksum the ZFS files AND then checksum them again for tripwire.)
If that's what he's trying to do, the data-integrity provided by ZFS doesn't do you any good -- because the changes are going to come from the same system-calls that a legitimate user would choose.
-Luke
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
