Different sizes between zfs list and zpool list
tevans.uk at googlemail.com
Wed May 5 16:20:15 UTC 2010
On Wed, May 5, 2010 at 4:56 PM, Freddie Cash <fjwcash at gmail.com> wrote:
> On Wed, May 5, 2010 at 8:44 AM, Tom Evans <tevans.uk at googlemail.com> wrote:
>> When looking at the size of a pool, this information can be got from
>> both zpool list and zfs list:
>> > $ zfs list
>> NAME USED AVAIL REFER MOUNTPOINT
>> tank 5.69T 982G 36.5K /tank
>> > $ zpool list
>> NAME SIZE USED AVAIL CAP HEALTH ALTROOT
>> tank 8.14T 6.86T 1.28T 84% ONLINE -
>> Why the different sizes?
>> The pool is a raidz of 6 x 1.5 TB drives.
> zpool lists the raw storage available to the pool. Every single bit of
> every single drive is listed here. This will be 6 x 1 TB.
> zfs lists only the amount of storage available to be used, after all
> redundancy is taken into account. This will be 5 x 1 TB.
> Freddie Cash
> fjwcash at gmail.com
Ah, that makes sense - also explains why the df output matches up
precisely with the zfs list output.
More information about the freebsd-stable