linux-lvm.redhat.com archive mirror
 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 22:45:39 -0500	[thread overview]
Message-ID: <20061115034539.GA5315@bdmcc-us.com> (raw)
In-Reply-To: <20061115013248.GA4251@bdmcc-us.com>

On Tue, Nov 14, 2006 at 08:32:48PM -0500, Brian McCullough wrote:
> On Tue, Nov 14, 2006 at 11:06:58PM +0000, Alasdair G Kergon wrote:
> > On Tue, Nov 14, 2006 at 06:00:03PM -0500, Brian McCullough wrote:
> > >   Internal error: PV segments corrupted in vg_system.
> > 
> > First update your lvm2 software to avoid that bug: you shouldn't
> > see internal errors!

OK, I went to the source and compiled the latest version of both the
library and LVM2.

Versions:

[root@clachan ~]# lvm version
  LVM version:     2.02.06 (2006-05-12)
  Library version: 1.02.12 (2006-10-13)
  Driver version:  4.6.0


pvscan:

[root@clachan ~]# 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.



Do I need to rebuild my kernel, too?

B-)

  reply	other threads:[~2006-11-15  3:45 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
2006-11-14 23:06       ` Alasdair G Kergon
2006-11-15  1:32         ` Brian McCullough
2006-11-15  3:45           ` Brian McCullough [this message]
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=20061115034539.GA5315@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).