From: Andreas Dilger <adilger@clusterfs.com>
To: "Kirby C. Bohling" <kbohling@birddog.com>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] accidently formatted a physical volume...
Date: Tue Aug 20 13:55:02 2002 [thread overview]
Message-ID: <20020820185256.GE1073@clusterfs.com> (raw)
In-Reply-To: <3D62888B.1060203@birddog.com>
On Aug 20, 2002 13:20 -0500, Kirby C. Bohling wrote:
> In the end, LVM is an abstraction for a block device. So I'd create
> a file and connect a loopback that was the same size as the LV. So pull a
> physical extent, figure out if it is associated with the lv you're
> recovering. Take the lv extent offset it is, and seek the extent size *
> logical extent number and write it to the loopback device. Throwing
> away the LVM metadata. Now, you can take this big pile of bits to an
> ext2/3 guru, and ask them how to glean as much data as possible out of
> it. If the LV was completely on one disk, it should just fsck and
> mount. Assuming you didn't specify the sizes, and do a lot of resizing
> of the LV's that should be the case. Possibly asking the ext2/3 guru
> what the holes should be filled in with, and put that there. I'd guess
> zero's. This trick should work on both sets of disks, but it'll be
> easier to pull off with known good meta-data.
Run something like "gpart" or build the findsuper program in
e2fsprogs/misc, which should give you a pretty good idea of where things
are put on the disk.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
prev parent reply other threads:[~2002-08-20 13:55 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
2002-08-20 13:29 ` Kirby C. Bohling
2002-08-20 13:55 ` Andreas Dilger [this message]
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=20020820185256.GE1073@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=kbohling@birddog.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