From: josv@osp.nl
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] how to determine if /dev/... is an LV?
Date: Wed, 22 Aug 2001 16:49:36 +0200 [thread overview]
Message-ID: <20010822164936.U2000@gatekeeper.osp.nl> (raw)
In-Reply-To: <20010822034425.F8742@pc.ilinx>; from 6888736b923846176364586bf2e7649f@interlinx.bc.ca on Wed, Aug 22, 2001 at 03:44:25AM -0400
Well,
You could always check the major number of the device file with
the one in /proc/devices, and see whether it is the major number
of the lvm driver. Then check whether the minor number is that
of a valid logical volume (not 0).
++Jos
And thus it came to pass that Brian J. Murrell wrote:
(on Wed, Aug 22, 2001 at 03:44:25AM -0400 to be exact)
> Hi all,
>
> This should hopefully be simple. I am modifying some code to deal
> with LVM. If I am given a device path for an LV, say, /dev/VG/1,
> programatically, how can I determine that it actually is an LV and not
> some other kind of device? The best I have come up with is:
>
> lvdisplay -D -c /dev/VG/lvol1 2>&1 | grep "^/dev/VG/lvol1" >/dev/null
>
> and testing "$?".
>
> Seems kind of "hacky" though. Is there a better way?
>
> Also, is there any relationship between the output from the lvdisplay
> and the minor number for the device?
>
> Thanx,
> b.
>
> --
> Brian J. Murrell
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Fear the Muppet! Winner of the HAL2001 Hacker Quiz...
next prev parent reply other threads:[~2001-08-22 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 7:44 [linux-lvm] how to determine if /dev/... is an LV? Brian J. Murrell
2001-08-22 14:49 ` josv [this message]
2001-08-22 16:43 ` José Luis Domingo López
2001-08-22 15:01 ` Brian J. Murrell
2001-08-23 8:11 ` Heinz J . Mauelshagen
2001-08-23 12:34 ` Keith Hopkins
2001-08-23 15:48 ` Harald Milz
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=20010822164936.U2000@gatekeeper.osp.nl \
--to=josv@osp.nl \
--cc=linux-lvm@sistina.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