Linux LVM users
 help / color / mirror / Atom feed
From: Michael Holschbach <m_holschbach@yahoo.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] missing vg after reboot
Date: Mon, 10 Sep 2001 08:49:03 -0700 (PDT)	[thread overview]
Message-ID: <20010910154903.33297.qmail@web13902.mail.yahoo.com> (raw)
In-Reply-To: <20010910131203.C31313@sistina.com>

--- "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
> 
> Michael,
> 
> the pvdata output below exposes a completely messy PV structure,
> which makes me think of 2 possible reasons:
> 
> a. /dev/hda2 is not the device you used to create a physical volume
> 
> b. something accidentially overwrote /dev/hda2 after the PV creation
> 
> 
> If b is true you might still have an actual VGDA backup in
> /etc/lvmconf/ which
> you can use to vgcfgrestore(8) it to /dev/hda2 presumed that
> /dev/hda2 is
> the right device.
> 
I already tried vgcfgrestore. All available backup files lead to the
same result:
 
> > server1:~ # vgcfgrestore -v -n data /dev/hda2
> > vgcfgrestore -- locking logical volume manager
> > vgcfgrestore -- restoring volume group "data" from
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- checking existence of
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- reading volume group data for "data"
> > from "/etc/lvmconf/data.con
> > f"
> > vgcfgrestore -- reading physical volume data for
> > "data" from "/etc/lvmconf/data.
> > conf"
> > vgcfgrestore -- reading logical volume data for "data"
> > from "/etc/lvmconf/data.c
> > onf"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- reading physical volume "/dev/hda2"
> > vgcfgrestore -- ERROR "pv_read(): PV identifier
> > invalid" reading physical volume
> >  "/dev/hda2"
> > 
My idea was to reset the values of /dev/hda2 according to the following
settings:

> > server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
...
> > --- Physical volume ---
> > PV Name               /dev/hda2
> > VG Name               data
> > PV Size               27.62 GB / NOT usable 2.48 MB
> > [LVM: 148 KB]
> > PV#                   2
> > PV Status             available
> > Allocatable           yes
> > Cur LV                6
> > PE Size (KByte)       4096
> > Total PE              7069
> > Free PE               669
> > Allocated PE          6400
> > PV UUID              
> > e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW
> > 

These values seem plausible for me. Can i use them to manually edit the
PV /dev/hda2 to rescue some data? 


MfG Michael

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

  reply	other threads:[~2001-09-10 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 22:13 [linux-lvm] missing vg after reboot Michael
2001-09-10 11:12 ` Heinz J . Mauelshagen
2001-09-10 15:49   ` Michael Holschbach [this message]
2001-09-11  2:38     ` IT3 Stuart B. Tener, USNR-R
2001-09-11  3:46       ` Erick Calder
2001-09-11  4:10         ` IT3 Stuart B. Tener, USNR-R
2001-09-11  4:51         ` Glenn Shannon
2001-09-11 14:18     ` Heinz J . Mauelshagen

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=20010910154903.33297.qmail@web13902.mail.yahoo.com \
    --to=m_holschbach@yahoo.com \
    --cc=linux-lvm@sistina.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