All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jelle Herold <wires@defekt.nl>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] recover lost VG (VG data differs between PVs)
Date: Mon, 15 Nov 2004 02:27:10 +0100	[thread overview]
Message-ID: <20041115012710.GA23196@hotwire.nl> (raw)
In-Reply-To: <20041114232126.GH24229@agk.surrey.redhat.com>

On Sun, Nov 14, 2004 at 11:21:26PM +0000, Alasdair G Kergon wrote:
> >  VG data differs between PVs /dev/hde and /dev/hdf3
> >  Volume group "datavg" doesn't exist
>  
> So hde should be in the VG at the moment, but not hdf3?

Yes.

> Add a filter to lvm.conf so lvm only looks at hde.  Run
> vgscan and see check if things look OK eg vgcfgbackup and
> read the text backup file.  If things *are* OK like that,
> then pvremove hdf3, remove the filter & vgscan.

OK, I shall try that tomorrow. But a quick look at
vgdisplay -P -v shows:

 VG data differs between PVs /dev/hde and /dev/hdf3
 Partial mode. Incomplete volume groups will be activated read-only.
    Finding all volume groups
    Finding volume group "datavg"
  --- Volume group ---
  VG Name               datavg
  System ID             trigger1078793806
  Format                lvm1
  VG Access             read
  VG Status             resizable
  MAX LV                256
  Cur LV                1
  Open LV               0
  Max PV                256
  Cur PV                3
  Act PV                3
  VG Size               284.09 GB
  PE Size               32.00 MB
  Total PE              9091
  Alloc PE / Size       9091 / 284.09 GB
  Free  PE / Size       0 / 0   
  VG UUID               f49snm-PqWg-hfnp-Ms2k-dgyC-M72S-YqScuJ
   
  --- Logical volume ---
  LV Name                /dev/datavg/datalv
  VG Name                datavg
  LV UUID                000000-0000-0000-0000-0000-0000-000000
  LV Write Access        read/write
  LV Status              NOT available
  LV Size                284.09 GB
  Current LE             9091
  Segments               3
  Allocation             normal
  Read ahead sectors     1024
   
  --- Physical volumes ---
  PV Name               /dev/hde     
  PV UUID               ifxE7h-Z1c6-9mox-VYz5-XTFy-aBw2-vAkdk4
  PV Status             allocatable
  Total PE / Free PE    1831 / 0
   
  PV Name               /dev/hdg3     
  PV UUID               3AnIvc-DdzR-JqtO-hYkV-3vqw-4Qm0-FBKsCS
  PV Status             allocatable
  Total PE / Free PE    3580 / 0
   
  PV Name               /dev/hdh     
  PV UUID               oxjwHR-Cm3S-d0GZ-5LJy-xqa7-X4X6-RAzX02
  PV Status             allocatable
  Total PE / Free PE    3680 / 0

All PVs that should be in the VG are there (hdf3 was the one
I added (and removed again) later to move hde to).

So, *this* output looks OK to me as far as the PVs are
concerned, but I shall have a look at the text backup file
as you suggested. 

thanks for the help
Jelle.

  reply	other threads:[~2004-11-15  1:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-14 22:58 [linux-lvm] recover lost VG (VG data differs between PVs) Jelle Herold
2004-11-14 23:21 ` Alasdair G Kergon
2004-11-15  1:27   ` Jelle Herold [this message]
2004-11-15 10:24   ` Jelle Herold
2004-11-15 14:15     ` Alasdair G Kergon
2004-11-15 17:51       ` Jelle Herold

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=20041115012710.GA23196@hotwire.nl \
    --to=wires@defekt.nl \
    --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.