On Tue, Feb 17, 2009 at 8:48 PM, Jason King wrote:
>> If a disk has two slices used for different purposes, then you need to know
>> how
>> much traffic goes to each slice so as to be able to work back to a filesystem
>> or metadevice and hence what's using it.
>
> But if you already have the fil
On Mon, Feb 16, 2009 at 4:17 PM, Jason King wrote:
> Here's what I was thinking for disk stats:
>
> Device (cXtYdZ)
In that form, or or simply enumerated? (Like sd#.)
> (not sure if there's any benefit for listing individual slices)
There is. (At least, those slices that are of non-zero size an
On Tue, Feb 17, 2009 at 2:25 PM, Peter Tribble
wrote:
> On Mon, Feb 16, 2009 at 4:17 PM, Jason King wrote:
>> Here's what I was thinking for disk stats:
>>
>> Device (cXtYdZ)
>
> In that form, or or simply enumerated? (Like sd#.)
I'd go with the cXtYdZ form -- I find the sd form to be almost us
Here's what I was thinking for disk stats:
Device (cXtYdZ) (not sure if there's any benefit for listing individual slices)
Description (Vendor, product, revision from scsi inquiry)
Read ops
Read bytes
Write ops
Write bytes
size (in bytes)
Errors:
iostat has soft, hard, and transport errors -- w
