Edit - Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

But I only turned it on for a 'filesystem' within the pool, if it has pool wide scope does that mean it's on for the whole pool? I was expecting when I created the dataset only that dataset would be deduped, so shouldn't I be able to see the ratio for only the dataset?
– deed02392
Commented Dec 20, 2012 at 0:29
4

To improve deduplication, ZFS doesn't limit itself to duplicate blocks within just one filesystem. Instead it looks across the whole pool. If dedup is not enabled for a particular filesystem then block writes are performed without passing through the dedup pipeline, even if duplicate blocks exist.
– Mike Fitzpatrick
Commented Dec 20, 2012 at 1:21
But if a duplicate block does exist in the filesystem with it enabled, surely this still yields a greater-than-one deduplication ratio, if only for that filesystem? Why can't I just see the ratio for that filesystem then?
– deed02392
Commented Dec 20, 2012 at 11:43
1

I can't answer that, maybe it was a design decision, I don't know for sure. Deduplication has side effects on reported disk usage and free space and these tend to make more sense when considering the whole pool rather than just a filesystem within it. Refer to the ZFS Dedup FAQ: Deduplicated space accounting is reported at the pool level. You must use the zpool list command rather than the zfs list command to identify disk space consumption when dedup is enabled.
– Mike Fitzpatrick
Commented Dec 20, 2012 at 21:48
You can also use zdb -S on your pool to get a rough estimate of the deduplication ratio as if it was applied. For more information, see the excellent post about deduplication on the blog of Constantin Gonzalez: constantin.glez.de/blog/2011/07/zfs-dedupe-or-not-dedupe
– user121391
Commented Jun 21, 2016 at 13:58

| Show 1 more comment

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »