On 07/31/2012 09:46 AM, opensolarisisdeadlongliveopensolaris wrote:
> Dedup: First of all, I don't recommend using dedup under any
> circumstance. Not that it's unstable or anything, just that the
> performance is so horrible, it's never worth while. But particularly
> with encrypted data, you're guaranteed to have no duplicate data
> anyway, so it would be a pure waste. Don't do it.
> _______________________________________________ zfs-discuss mailing
> list firstname.lastname@example.org
One thing you can do is enable dedup when you copy all your data from
one zpool to another, then, when you're done, disable dedup. It will no
longer waste a ton of memory, and your new volume will have a high dedup
ratio. (Obviously anything you add after you turn dedup off won't be
deduped.) You can keep the old pool as a backup, or wipe it or whatever
and later on do the same operation in the other direction.
Anyone know if zfs send | zfs get will maintain the deduped files after
this? Maybe once deduped you can wipe the old pool, then use get|send
to get a deduped backup?
zfs-discuss mailing list