Jure Pečar wrote: > Maybe a basic zfs question ... > > I have a pool: > > # zpool status backup > pool: backup > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > backup ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c1t0d0s1 ONLINE 0 0 0 > c2t0d0s1 ONLINE 0 0 0 > raidz2 ONLINE 0 0 0 > c1t1d0 ONLINE 0 0 0 > c1t2d0 ONLINE 0 0 0 > c1t3d0 ONLINE 0 0 0 > c1t4d0 ONLINE 0 0 0 > c1t5d0 ONLINE 0 0 0 > c1t6d0 ONLINE 0 0 0 > c1t7d0 ONLINE 0 0 0 > c2t1d0 ONLINE 0 0 0 > c2t2d0 ONLINE 0 0 0 > c2t3d0 ONLINE 0 0 0 > c2t4d0 ONLINE 0 0 0 > c2t5d0 ONLINE 0 0 0 > c2t6d0 ONLINE 0 0 0 > c2t7d0 ONLINE 0 0 0 > > For which list reports: > > # zpool list backup > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > backup 13.5T 434K 13.5T 0% ONLINE - > > > Yet df and zfs list shows something else: > > [EMAIL PROTECTED]:~# zfs list > NAME USED AVAIL REFER MOUNTPOINT > backup 262K 11.5T 1.78K none > backup/files 32.0K 11.5T 32.0K /export/files > ... > > # df -h > Filesystem size used avail capacity Mounted on > ... > backup/files 11T 32K 11T 1% /export/files > > > Why does AVAIL differ for such a large amount? >
They represent two different things. See the man pages for zpool and zfs for a description of their meanings. -- richard > (NexentaOS_20080131) > > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
