From: "John Antypas" <ja@s21.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] New developer question -- API
Date: Thu, 26 Apr 2007 18:44:32 -0700 [thread overview]
Message-ID: <000001c7886d$a041fb40$e0c5f1c0$@com> (raw)
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
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?
[-- Attachment #2: Type: text/html, Size: 4762 bytes --]
next reply other threads:[~2007-04-27 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 1:44 John Antypas [this message]
2007-04-27 8:50 ` [linux-lvm] New developer question -- API Bryn M. Reeves
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='000001c7886d$a041fb40$e0c5f1c0$@com' \
--to=ja@s21.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).