Guys,
# zpool iostat pool1
capacity operations bandwidth
pool used avail read write read write
---------- ----- ----- ----- ----- ----- -----
pool1 822M 927G 0 0 435 28.2K
In which units is bandwidth measured?
I suppose capital K means Byte but Im not sure.
Anyway abbreviation for mega is only capital M.
Docs just say:
WRITE BANDWIDTH The bandwidth of all write operations, expressed as units per
second.
Thanks!
/M
--
This message posted from opensolaris.org
answer for your questions:
usr/src/cmd/zpool/zpool_main.c
} else {
print_one_stat(newvs->vs_alloc);
print_one_stat(newvs->vs_space - newvs->vs_alloc);
}
print_one_stat((uint64_t)(scale * (newvs->vs_ops[ZIO_TYPE_READ] -
oldvs->vs_ops[ZIO_TYPE_READ])));
print_one_stat((uint64_t)(scale * (newvs->vs_ops[ZIO_TYPE_WRITE] -
oldvs->vs_ops[ZIO_TYPE_WRITE])));
print_one_stat((uint64_t)(scale * (newvs->vs_bytes[ZIO_TYPE_READ] -
oldvs->vs_bytes[ZIO_TYPE_READ])));
print_one_stat((uint64_t)(scale * (newvs->vs_bytes[ZIO_TYPE_WRITE] -
oldvs->vs_bytes[ZIO_TYPE_WRITE])));
usr/src/uts/common/sys/fs/zfs.h
/*
* Vdev statistics. Note: all fields should be 64-bit because this
* is passed between kernel and userland as an nvlist uint64 array.
*/
typedef struct vdev_stat {
hrtime_t vs_timestamp; /* time since vdev load */
uint64_t vs_state; /* vdev state */
uint64_t vs_aux; /* see vdev_aux_t */
uint64_t vs_alloc; /* space allocated */
uint64_t vs_space; /* total capacity */
uint64_t vs_dspace; /* deflated capacity */
uint64_t vs_rsize; /* replaceable dev size */
uint64_t vs_ops[ZIO_TYPES]; /* operation count */
uint64_t vs_bytes[ZIO_TYPES]; /* bytes read/written */
uint64_t vs_read_errors; /* read errors */
uint64_t vs_write_errors; /* write errors */
uint64_t vs_checksum_errors; /* checksum errors */
uint64_t vs_self_healed; /* self-healed bytes */
uint64_t vs_scan_removing; /* removing? */
uint64_t vs_scan_processed; /* scan processed bytes */
} vdev_stat_t;
2010/6/17 pitutek <maciej.plona at gmail.com>
> Guys,
>
> # zpool iostat pool1
> capacity operations bandwidth
> pool used avail read write read write
> ---------- ----- ----- ----- ----- ----- -----
> pool1 822M 927G 0 0 435 28.2K
>
>
> In which units is bandwidth measured?
> I suppose capital K means Byte but Im not sure.
> Anyway abbreviation for mega is only capital M.
>
> Docs just say:
> WRITE BANDWIDTH The bandwidth of all write operations, expressed as units
> per second.
>
> Thanks!
>
> /M
> --
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100617/9fe0c773/attachment.html>
Hi-- ZFS command operations involving disk space take input and display using numeric values specified as exact values, or in a human-readable form with a suffix of B, K, M, G, T, P, E, Z for bytes, kilobytes, megabytes, gigabytes, terabytes, petabytes, exabytes, or zettabytes. Thanks, Cindy On 06/17/10 05:42, pitutek wrote:> Guys, > > # zpool iostat pool1 > capacity operations bandwidth > pool used avail read write read write > ---------- ----- ----- ----- ----- ----- ----- > pool1 822M 927G 0 0 435 28.2K > > > In which units is bandwidth measured? > I suppose capital K means Byte but Im not sure. > Anyway abbreviation for mega is only capital M. > > Docs just say: > WRITE BANDWIDTH The bandwidth of all write operations, expressed as units per second. > > Thanks! > > /M
> Hi-- > > ZFS command operations involving disk space take input and display using > numeric values specified as exact values, or in a human-readable form > with a suffix of B, K, M, G, T, P, E, Z for bytes, kilobytes, megabytes, > gigabytes, terabytes, petabytes, exabytes, or zettabytes. >Let''s play a game here. :-) Suppose you wanted a 1PB zpool and you wanted dedup. How much memory would you need for that and would you separate out ZIL cache etc? I''m guessing ( total WAG ) that one would want at least 16TB of memory. I have no idea of any system out there that can pop that many 8G ECC SIMMs ( 2048 of them ) into. But really .. what sort of theoretical machine would be needed to handle a single 1024 TB zpool ? Dennis