linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Maurizio Marini Gmail <marini.maurizio@gmail.com>, maumar@datalogica.com
Subject: Re: [linux-lvm] vgextend path to device should'n be allowed
Date: Sun, 20 Dec 2009 19:43:27 +0100	[thread overview]
Message-ID: <4B2E704F.3090208@redhat.com> (raw)
In-Reply-To: <784f9de10912200601o69fbbf58r155eccd0f11eb287@mail.gmail.com>

On 12/20/2009 03:01 PM, Maurizio Marini Gmail wrote:
> IMHO, vgextend should check input and deny operation on a device instead of a
> volume group name; it should abort with an error,
...

> After extending whic /dev/sdc of 80G using wrong statement:
> vgextend /dev/mapper/VolGroup01 /dev/sdc

this works correctly with recent version of lvm2 (despite the strange syntax).

Please can you try to upgrade lvm2 (to RHEL/CentOS 5.4 version, the reported
version is from 5.3) and try it again (bu after restoring correct metadata)?

> Now, to fix it, can I issue:
> vgreduce --force  --removemissing VolGroup01

The best is revert metadata to version before the failed operation
(you pasted the correct version above:-) using vgcfgrestore command.

(The whole problem is stored "MISSING" flag in metadata, you can
also use last metadata backup, remove that flag manually and restore this
edited version.)

Milan
--
mbroz@redhat.com

      reply	other threads:[~2009-12-20 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 14:01 [linux-lvm] vgextend path to device should'n be allowed Maurizio Marini Gmail
2009-12-20 18:43 ` Milan Broz [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=4B2E704F.3090208@redhat.com \
    --to=mbroz@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=marini.maurizio@gmail.com \
    --cc=maumar@datalogica.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).