I believe it goes a something like this -
ZPS filesystems with dedupe turned on can be thought of as hippie/socialist
filesystems, wanting to "share", etc. Filesystems with dedupe turned off are
a grey Randian landscape where sharing blocks between files is seen as a
weakness/defect. They all live together in a zpool, let's call it "San
Francisco"...
The hippies store their shared blocks together in a communal store at the pool
level and everything works pretty well until one of the hippie filesystems
wants to pull a large number of their blocks out of the communal store; then
all hell breaks loose and the grey Randians laugh at the hippies and their
chaos but it is a joyless laughter.
That is the technical explanation, someone else may have a better explanation
in layman's terms.
On 9/23/10 3:36 PM, Peter Taps wrote:
Folks,
I am a bit confused on the dedup relationship between the filesystem and its
pool.
The dedup property is set on a filesystem, not on the pool.
However, the dedup ratio is reported on the pool and not on the filesystem.
Why is it this way?
Thank you in advance for your help.
Regards,
Peter
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
