Date: Mon, 8 Feb 2021 13:06:49 -0800 From: Freddie Cash <fjwcash@gmail.com> To: joe mcguckin <joe@via.net> Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: zpool list vs df free space? Message-ID: <CAOjFWZ6CM1ke1mZYh3065%2BN6NWw7Usr4wmXus-Hd8ZRTLs%2BQng@mail.gmail.com> In-Reply-To: <8BF84A0F-E66D-423A-AB99-0D19A9BB37EE@via.net> References: <8BF84A0F-E66D-423A-AB99-0D19A9BB37EE@via.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon., Feb. 8, 2021, 12:27 p.m. joe mcguckin, <joe@via.net> wrote: > df -h reports 66T available > > zpool list says 102T > > Why the discrepency? > > This is on a system with 7 16Tb drives configured as raidz2. > > Thanks, > > Joe > > > Joe McGuckin > ViaNet Communications > > joe@via.net > 650-207-0372 cell > 650-213-1302 office > 650-969-2124 fax > "zpool list" shows the raw storage available on the pool, across all the disks in the pool, minus some internal reserved storage. "zfs list" shows the usable storage space after all the parity drives are removed from the calculation. "df" output can be misleading as it doesn't take into account compression and reservations and things like that. It can give you an approximation of available space, but it won't be as accurate as "zfs list". For example, if you have 6x 2 TB drives configured as a single raidz2 vdev, then: zpool list: around 12 TB (6 drives x 2 TB) zfs list: around 8 TB (4 data drives x 2 TB) df: should be around 8 TB Cheers, Freddie Typos due to smartphone keyboard. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ6CM1ke1mZYh3065%2BN6NWw7Usr4wmXus-Hd8ZRTLs%2BQng>