If you did not do "zfs set dedup=fletcher4,verify " (which is available
in build 128 and nightly bits since then), you can ignore this message.
We have changed the on-disk format of the pool when using
dedup=fletcher4,verify with the integration of:
6903705 dedup=fletcher4,verify doesn't byt
We discovered another, more fundamental problem with dedup=fletcher4,verify.
I've just putback the fix for:
6904243 zpool scrub/resilver doesn't work with cross-endian
dedup=fletcher4,verify blocks
The same instructions as below apply, but in addition, the
dedup=fletcher4,verify functio
And, for the record, this is my fault. There is an aspect of endianness
that I simply hadn't thought of. When I have a little more time I will
blog about the whole thing, because there are many useful lessons here.
Thank you, Matt, for all your help with this. And my apologies to
everyone else
Finally, just to be clear, one last point: the two fixes integrated
today only affect you if you've explicitly set dedup=fletcher4,verify.
To quote Matt:
> This is not the default dedup setting; pools that only used "zfs set
> dedup=on" (or =sha256, or =verify, or =sha256,verify) are unaffected.
When will SXCE 129 be released since 128 was passed over? There used to
be a release calendar on opensolaris.org but I can't find it anymore.
Jeff Bonwick wrote:
And, for the record, this is my fault. There is an aspect of endianness
that I simply hadn't thought of. When I have a little more
Maybe 11/30/2009 ?
According to
http://hub.opensolaris.org/bin/view/Community+Group+on/schedule. we have
onnv_129 11/23/2009 11/30/2009
But..as far as i know those release dates are in a "best effort basis".
Bruno
Karl Rossing wrote:
> When will SXCE 129 be released since 128 was passed over? T
It seems b128 will be re-spun for IPS, and was canceled only for SXCE.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
