linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: tariq wali <ganaiwali@gmail.com>
Subject: Re: [linux-lvm] LVM2 recovery on IP-SAN after OS re-install
Date: Tue, 19 Jun 2012 17:40:50 +0100	[thread overview]
Message-ID: <4FE0AB92.7020400@redhat.com> (raw)
In-Reply-To: <CAGQjrKZ0CD7O8_KYBd+KvBmK0nnxxoWc+5sm0Pk+XYkZEq3vOQ@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/28/2012 07:40 PM, tariq wali wrote:
> I tried to fix this by but it just won't go.. vgreduce
> --removemissing vg0 Found duplicate PV
> XtGmeFOiCTWpLBckKZKlGtYKPVdBgVJn: using /dev/sdd1 not /dev/sdc1 
> Volume group "vg0" is already consistent
> 
> why does LVM think that it's still using PV ( /dev/sdc1 ) when it
> no more exists ? and how do i get rid of it ?

Although you have removed the PV from the volume group it still has a
PV label on it which has the same UUID value as some other valid
device that is part of the volume group.

You should verify which device is correct and then remove the PV label
from the other device (or re-run pvcreate to give it a new random UUID):

# pvremove /dev/sdc1

Once the label is removed you should stop seeing those messages.

Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/gq5EACgkQ6YSQoMYUY97zTACdEn2l2OkwM/4naoqzZwJFDSiO
WpYAnjSN8Uppia//lZK28FnhXvyDwK+Y
=v7ST
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2012-06-19 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28 18:40 [linux-lvm] LVM2 recovery on IP-SAN after OS re-install tariq wali
2012-05-29  9:14 ` James Hawtin
2012-06-19 16:40 ` Bryn M. Reeves [this message]
2012-06-20 10:06   ` tariq wali

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=4FE0AB92.7020400@redhat.com \
    --to=bmr@redhat.com \
    --cc=ganaiwali@gmail.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).