From: Matt Zimmerman <mdz@debian.org>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Need help with PV recovery
Date: Mon Dec 31 02:13:02 2001 [thread overview]
Message-ID: <20011231081542.GO1965@alcor.net> (raw)
In-Reply-To: <20011231004824.D12868@lynx.no>
On Mon, Dec 31, 2001 at 12:48:24AM -0700, Andreas Dilger wrote:
> So, what you need to do (approximately) is (bPV = broken PV):
> # restore the LVM magic at the start of the PV (probably OK, but why not)
> dd if=/dev/<some other PV> bs=1 count=4 of=<bPV>
> # restore the UUID (obviously broken)
> echo -e "EffefHZmr5gMrsrUEM6CkDRRZC1ragTp\0" | dd bs=1 seek=44 count=33 of=<bPV>
> # restore the VG name (looks to be missing)
> echo -e "<vgname>\0" | dd bs=1 seek=172 count=<length of vgname + 1>
These three things are more or less what I did by hand, but it looks like I
must have fat-fingered something, because when I do it this way, it seems to
work (!).
> According to the UUID list, this _should_ be PV #2, is that correct? Hard
> to see if the "system id" is OK, but I'm not sure if it is important.
> What about the output of "pvdata -PP <bPV>"? I _assume_ that the PV
> location data is OK, or you wouldn't be getting anything from the PE and
> LV lists, but it is hard to tell for sure.
Yes, I think it was originally PV #2. LVM doesn't seem to mind having it
show up as PV #0, though, as I am now able to activate the volume group and
access all of the LVs. Since I have enough free space in the volume group
to pvmove everything off of the damaged PV, I am doing that right now, after
which I will recreate it fresh, to be safe.
Thanks very much for your help.
--
- mdz
prev parent reply other threads:[~2001-12-31 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-30 17:38 [linux-lvm] Need help with PV recovery Matt Zimmerman
2001-12-31 1:47 ` Andreas Dilger
2001-12-31 2:13 ` Matt Zimmerman [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=20011231081542.GO1965@alcor.net \
--to=mdz@debian.org \
--cc=adilger@turbolabs.com \
--cc=linux-lvm@sistina.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