linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "C'est Pierre" <cestpierre@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Inconsistent VG
Date: Wed, 12 Dec 2007 14:57:39 +0000	[thread overview]
Message-ID: <5485940d0712120657t54d848a0l5f40bdc209ce2d6a@mail.gmail.com> (raw)

[-- 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 --]

             reply	other threads:[~2007-12-12 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 14:57 C'est Pierre [this message]
2007-12-12 15:21 ` [linux-lvm] Inconsistent VG Bryn M. Reeves

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=5485940d0712120657t54d848a0l5f40bdc209ce2d6a@mail.gmail.com \
    --to=cestpierre@gmail.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).