All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Inconsistent VG
Date: Wed, 12 Dec 2007 15:21:52 +0000	[thread overview]
Message-ID: <475FFC90.6050903@redhat.com> (raw)
In-Reply-To: <5485940d0712120657t54d848a0l5f40bdc209ce2d6a@mail.gmail.com>

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

      reply	other threads:[~2007-12-12 15:21 UTC|newest]

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

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=475FFC90.6050903@redhat.com \
    --to=breeves@redhat.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 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.