Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expected Output in ZFS? #293

Open
johntdavis84 opened this issue Jan 5, 2025 · 0 comments
Open

Expected Output in ZFS? #293

johntdavis84 opened this issue Jan 5, 2025 · 0 comments

Comments

@johntdavis84
Copy link

johntdavis84 commented Jan 5, 2025

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.

image

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant