So we have multiple levels of information here.
If you have 64GB of "drive space" I believe you are referring to the
partition size. If one allocates a whole pool to this then some of the
space is used as overhead to make the pool. This includes labelling,
alignment usage, metaslab allocation overhead, slop space reservations
and other sundries. For example, a 1000 GiB disk with just a single pool
may end up with ~960 GiB of usable pool space [ see
https://wintelguy.com/2017/zfs-storage-overhead.html and
https://wintelguy.com/zfs-calc.pl ]
Next you have zfs file systems inside the pool. Again there is some
overhead for this.
Secondly, the file system stats that are shown by the desktop are most
probably not ZFS aware and probably just use the generic statvfs()
family of system calls to get file system sizes. This probably won't
show the correct free space as ZFS can't properly represent this data
over these with these older system calls because we may have compression
on and dedup that can skew the stats. The only real way to figure out
the disc size and free space with zfs is with zpool list.
Note also that zpool list shows the size in GiB (Gibibytes) based on 1K
= 1024. The GUI disk tool shows the size in GB (Gigabytes) based on 1K
= 1000. Hence zpool list size will appear also to be smaller. Use zpool
list -p to show the sizes in bytes.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897464
Title:
Problems with disk size with zfs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1897464/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
