[linux-lvm] Inconsistent VG

[linux-lvm] Inconsistent VG

[C'est Pierre]

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

Hello everyone,

We're facing a curious inconsistency problem. From our checks, we've
concluded that vgdw2 metadata doesn't include lvol4, however, it exists,
it's created and it's mountable, altho, an lvdisplay on it fails and a
vgdisplay doesn't show it either.

  WARNING: Volume group "vgdw2" inconsistent
  --- Volume group ---
  VG Name               vgdw2
  System ID
  Format                lvm2
  Metadata Areas        25
  Metadata Sequence No  166
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                16
  Open LV               16
  Max PV                0
  Cur PV                24
  Act PV                24
  VG Size               1.84 TB
  PE Size               4.00 MB
  Total PE              483048
  Alloc PE / Size       465150 / 1.77 TB
  Free  PE / Size       17898 / 69.91 GB
  VG UUID               GTMKwf-S9Ma-34DN-9lxx-8qzb-3uML-8KxjJH

Does someone have any guesses?
Aside from that, we've checked from the lvm/archive/vgdw2_* files. The
recent-most, doesn't include lvol4. We've managed to pull the "lvol4 { }"
part from an older file and confirmed all pv's in the segment definitions
existed in the destination, but it didn't help either.


Thanks,
Pierre

[-- Attachment #2: Type: text/html, Size: 2621 bytes --]

Re: [linux-lvm] Inconsistent VG

[Bryn M. Reeves]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

C'est Pierre wrote:
> Does someone have any guesses?
> Aside from that, we've checked from the lvm/archive/vgdw2_* files. The
> recent-most, doesn't include lvol4. We've managed to pull the "lvol4 {
> }" part from an older file and confirmed all pv's in the segment
> definitions existed in the destination, but it didn't help either.

You need to find a version of the metadata that's consistent & contains
the LV that has gone "missing", then restore that using vgcfgrestore.

You should also probably look at the metadata backups for lines that
begin "description = ", as these contain the command that was run at the
time the archive was created. If your LV disappeared at some point in
the past there is a good chance this will tell you when & why.

Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHX/yQ6YSQoMYUY94RAvdEAJ97ITMjN9hFbzRWLMTc2DG0SfNzuACfW3MC
lTlIEpTQZgM4NcS978osQLM=
=oF9U
-----END PGP SIGNATURE-----