All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rainer Hoerbe <rhoerbe@netpromote.co.at>
To: linux-lvm@redhat.com
Subject: [linux-lvm] PV not reconized after vgcfgrestore?
Date: Sat, 28 Aug 2004 21:52:38 +0200	[thread overview]
Message-ID: <4130E286.80606@netpromote.co.at> (raw)

After my a system (lvm 1.0.6) hung, volume group data (out of 2) 
disappeard. There were no IO-errors in the system log.

A pvscan will not show the lost PV, and vgimport tells:
vgimport -- ERROR "pv_read(): PV identifier invalid" reading physical 
volume "/dev/hde1"

Now, when I try to restore, it should fix the PV in my understanding. 
But pvscan still does not bring it back. What could I do?

Your help is appreciated, as it would save me a day of work since the 
last backup :-)
Rainer Hoerbe


# vgcfgrestore -l -l -n data /dev/hde1
vgcfgrestore -- INFO: using backup file "/etc/lvmconf/data.conf"
--- Volume group ---
VG Name               data
VG Access             read/write
VG Status             NOT available/resizable
VG #                  1
MAX LV                256
Cur LV                3
Open LV               0
MAX LV Size           255.99 GB
Max PV                256
Cur PV                1
Act PV                1
VG Size               149.04 GB
PE Size               4 MB
Total PE              38153
Alloc PE / Size       38145 / 149 GB
Free  PE / Size       8 / 32 MB
VG UUID               RGvrGj-qVpF-e3ke-n17z-oQAx-g3c6-WHvNYu

--- Logical volume ---
LV Name                /dev/data/m-data
VG Name                data
LV Write Access        read/write
LV Status              NOT available
LV #                   1
# open                 0
LV Size                80 GB
Current LE             20480
Allocated LE           20480
Allocation             next free
Read ahead sectors     1024
Block device           58:1

--- Logical volume ---
LV Name                /dev/data/e-data
VG Name                data
LV Write Access        read/write
LV Status              NOT available
LV #                   2
# open                 0
LV Size                5.20 GB
Current LE             1332
Allocated LE           1332
Allocation             next free
Read ahead sectors     1024
Block device           58:2

--- Logical volume ---
LV Name                /dev/data/video
VG Name                data
LV Write Access        read/write
LV Status              NOT available
LV #                   3
# open                 0
LV Size                63.80 GB
Current LE             16333
Allocated LE           16333
Allocation             next free
Read ahead sectors     1024
Block device           58:3


--- Physical volume ---
PV Name               /dev/hde1
VG Name               data
PV Size               149.04 GB [312560577 secs] / NOT usable 4.31 MB 
[LVM: 277 KB]
PV#                   1
PV Status             available
Allocatable           yes
Cur LV                3
PE Size (KByte)       4096
Total PE              38153
Free PE               8
Allocated PE          38145
PV UUID               y5rlkX-JZy2-yukW-8hkA-xeoh-U8qe-ulpuMs

                 reply	other threads:[~2004-08-28 19:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4130E286.80606@netpromote.co.at \
    --to=rhoerbe@netpromote.co.at \
    --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.