All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian McCullough <bdmc@bdmcc-us.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] How to restore a PV ??
Date: Tue, 14 Nov 2006 18:00:03 -0500	[thread overview]
Message-ID: <20061114230003.GA3401@bdmcc-us.com> (raw)
In-Reply-To: <01dbd6887fd9d439599e31bda27f3883@redhat.com>

I am having a similar problem with a drive that was created under LVM
version 1.  More questions below.


On Mon, Oct 16, 2006 at 02:20:14PM -0500, Jonathan E Brassow wrote:
> On each disk in the volume group is a record of the changes that have 
> been made to the volume group.  The last item in the record is the 
> current lvm meta-data.  If you can retrieve that, it is the same as 
> having the backup file which would normally be found in 
> /etc/lvm/backup.
> 
> You could use hexdump, but I find it much simpler to use 'less -f 
> <device>'.  You should see something like:
> 
> <crap>
> principal {
> ...
> }
> <comments>
> <crap>
> principal {
> ...
> }
> <comments>
> <crap>


Is this also true for LVM1?  I have examined the disk ( there are 5 LVs
on this disk, one elsewhere ( nowhere! ) ) and it doesn't seem to follow
this format.

If this is not true, is there any way to recover such a Volume Group?

Here is what vgscan and pvscan show:

[root@clachan media]# pvscan
  5 PV(s) found for VG vg_system: expected 6
  Logical volume (lvol4) contains an incomplete mapping table.
  PV segment VG free_count mismatch: 1381 != 2572
  PV segment VG extent_count mismatch: 1417 != 2608
  Internal error: PV segments corrupted in vg_system.
[root@clachan media]# vgscan
  Reading all physical volumes.  This may take a while...
  5 PV(s) found for VG vg_system: expected 6
  5 PV(s) found for VG vg_system: expected 6
  Volume group "vg_system" not found
[root@clachan media]# vgchange -a y --partial vg_system
  Partial mode. Incomplete volume groups will be activated read-only.
  5 PV(s) found for VG vg_system: expected 6
  Logical volume (lvol4) contains an incomplete mapping table.
  PV segment VG free_count mismatch: 1381 != 2572
  PV segment VG extent_count mismatch: 1417 != 2608
  Internal error: PV segments corrupted in vg_system.
  Unable to find volume group "vg_system"


I do have several copies of the config file, also on this drive ( in a
real ext2 partition! ).  Could I just edit the file to remove lvol4 (
with 250 segments! ) and do a vgcfgrestore from an LVM2 system?


Thank you,
Brian

  reply	other threads:[~2006-11-14 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13  1:27 [linux-lvm] How to restore a PV ?? Jerome
2006-10-16 15:43 ` Jonathan E Brassow
2006-10-16 15:57 ` Jerome
2006-10-16 19:20   ` Jonathan E Brassow
2006-11-14 23:00     ` Brian McCullough [this message]
2006-11-14 23:06       ` Alasdair G Kergon
2006-11-15  1:32         ` Brian McCullough
2006-11-15  3:45           ` Brian McCullough
2006-11-17 13:44         ` Brian McCullough
2006-11-17 19:21           ` Alasdair G Kergon
2006-11-18 10:24             ` 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=20061114230003.GA3401@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.