From: Adam McDaniel <adamm@array.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] accidently formatted a physical volume...
Date: Tue Aug 20 12:56:01 2002 [thread overview]
Message-ID: <20020820175543.GA8709@grimlock> (raw)
In-Reply-To: <3D6159EA.1070406@birddog.com>
[-- Attachment #1: Type: text/plain, Size: 2732 bytes --]
On Mon, Aug 19, 2002 at 03:49:46PM -0500, Kirby C. Bohling wrote:
> I'd imagine that doing a vgcfgrestore to the device, followed by
> mounting the filesystem without fsck'ing it will get you some data.
Unfortunatly, I don't have any data for vgcfgrestore to build upon.
Here's the current status:
/dev/loop0 is pointing to /root/lvm/hde1
/dev/loop1 is pointing to /root/lvm/hdf1
(built via 'dd if=/dev/hd?1 of=/root/lvm/hd?1')
/dev/loop0 is the good image
/dev/loop1 is the fubar'd one.
pvdisplay /dev/loop0:
---
PV Name /dev/loop0
VG Name data
PV Size 14.31 GB [30009357 secs] / NOT usable 1.01 MB [LVM: 135 KB]
PV# 2
PV Status available
Allocatable yes (but full)
Cur LV 1
PE Size (KByte) 4096
Total PE 3663
Free PE 0
Allocated PE 3663
PV UUID 3IRYim-Lpgb-2N1Y-6TPu-C8mZ-58hy-exlmBm
---
pvdisplay /dev/loop1:
---
PV Name /dev/loop1
VG Name data
PV Size 9.44 GB [19792017 secs] / NOT usable 4.07 MB [LVM: 130 KB]
PV# 1
PV Status available
Allocatable yes (but full)
Cur LV 1
PE Size (KByte) 4096
Total PE 2415
Free PE 0
Allocated PE 2415
PV UUID P7xAxa-J36q-2C8i-2vKc-5KJO-2tQ6-H3eGiz
---
First I tried running pvscan:
---
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/loop0" is associated to unknown VG "data" (run vgscan)
pvscan -- inactive PV "/dev/loop1" is associated to unknown VG "data" (run vgscan)
pvscan -- total: 2 [23.75 GB] / in use: 2 [23.75 GB] / in no VG: 0 [0]
---
fair enough.. so I run 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
---
ofcourse /etc/lvmtab and /etc/lvmtab.d/* are all blank/empty.
If anything, I'm just about at the point where the dead drive is a
writeoff (/dev/loop1).. but I would like to try to salvage the data on
/dev/loop0
Any ideas?
Thanks.
--
Adam McDaniel
Array Networks
Calgary, AB, Canada
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-08-20 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 14:23 [linux-lvm] accidently formatted a physical volume Adam McDaniel
2002-08-19 14:38 ` Steven Lembark
[not found] ` <284650000.1029786116@[192\.168\.200\.4]>
2002-08-19 15:42 ` Anders Widman
2002-08-19 15:50 ` Adam McDaniel
2002-08-19 15:58 ` Kirby C. Bohling
2002-08-20 12:56 ` Adam McDaniel [this message]
2002-08-20 13:29 ` Kirby C. Bohling
2002-08-20 13:55 ` Andreas Dilger
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=20020820175543.GA8709@grimlock \
--to=adamm@array.org \
--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