From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgs result code error
Date: Tue, 21 Jul 2009 11:35:11 +0100 [thread overview]
Message-ID: <20090721103511.GH32330@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4A658D5A.7060205@cox.net>
On Tue, Jul 21, 2009 at 04:41:46AM -0500, Ron Johnson wrote:
> Debian Sid's 2.02.44-3 returns a non-zero code, so either RH fixed it
> upstream, or Debian patched it...
> # vgs /dev/sdc1
> WARNING: Ignoring duplicate config node: filter (seeking filter)
> Volume group "sdc1" not found
> # echo $?
> 5
That's a *different* error case that works correctly.
Yes, I agree that the original case mentioned should give EINVALID_CMD_LINE
instead of ECMD_PROCESSED.
Alasdair
next prev parent reply other threads:[~2009-07-21 10:35 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
2009-07-21 10:35 ` Alasdair G Kergon [this message]
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=20090721103511.GH32330@agk-dp.fab.redhat.com \
--to=agk@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).