From: 張廷州 <ctc1230@ms67.hinet.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] How to recover data corrupted by vgcreate
Date: Mon, 1 Aug 2005 21:25:44 +0800 [thread overview]
Message-ID: <012601c5969c$8f7cc2f0$fa01a8c0@Notebook> (raw)
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
Hi,
There is no backup information available in /etc/lvm/archive to restore VG to original configuration.
Unfortunately the root directory is also in LVM partition.
So, "vgcfgrestore" did not solve the problem.
I also tried to create new LV by "lvcreate" to match with the existing LV.
The problem is I have no idea about the size of old LV.
I just gave a random size in "lvcreate" command.
But, I could not mount the file system because of bad superblock.
I don't know what I missed. Maybe the size is critical to do the matching.
Is there any reverse procedure I can do to recover VG by the existing LV information?
It may just like to recover partition table by scanning cylinder data in hard disk.
Any idea? Thanks a lot.
Davis
> >On Wed, Jul 27, 2005 at 11:33:05AM -0500, Jonathan E Brassow wrote:
> >>I'm not familiar exactly with how the metadata gets laid on disk, but
> >>I would think you could just 'vgcreate vg_name /dev/hdd2' (you did
> >>this
> >>already) then 'lvcreate -n <lvname> -l <max size> vg_name'... This of
> >>course assumes that the previous lv resided wholly on /dev/hdd2. Then
> >>try mounting the new lv and see what happens.
> >
> >Before you do that, try vgcfgrestore.
> >
>
> AJ, when he did the initial 'vgcreate' was part of the process to
> create a backup copy of the metadata? If so, vgcfgrestore could work.
> But otherwise, I'm not sure were the old metadata would be stored,
> since this disk is from a different machine... Seems odd to me that
> vgcreate would blow over the old vg if it knew about it. If it did not
> know (or detect the old vg), how would it know to backup the metadata?
Not sure, but if the reason the disk was moved was because a cpu went out, i'm
assuming the old root fs is also on that disk - hoping so anyway ;) If so,
the old root fs can be mounted and /etc/lvm/archive can be checked for a valid
copy of the metadata. (Assuming root wasn't on lvm...)
As to why vgcreate didn't recognize the old VG...that's very odd - not sure
what went wrong there...
[-- Attachment #2: Type: text/html, Size: 3395 bytes --]
next reply other threads:[~2005-08-01 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 13:25 張廷州 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 16:57 [linux-lvm] How to recover data corrupted by vgcreate 張廷州
2005-07-27 16:33 ` Jonathan E Brassow
2005-07-27 17:24 ` AJ Lewis
2005-07-28 15:00 ` Jonathan E Brassow
2005-07-28 16:41 ` AJ Lewis
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='012601c5969c$8f7cc2f0$fa01a8c0@Notebook' \
--to=ctc1230@ms67.hinet.net \
--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.