From: Brian McCullough <bdmc@bdmcc-us.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Missing PV
Date: Thu, 26 Apr 2012 10:58:11 -0400 [thread overview]
Message-ID: <20120426145811.GA3329@bdmcc-us.com> (raw)
In-Reply-To: <20120424132419.GA2244@bdmcc-us.com>
On Tue, Apr 24, 2012 at 09:24:19AM -0400, Brian McCullough wrote:
> I have encountered a situation where vgscan and vgchange are complaining
> about a missing UUID.
>
> As far as I know, all, or almost all, of the LV is on the PV that is
> known ( how do I know for sure? ), so I think that I am trying to just
> "remove" the PV and recover what I can of the LV.
Sorry to be dense, but I don't feel confident about proceeding before I
know what the next step should be.
I am pretty sure that I can remove the "lost" PV, using the
instructions that I have found in multiple places, including the
referenced slide deck, but I have not been able to find anything about
recovering the LV that spans from the existing PV into the lost one.
Since most, if not all of the existing data from that LV is on the
"good" PV, I would hope that I can recover that filesystem. The
question is "How?"
> I have read Milan Brosz' slides from 2009, and the only piece that I
> seem to be missing is the recovery of the LV.
>
>
> I have made a copy of the PV to work with and the procedure that I need
> to follow, as I understand it, is as follows:
>
>
> vgscan
> vgchange -a y ( fails )
> vgchange -a y --partial
> vgreduce --removemissing vgname
>
> then what?
>
> I have done:
>
> pvs -o +uuid
> lvs -o +devices
>
> But am not sure how to interpret the results. lvs shows two entries for
> the LV that I am interested in. The second entry shows "unknown device(0)".
Thanks,
Brian
next prev parent reply other threads:[~2012-04-26 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 13:24 [linux-lvm] Missing PV Brian McCullough
2012-04-26 14:58 ` Brian McCullough [this message]
2012-04-26 16:47 ` Milan Broz
2012-04-26 17:23 ` Brian McCullough
2012-04-26 17:47 ` Milan Broz
2012-04-26 18:24 ` Brian McCullough
2012-04-26 19:43 ` Brian McCullough
2012-04-26 20:45 ` Milan Broz
2012-04-26 21:13 ` Brian McCullough
2012-04-27 3:08 ` Brian McCullough
2012-04-28 17:01 ` Brian McCullough
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=20120426145811.GA3329@bdmcc-us.com \
--to=bdmc@bdmcc-us.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 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.