Linux LVM users
 help / color / mirror / Atom feed
From: Daniel Barklon <dan@veddma.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] recovering from VGDA loss
Date: Fri May  2 03:13:01 2003	[thread overview]
Message-ID: <1051864754.15671.56.camel@localhost> (raw)

Hi,
    I was running lvm with one PV [/dev/hdb3], making up one GV
[/dev/data], which was completely allocated to one LV
[/dev/data/homes].  My root was a separate harddisk [/dev/hda1].  Hda is
now gone, and so is my /etc, where my VGDA was.

Is there a way for me to get at the data that is still stored on
/dev/hdb3 (I am running slackware linux 9; linux-2.4.20, lvm-1.0.6)?

When I run pvscan I get the following:

root@ved:~# pvscan -v    
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- walking through all physical volumes found
pvscan -- inactive PV "/dev/hdb3"  is associated to unknown VG "data"
(run vgscan)
pvscan -- total: 1 [13.64 GB] / in use: 1 [13.64 GB] / in no VG: 0 [0]

This suggests I run vgscan...

root@ved:~# vgscan -v    
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- scanning for all active volume group(s) first
vgscan -- reading data of volume group "data" from physical volume(s)
vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of
volume group "data" from physical volume(s)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
group

...

vgimport segfaults on me when I try to import the VG as shown:

root@ved:~# vgimport -fv data /dev/hdb3
vgimport -- locking logical volume manager
vgimport -- checking volume group name
vgimport -- checking volume group "data" existence
vgimport -- trying to read physical volume
vgimport -- checking for duplicate physical volumes
vgimport -- checking physical volume name "/dev/hdb3"
vgimport -- reading data of physical volume "/dev/hdb3" from disk
vgimport -- checking for exported physical volume "/dev/hdb3"
vgimport -- checking consistency of physical volume "/dev/hdb3"
vgimport -- reallocating memory
Segmentation fault

"pvdata -P /dev/hdb3" yields

--- Physical volume ---
PV Name               /dev/hdb3
VG Name               data
PV Size               13.64 GB [28611765 secs] / NOT usable 4.19 MB
[LVM: 141 KB]
PV#                   1
PV Status             NOT available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              3491
Free PE               0
Allocated PE          3491
PV UUID               gdtjvf-8UHQ-SbSF-zmaG-7E0z-5olx-cCQRrI



Any help will be greatly appreciated.  I am still sifting through the
linux-lvm archive, but I can't seem to find a case that resmbles mine
closely enough...

Thanks,

-- 
Daniel Barklon <dan@veddma.com>

                 reply	other threads:[~2003-05-02  3:13 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=1051864754.15671.56.camel@localhost \
    --to=dan@veddma.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