Miles Nordin wrote:
"et" == Erik Trimble <erik.trim...@oracle.com> writes:
et> No, you're reading that blog right - dedup is on a per-pool
et> basis.
The way I'm reading that blog is that deduped data is expaned in the
ARC.
What I think is being done is this: for pool A and B, each have a
separate DDT. That is, if there is an identical block in both pool A
and pool B, then BOTH keep a copy of that block - removal of duplicates
is only done *inside* a pool. However, if that identical block
happens to be read from both pools and stored in the ARC, the new
feature will detect that you have an identical block in ARC, and thus
only keep a single copy of it cached in ARC.
--
Erik Trimble
Java System Support
Mailstop: usca22-123
Phone: x17195
Santa Clara, CA
Timezone: US/Pacific (GMT-0800)
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
