Linux Disk IO

[Hari Sekhon]

If you try looking at vgs or lvs you'll fail, iostat will output no stats.

You can either look at the underlying pvs or the dms.

So figure out what your lvm is sitting on and look at that.

Running iostat without specifying targets will list all your relevant 
underlying partitions which will make it easier for you to see what you 
have. Then if you're interested in something particular and you know 
what the mapping is then you can focus on that.

-h

Nair wrote:
>
> Thank you Hari
>
> Could not find anything of same.
>
> Also, is thr any option in iostat to find Disk IO for a particular 
> volume group.(i know this is not the right forum, but still asking :)) 
>
> Regards,
> Nair
>
>
> On Thu, 31 Jul 2008 Hari Sekhon wrote :
> >Nair wrote:
> >>
> >>Friends,
> >>
> >>Any got Nagios Plugin for monioting Linux Disk IO for a particular 
> volume group.
> >>
> >>I mean, something similar to iostat. :) Not sure how to use iostat 
> to find out Disk IO for a given Volume Group.
> >>
> >Have you searched nagiosexchange.org? If there is no check_iostat or 
> similar, it should be simple to write a wrapper around iostat to check 
> this.
> >
> >I use iostat quite a lot in fact, especially on my heavier used 
> servers so this is quite interesting to me.
> >
> >Let me know how you get along.
> >
> >If there is nothing very good right now, I may put this on my (very 
> long) todo list for writing this plugin.
> >
> >-h
> >
> >-- Hari Sekhon
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null