Expected Output in ZFS?

[johntdavis84]

Hello!

I saw Tom Lawrence using duf in his 2024/2025 New Year Q&A video, and immediately fell in love with the look. I grabbed the version in the Debian repo for my Proxmox server; with no setup it's gorgeous and already the best way of looking at my filesystems I've ever seen. I've also installed it on my Mac via Homebrew.

I'm curious about what I should expect as far as readouts from ZFS filesystems. In particular, on my Proxmox server, it's picking up my entire ZFS dataset structure and seems to be picking up the correct SIZE value for the pools, but USED on everything but LXC zVols is reported as 128k (effectively, the default value/empty value).

In this example, vmStore64k is where my VM virtual disks live, and it's very much not empty.
ctStore0 isn't empty, either, but it is showing the disk for my one LXC.

Is this expected behavior? If not, are there ZFS specific arguments I need to pass?

[WereCatf]

This is how ZFS works, so yes, this is expected behaviour. Each dataset is an individual thing and as such the space used by each dataset's contents is reported separately, not recursively.

[johntdavis84]

Thanks for confirming that. Still very new to ZFS, so I wasn’t sure.

…

On Apr 29, 2025, at 1:26 AM, Nita Vesa ***@***.***> wrote: WereCatf left a comment (muesli/duf#293) <#293 (comment)> This is how ZFS works, so yes, this is expected behaviour. Each dataset is an individual thing and as such the space used by each dataset's contents is reported separately, not recursively. — Reply to this email directly, view it on GitHub <#293 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGI5CYU4YPA5LJUI2SNYTGT234LRXAVCNFSM6AAAAABUTVFPQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZXGYYTSNRRGA>. You are receiving this because you authored the thread.