Hi Karim,
All ZFS storage pools are going to use some amount of space for
metadata and in this example it looks like 3 GB. This is what
the difference between zpool list and zfs list is telling you.
No other way exists to calculate the space that is consumed by
metadata.
pool space (199 GB) minus avail file system space (196 GB) = 3 GB
The db-smp.zpool/db-smp.zfs is consuming 180 GB and the
db-smp.zpool/oraarch.zfs is consuming 15.8 GB, which adds up to 196 GB.
This pool is full so you need to reduce the space that the file systems
are consuming or add more disks to the pool.
Cindy
On 10/23/09 06:55, Karim Akhssassi wrote:> Hi,
>
> Im Karim from the Solaris software support, i need a help from your side
> regarding this issue :
>
> Why ZFS is full while it''s zpool has 3.11 Go available ?
>
> zfs list -t filesystem | egrep "db-smp|NAME"
> NAME USED AVAIL REFER MOUNTPOINT
> db-smp.zpool 196G 0 1K legacy
> db-smp.zpool/db-smp.zfs 180G 0 70.8G
> /opt/quetzal.zone/data/quetzal.zone/root/opt/db-smp
> db-smp.zpool/oraarch.zfs 15.8G 0 15.8G
> /opt/quetzal.zone/data/quetzal.zone/root/opt/db-smp/oracle/SMP/oraarch/
> zpool list | egrep "db-smp|NAME"
> NAME SIZE USED AVAIL CAP HEALTH ALTROOT
> db-smp.zpool 199G 196G 3.11G 98% ONLINE
> /opt/quetzal.zone/data/quetzal.zone/root
>
> *I Found* http://www.opensolaris.org/os/community/zfs/faq/#zfsspace
> <http://www.opensolaris.org/os/community/zfs/faq/#zfsspace>
> ---
> 1) Why doesn''t the space that is reported by the zpool list
command and
> the zfs list command match?
> The available space that is reported by the zpool list command is the
> amount of physical disk space. The zfs list command lists the usable
> space that is available to file systems, which is disk space minus ZFS
> redundancy metadata overhead, if any.
> **
>
> if this doc can explain the above issue, how can i know (calculate) the
> zfs redundancy metadata?how can i know if it exists?
> otherwise how can we fix the above problem.
>
> I appreciate your help
>
> regards
>
> A.Karim
>
>