From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lBCEw0nq023060 for ; Wed, 12 Dec 2007 09:58:00 -0500 Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx3.redhat.com (8.13.1/8.13.1) with ESMTP id lBCEvdna001212 for ; Wed, 12 Dec 2007 09:57:40 -0500 Received: by rv-out-0910.google.com with SMTP id k15so236147rvb.51 for ; Wed, 12 Dec 2007 06:57:39 -0800 (PST) Message-ID: <5485940d0712120657t54d848a0l5f40bdc209ce2d6a@mail.gmail.com> Date: Wed, 12 Dec 2007 14:57:39 +0000 From: "C'est Pierre" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_28025_33150378.1197471459550" Subject: [linux-lvm] Inconsistent VG Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development ------=_Part_28025_33150378.1197471459550 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_28025_33150378.1197471459550 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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


------=_Part_28025_33150378.1197471459550--