On Sun, May 31, 2009 at 12:57 PM, Tim<t...@tcsac.net> wrote: > > On Sun, May 31, 2009 at 10:29 AM, Rodrigo E. De León Plicet > <rdele...@gmail.com> wrote: >> >> 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? > > 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).
But, in this case, I'm using mirroring. Wouldn't the ZFS parity overhead apply to raidz/raidz2 only? I confess I'm not 100% clear on the concepts... Thanks for your time. Regards. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
