Ray,
The checksums are set on the file systems not the pool.
If a new checksum is set and *you* rewrite the data, then the rewritten
data will contain the new checksum. If your pool has the space for you
to duplicate the user data and new checksum is set, then the duplicated
data will have the new checksum.
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.
Cindy
On 10/02/09 08:44, Ray Clark wrote:
Replying to Cindys Oct 1, 2009 3:34 PM post:
Thank you. The second part was my attempt to guess my way out of this. If the fundamental structure of the pool (That which was created before I set the checksum=sha256 property) is using fletcher2, perhaps as I use the pool all of this structure will be updated, and therefore automatically migrate to the new checksum. It would be very difficult for me to recreate the pool, but I have space to duplicate the "user" files (and so get the new checksum). Perhaps this will also result in the underlying "structure" of the pool being converted in the course of normal use.
Comments for or against?
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
