Hi Ross,
The CR ID is 6740597:
zfs fletcher-2 is losing its carries
Integrated in Nevada build 114 and the Solaris 10 10/09 release.
This CR didn't get a companion man page bug to update the docs
so I'm working on that now.
The opensolaris.org site seems to be in the middle of its migration
s
Thanks for the update Adam, that's good to hear. Do you have a bug ID number
for this, or happen to know which build it's fixed in?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensol
Thank you for the correction. My next question is, do you happen to
know what the overhead difference between fletcher4 and SHA256 is?
Is the checksumming multi-threaded in nature? I know my fileserver
has a lot of spare cpu cycles, but it would be good to know if I'm
going to take a sub
On Fri, Oct 23, 2009 at 7:19 PM, Adam Leventhal wrote:
> On Fri, Oct 23, 2009 at 06:55:41PM -0500, Tim Cook wrote:
> > So, from what I gather, even though the documentation appears to state
> > otherwise, default checksums have been changed to SHA256. Making that
> > assumption, I have two quest
On Fri, Oct 23, 2009 at 06:55:41PM -0500, Tim Cook wrote:
> So, from what I gather, even though the documentation appears to state
> otherwise, default checksums have been changed to SHA256. Making that
> assumption, I have two questions.
That's false. The default checksum has changed from fletch
So, from what I gather, even though the documentation appears to state
otherwise, default checksums have been changed to SHA256. Making that
assumption, I have two questions.
First, is the default updated from fletcher2 to SHA256 automatically for a
pool that was created with an older version of
