All of lore.kernel.org
 help / color / mirror / Atom feed
From: kelsey hudson <khudson@tsss.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Hosed up arrays and LVM
Date: Sun, 20 Nov 2005 09:38:50 -0800	[thread overview]
Message-ID: <4380B4AA.5080705@tsss.org> (raw)
In-Reply-To: <1132507550.24931.29.camel@joesgrill.cc.vt.edu>

Bill Ranck wrote:
> It continues on like that with another volume group and different uuids.
> I have /dev/md0 through /dev/md11 defined with md and some of those seem
> OK, but md1, md2, md3, md4, md8, md9, md11 are not seen by vgscan.  I
> tried pvcreate on those missing arrays, which made them visible, but LVM
> does not recognize them as part of the volume groups they belong to
> anymore.  
> 
> Can anyone suggest a course of action here?

ouch, you ran pvcreate on a volume which already had data on it? From 
all I've read, you had better have a good backup laying around, 'cause 
you may not be able to get that data back pvcreate, IIRC, wipes out the 
metadata ...

If you have the old UUIDs for the physical volumes, you may be able to 
write those back to the device using pvcreate -u <old-uuid> on each such 
PV, then try vgscan again.

but, as from the man page:

    You can not recreate (reinitialize)  a  physical  volume  belonging
    to  an existing  volume  group.

so, you may be out of luck. But, good luck anyways ...

-kelsey

  reply	other threads:[~2005-11-20 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20 17:25 [linux-lvm] Hosed up arrays and LVM Bill Ranck
2005-11-20 17:38 ` kelsey hudson [this message]
2005-11-22 14:14   ` Bill Ranck

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=4380B4AA.5080705@tsss.org \
    --to=khudson@tsss.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.