On Sun, May 31, 2009 at 10:29 AM, Rodrigo E. De León Plicet < rdele...@gmail.com> wrote:
> Hi. > > Just to report the following. > > Thanks for your time. > > Regards. > > **************************************** > > Forwarded conversation > Subject: Difference in reported available space? > ------------------------ > > From: Rodrigo E. De León Plicet <rdele...@gmail.com> > Date: Wed, May 27, 2009 at 1:00 PM > To: zfs-f...@googlegroups.com > > Sorry if the following is a dumb question. > > Related to the attached file, I just want to understand why, if 'zpool > list' reports 191MB available for coolpool, 'df -h|grep cool' only > shows 159MB available for coolpool? > > Thanks for your time. > > Regards. > > ---------- > From: Rodrigo E. De León Plicet <rdele...@gmail.com> > Date: Sat, May 30, 2009 at 8:51 PM > To: zfs-f...@googlegroups.com > > Anyone? > > ---------- > From: Fajar A. Nugraha <fa...@fajar.net> > Date: Sun, May 31, 2009 at 5:34 AM > To: zfs-f...@googlegroups.com > > Possibly upstream bug. > http://markmail.org/message/zmygvaarfvseipzx > > Better ask Sun folks, as it still happens on latest opensolaris > (2009.06) as well. > > -- > Fajar > > **************************************** > > That's not a bug, and the behavior isn't changing. zpool list shows the size of the entire pool, including parity disks. You cannot write user data to parity disks/devices. I suppose you could complain that the zpool list command should account for user data as well as parity data being subtracted from the entire pool, bug regardless, you shouldn't be using zpool list to track your data usage as it doesn't "hide" parity space like the standard userland utilities. df shows the space available minus the parity device(s). --Tim
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
