From: Ceri Storey <ceri.storey@dsvr.co.uk>
To: russell@coker.com.au
Cc: linux-lvm@redhat.com
Subject: [linux-lvm] Re: Linux LVM snmp MIB.
Date: Wed, 27 Jul 2005 11:26:33 +0100 [thread overview]
Message-ID: <42E76159.5050808@dsvr.co.uk> (raw)
In-Reply-To: <200507252245.13317.russell@coker.com.au>
Russell Coker wrote:
> On Monday 25 July 2005 19:38, Ceri Storey <ceri.storey@dsvr.co.uk> wrote:
> It's been ages since I looked at that. Nothing that I devised became
> official. It would be best if someone else took over that, I'm sure that
> Wichert would be happy to delegate it to someone else instead of me.
>
> Any volunteers? Ceri, maybe you should do this.
Fair enough; although I'd welcome feedback. Also, I only really plan to
do monitoring of logical volumes for the moment.
Here's a preliminary suggestion (LVM standing for 1.3.6.1.4.1.9586.100.1)
NAME
LVM.physicalVolume LVM.1
LVM.volumeGroup LVM.2
LVM.volumeGroup.groupName LVM.2.1
LVM.volumeGroup.extentSize LVM.2.2 The size of each extent in bytes
LVM.volumeGroup.extentCount LVM.2.3
LVM.volumeGroup.extentFree LVM.2.4
LVM.volumeGroup.writable LVM.2.5
LVM.volumeGroup.resizeable LVM.2.6
LVM.volumeGroup.exported LVM.2.7
LVM.volumeGroup.partial LVM.2.8
LVM.logicalVolume LVM.3 A table of devices
LVM.logicalVolume.volumeName LVM.3.1
LVM.logicalVolume.volumeGroup LVM.3.2
LVM.logicalVolume.extentCount LVM.3.3 the number of extents in this volume
LVM.logicalVolume.reads LVM.3.4 the number of extents in this volume
LVM.logicalVolume.writes LVM.3.5 the number of extents in this volume
Comments? Suggestions?
--
ceri.storey@dsvr.co.uk (Ceri Storey)
Systems Administrator
next prev parent reply other threads:[~2005-07-27 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 9:38 [linux-lvm] Linux LVM snmp MIB Ceri Storey
2005-07-25 12:45 ` [linux-lvm] " Russell Coker
2005-07-27 10:26 ` Ceri Storey [this message]
2005-07-27 11:32 ` Russell Coker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42E76159.5050808@dsvr.co.uk \
--to=ceri.storey@dsvr.co.uk \
--cc=linux-lvm@redhat.com \
--cc=russell@coker.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.