On Wed, Aug 25, 2010 at 2:05 PM, Peter Taps ptr...@yahoo.com wrote:
It appears it is better to use on instead of sha256. This way, you are
letting zfs decide the best option.
It's probably better to specify the hash type, actually. If on were
to change in the future version, data written after
On Tue, Aug 24, 2010 at 9:45 PM, Peter Taps ptr...@yahoo.com wrote:
Essentially, on is just a pseudonym for sha256 and verify is just a
pseudonym for sha256,verify.
Can someone please confirm if this is true?
When dedup was initially announced, dedup=on was fletcher4. There was
a problem
Thank you all for your help.
It appears it is better to use on instead of sha256. This way, you are
letting zfs decide the best option.
Regards,
Peter
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
Folks,
One of the articles on the net says that the following two commands are exactly
the same:
# zfs set dedup=on tank
# zfs set dedup=sha256 tank
Essentially, on is just a pseudonym for sha256 and verify is just a
pseudonym for sha256,verify.
Can someone please confirm if this is true?
Correct.
Jeff
On Aug 24, 2010, at 9:45 PM, Peter Taps wrote:
Folks,
One of the articles on the net says that the following two commands are
exactly the same:
# zfs set dedup=on tank
# zfs set dedup=sha256 tank
Essentially, on is just a pseudonym for sha256 and verify is just a
Correct, but presumably for a limited time only. I would think that over time
as the technology improves that the default would change.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
