From: Ron Johnson <ron.l.johnson@cox.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] vgs result code error
Date: Tue, 21 Jul 2009 04:41:46 -0500 [thread overview]
Message-ID: <4A658D5A.7060205@cox.net> (raw)
In-Reply-To: <38bdcd1f0907210208g19b3a803j90e43a4ce8f6b301@mail.gmail.com>
On 2009-07-21 04:08, Masanari Iida wrote:
> Thanks for reply.
>
>> You specified a PV, not a VG. Try:
>> # vgs vg01
>
> Yes I know it should work.
>
> # vgs vg01
> VG #PV #LV #SN Attr VSize VFree
> vg01 1 0 0 wz--n- 3.82G 3.82G
>
>
> The point I want to say is, vgs command _should_ return non-zero
> exit status value, if vgs command returned an error.
Sorry.
> Reference: man lvm(8)
>
> DIAGNOSTICS
> All tools return a status code of zero on success or non-zero on fail-
> ure.
[snip]
> I have found this bug on RHEL5 (which uses lvm2.02.40-6) and
> I have checked out WHATS_NEW between 2.02-40 to 49,
> so far no similar symptom.
Debian Sid's 2.02.44-3 returns a non-zero code, so either RH fixed
it upstream, or Debian patched it...
# vgs --version
WARNING: Ignoring duplicate config node: filter (seeking filter)
LVM version: 2.02.44 (2009-01-26)
Library version: 1.02.30 (2009-01-26)
Driver version: 4.14.0
# vgs /dev/sdc1
WARNING: Ignoring duplicate config node: filter (seeking filter)
Volume group "sdc1" not found
# echo $?
5
--
Scooty Puff, Sr
The Doom-Bringer
next prev parent reply other threads:[~2009-07-21 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 7:16 [linux-lvm] vgs result code error Masanari Iida
2009-07-21 8:27 ` Ron Johnson
2009-07-21 9:08 ` Masanari Iida
2009-07-21 9:41 ` Ron Johnson [this message]
2009-07-21 10:35 ` Alasdair G Kergon
2009-07-21 10:48 ` Ron Johnson
2009-07-21 11:49 ` Masanari Iida
2009-07-23 7:44 ` Masanari Iida
2009-07-23 9:28 ` Masanari Iida
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=4A658D5A.7060205@cox.net \
--to=ron.l.johnson@cox.net \
--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).