Cindys Oct 2, 2009 2:59, Thanks for staying with me. Re: "The checksums are aset on the file systems not the pool.":
But previous responses seem to indicate that I can set them for file stored in the filesystem that appears to be the pool, at the pool level, before I create any new ones. One post seems to indicate that there is a checksum property for this file system, and independently for the pool. (This topic needs a picture). Re: "If a new checksum is set and *you* rewrite the data ... then the duplciated data will have the new checksum." Understand. Now I am on to being concerned for the blocks that comprise the zpool that *contain* the file system. Re: "ZFS doesn't rewrite data as part of normal operations. I confirmed with a simple test (like Darren's) that even if you have a single-disk pool and the disk is replaced and all the data is resilvered and a new checksum is set, you'll see data with the previous checksum and the new checksum." Yes, ... a resilver duplicates exactly. Darren's example showed that without the -R, no properties were sent and the zfs receive had no choice but to use the pool default for the zfs filesystem that it created. This also implies that there was a property associated with the pool. So my previous comment about zfs send/receive not duplicating exactly was not fair. The man page / admin guide should be clear as to what is sent without -R. I would have guessed everything, just not descendent file systems. It is a shame that zdb is totally undocumented. I thought I had discovered a gold mine when I first read Darren's note! --Ray -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
