I see the same behavior on illumos.  Agreed that it should act like "zpool
list" and figure out the correct field width.  Patches appreciated :-)

--matt


On Wed, Jun 25, 2014 at 1:19 AM, Trond Endrestøl <
[email protected]> wrote:

> I have two FreeBSD/amd64 stable/9 systems with rather long pool names.
>
> While running zpool iostat -v 1 on these systems, I noticed zpool(8)
> only considers the length of the names of the vdev members when
> scaling the width of the pool field.
>
> Sample from system 1:
>
>                capacity     operations    bandwidth
> pool        alloc   free   read  write   read  write
> ----------  -----  -----  -----  -----  -----  -----
> enterprise_zdata   578G   814G      0      0      0      0
>   raidz1     578G   814G      0      0      0      0
>     ada2        -      -      0      0      0      0
>     ada3        -      -      0      0      0      0
>     ada4        -      -      0      0      0      0
> ----------  -----  -----  -----  -----  -----  -----
> enterprise_zroot  61,6G   386G      0      0      0      0
>   mirror    61,6G   386G      0      0      0      0
>     ada0p3      -      -      0      0      0      0
>     ada1p3      -      -      0      0      0      0
> ----------  -----  -----  -----  -----  -----  -----
>
> Sample from system 2:
>
>                          capacity     operations    bandwidth
> pool                  alloc   free   read  write   read  write
> --------------------  -----  -----  -----  -----  -----  -----
> svabu_zdata           1,36T   469G      0     47      0  5,95M
>   mirror              1,36T   469G      0     47      0  5,95M
>     ada3                  -      -      0     47      0  5,95M
>     ada2                  -      -      0     52      0  6,58M
> --------------------  -----  -----  -----  -----  -----  -----
> svabu_zroot           26,3G   434G      0      0      0      0
>   mirror              26,3G   434G      0      0      0      0
>     gpt/svabu_zroot0      -      -      0      0      0      0
>     gpt/svabu_zroot1      -      -      0      0      0      0
> --------------------  -----  -----  -----  -----  -----  -----
>
> The output would be a lot more readable if zpool(8) would also
> consider the length of the pool names when scaling the width of the
> pool field.
>
> The same applies when running zpool status (-v):
>
>   pool: enterprise_zdata
>  state: ONLINE
>   scan: scrub repaired 0 in 3h18m with 0 errors on Thu Jun 19 06:56:53 2014
> config:
>
>         NAME        STATE     READ WRITE CKSUM
>         enterprise_zdata  ONLINE       0     0     0
>           raidz1-0  ONLINE       0     0     0
>             ada2    ONLINE       0     0     0
>             ada3    ONLINE       0     0     0
>             ada4    ONLINE       0     0     0
>
> errors: No known data errors
>
>   pool: enterprise_zroot
>  state: ONLINE
>   scan: scrub repaired 0 in 1h9m with 0 errors on Thu Jun 19 04:48:05 2014
> config:
>
>         NAME        STATE     READ WRITE CKSUM
>         enterprise_zroot  ONLINE       0     0     0
>           mirror-0  ONLINE       0     0     0
>             ada0p3  ONLINE       0     0     0
>             ada1p3  ONLINE       0     0     0
>
> errors: No known data errors
>
> --
> ----------------------------------------------------------------------
> Trond Endrestøl                     |     [email protected]
> ACM, NAS, NUUG, SAGE, USENIX        |    FreeBSD 9.3-PRE & Alpine 2.11
> _______________________________________________
> developer mailing list
> [email protected]
> http://lists.open-zfs.org/mailman/listinfo/developer
>
>
_______________________________________________
developer mailing list
[email protected]
http://lists.open-zfs.org/mailman/listinfo/developer

Reply via email to