Hi Michael,

For a RAIDZ pool, the zpool list command identifies the "inflated" space
for the storage pool, which is the physical available space without an
accounting for redundancy overhead.

The zfs list command identifies how much actual pool space is available
to the file systems.

See the example of a RAIDZ-2 pool created below with 3 44 GB disks.
The total pool capacity reported by zpool list is 134 GB. The amount of
pool space that is available to the file systems is 43.8 GB due to
RAIDZ-2 redundancy overhead.

See this FAQ section for more information.

http://hub.opensolaris.org/bin/view/Community+Group+zfs/faq#HZFSAdministrationQuestions

Why doesn't the space that is reported by the zpool list command and the zfs list command match?

Although this site is dog-slow for me today...

Thanks,

Cindy

# zpool create xpool raidz2 c3t40d0 c3t40d1 c3t40d2
# zpool list xpool
NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
xpool   134G   234K   134G     0%  ONLINE  -
# zfs list xpool
NAME    USED  AVAIL  REFER  MOUNTPOINT
xpool  73.2K  43.8G  20.9K  /xpool


On 03/15/10 08:38, Michael Hassey wrote:
Sorry if this is too basic -

So I have a single zpool in addition to the rpool, called xpool.

NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
rpool   136G   109G  27.5G    79%  ONLINE  -
xpool   408G   171G   237G    42%  ONLINE  -

I have 408 in the pool, am using 171 leaving me 237 GB.
The pool is built up as;

  pool: xpool
 state: ONLINE
 scrub: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        xpool       ONLINE       0     0     0
          raidz2    ONLINE       0     0     0
            c8t1d0  ONLINE       0     0     0
            c8t2d0  ONLINE       0     0     0
            c8t3d0  ONLINE       0     0     0

errors: No known data errors


But - and here is the question -

Creating file systems on it, and the file systems in play report only 76GB of 
space free....

<<<<SNIP FROM ZFS LIST>>>>>>>

xpool/zones/logserver/ROOT/zbe     975M  76.4G   975M  legacy
xpool/zones/openxsrvr             2.22G  76.4G  21.9K  /export/zones/openxsrvr
xpool/zones/openxsrvr/ROOT        2.22G  76.4G  18.9K  legacy
xpool/zones/openxsrvr/ROOT/zbe    2.22G  76.4G  2.22G  legacy
xpool/zones/puggles                241M  76.4G  21.9K  /export/zones/puggles
xpool/zones/puggles/ROOT           241M  76.4G  18.9K  legacy
xpool/zones/puggles/ROOT/zbe       241M  76.4G   241M  legacy
xpool/zones/reposerver             299M  76.4G  21.9K  /export/zones/reposerver


So my question is, where is the space from xpool being used? or is it?


Thanks for reading.

Mike.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to