linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ray Van Dolson <rvandolson@esri.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!
Date: Tue, 21 Jul 2009 14:59:13 -0700	[thread overview]
Message-ID: <20090721215913.GA32225@esri.com> (raw)
In-Reply-To: <2473b43f0907211424o209e52ccj9223295a328220d3@mail.gmail.com>

On Tue, Jul 21, 2009 at 02:24:26PM -0700, Adam Olsen wrote:
> On Tue, Jul 21, 2009 at 3:07 PM, Ray Van Dolson<rvandolson@esri.com> wrote:
> > Very strange... a few more commands:
> >
> > vgs -P -o +devices
> > lvs -P -a -o +devices
> 
> imgserv:/storage/# vgs -P -o +devices
>   Partial mode. Incomplete volume groups will be activated read-only.
>   VG      #PV #LV #SN Attr   VSize VFree Devices
>   storage   3   1   0 wz--n- 3.62T 4.98G /dev/sda3(0)
>   storage   3   1   0 wz--n- 3.62T 4.98G /dev/sdb1(0)
>   storage   3   1   0 wz--n- 3.62T 4.98G /dev/sdc1(0)
> imgserv:/storage/# lvs -P -a -o +devices
>   Partial mode. Incomplete volume groups will be activated read-only.
>   LV      VG      Attr   LSize Origin Snap%  Move Log Copy%  Convert
> Devices
>   storage storage -wi-i- 3.62T
> /dev/sda3(0)
>   storage storage -wi-i- 3.62T
> /dev/sdb1(0)
>   storage storage -wi-i- 3.62T
> /dev/sdc1(0)
> 
> > If you want, post the lvmdump tarball somewhere...
> 
> http://www.exaile.org/lvmdump.tar.gz

Maybe someone else could take a look as well.  Some of the LVM metadata
files in the archive directory appear to be missing logical_volumes {}
sections.

I wonder if this could be fixed with a simple 

  vgcfgrestore -f /etc/lvm/backup/storage storage
  vgscan
  vgchange -ay storage

Also it looks like some of the older archived versions would be valid
as well.

  vgcfgrestore -l storage

Should give a list...

> 
> > When did this start happening?
> 
> This morning.  5am MST.

Ray

  reply	other threads:[~2009-07-21 21:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 19:55 [linux-lvm] Can't mount or run fdisk on an existing logical volume, help! Adam Olsen
2009-07-21 19:58 ` Ray Van Dolson
2009-07-21 20:01   ` Adam Olsen
2009-07-21 20:07     ` Ray Van Dolson
2009-07-21 20:29       ` Adam Olsen
2009-07-21 20:35         ` Ray Van Dolson
2009-07-21 20:46           ` Sven Eschenberg
2009-07-21 20:47           ` Adam Olsen
2009-07-21 21:07             ` Ray Van Dolson
2009-07-21 21:24               ` Adam Olsen
2009-07-21 21:59                 ` Ray Van Dolson [this message]
2009-07-21 22:09                   ` Adam Olsen
2009-07-21 22:21                     ` Ray Van Dolson
2009-07-21 22:43                       ` Adam Olsen
2009-07-21 22:50                         ` Ray Van Dolson
2009-07-22 13:08                     ` Bryn M. Reeves
2009-07-24  1:38                     ` Ron Johnson
2009-07-22 13:17     ` Bryn M. Reeves
2009-07-22  5:26   ` Ron Johnson
2009-07-22  5:41     ` Adam Olsen
2009-07-22  5:49       ` Ron Johnson
2009-07-22  6:01         ` Adam Olsen
2009-07-22 15:42           ` Sven Eschenberg
2009-07-22 16:49             ` Bryn M. Reeves
2009-07-23 23:42               ` Adam Olsen
2009-07-22 13:06       ` Bryn M. Reeves
2009-07-22 13:05     ` 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=20090721215913.GA32225@esri.com \
    --to=rvandolson@esri.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).