For one of my datasets `zfs list` and `df` show significantly different used numbers:
That’s about 20% difference. I assume ZFS stores some metadata or snapshots or something like that which is not added up by using `df` (and `zfs list` REFER).
Is there a way to find out what is taking up all that space? And how to free that space?
The pool is a stripe using just one 3 TB disk; the dataset uses lz4 compression and currently has a ratio of 1.02.
Replicating the dataset with default setting makes it use 628G (also according to `zfs list`), so the data in question gets lost on the way.
Code:
# zfs list | grep myDataset NAME USED AVAIL REFER MOUNTPOINT … myPool/myDataset 826G 573G 628G /mnt/myPool/myDataset … # df -h | grep myDataset Filesystem Size Used Avail Capacity Mounted on … myPool/myDataset 1.2T 628G 573G 52% /mnt/myPool/myDataset …
That’s about 20% difference. I assume ZFS stores some metadata or snapshots or something like that which is not added up by using `df` (and `zfs list` REFER).
Is there a way to find out what is taking up all that space? And how to free that space?
The pool is a stripe using just one 3 TB disk; the dataset uses lz4 compression and currently has a ratio of 1.02.
Replicating the dataset with default setting makes it use 628G (also according to `zfs list`), so the data in question gets lost on the way.