Hi Jörg, On Tuesday 02 February 2010 16:40:50 Joerg Schilling wrote: > After that, the zpool did notice that there is more space: > > zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > test 476M 1,28M 475M 0% ONLINE - >
That's the size already after the initial creation, after exporting and importing it again: # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT test 976M 252K 976M 0% ONLINE - > the ZFS however did not grow: > > zfs list > NAME USED AVAIL REFER MOUNTPOINT > test 728K 251M 297K /test > # zfs list test NAME USED AVAIL REFER MOUNTPOINT test 139K 549M 37.5K /test I think you fell into the tarp that zpool just adds up all rows, especially visible on a thumper when it's under heavy load, the read and write operations per time slice for each vdev seem to be just the individual sums of the devices underneath. But this still does not explain why the pool is larger ater exporting and reimporting. Cheers Carsten _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
