From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] New developer question -- API
Date: Fri, 27 Apr 2007 09:50:30 +0100 [thread overview]
Message-ID: <4631B956.5020808@redhat.com> (raw)
In-Reply-To: <000001c7886d$a041fb40$e0c5f1c0$@com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John Antypas wrote:
> This has probably been asked thousands of times before, but I?ll try to
> be a good 1001 J
>
>
>
> I?m trying to write some userspace code which can determine what LV, VG
> and PV a givne file mout belongs to. Yes, I can process the output of a
> few command lines tools like this:
>
>
>
> 1. Get the mount from /proc/mounts
>
> 2. Run lvs and map that into the LVM
>
> 3. Using the LVM, run vgs and get the VG
>
> 4. Using VG, use pvs and get the PV
>
> 5. Using PV, now some knowledge about how I set things up and get
> the md
>
> 6. Run around proc some more and figure out which disks this md is on
>
>
>
> These utilities do it ? is there an API I can call to do all of this
> tracing down rather than processing shell processes?
>
You can use liblvm2cmd to get this information (the header is normally
/usr/include/lvm2cmd.h). This allows you to run LVM2 commands through a
library interface, although you will still need to parse the output as
it is the same textual format as the commands themselves provide.
On a recent enough kernel though, all the information you are interested
in is exposed directly in sysfs. Take a look at the "holders" and
"slaves" entries in subdirectories of /sys/block. There is also a
library interface (libsysfs) that provides access to the keys & values
exposed here.
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGMblW6YSQoMYUY94RAkgHAKDCwMM8R8H4H72Hpr8lsTHgyLxv8wCgsX6f
lBGTn0VeYA0M/4uTNHDr+j4=
=B9i/
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-04-27 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 1:44 [linux-lvm] New developer question -- API John Antypas
2007-04-27 8:50 ` Bryn M. Reeves [this message]
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=4631B956.5020808@redhat.com \
--to=breeves@redhat.com \
--cc=linux-lvm@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).