From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Solution? found backup hexdump of partition's first MB
Date: Wed, 30 May 2001 11:33:50 +0200 [thread overview]
Message-ID: <20010530113350.D30938@sistina.com> (raw)
In-Reply-To: <20010529202030.A700@jensbenecke.de>; from lvm@jensbenecke.de on Tue, May 29, 2001 at 08:20:30PM +0200
On Tue, May 29, 2001 at 08:20:30PM +0200, Jens Benecke wrote:
> On Tue, May 29, 2001 at 09:34:36AM +0200, Jens Benecke wrote:
> > On Tue, May 29, 2001 at 01:06:28AM +0200, Jens Benecke wrote:
> > > Hello,
> > > I upgraded to 2.2.4 (0.9.1-beta2) from 2.2.18 (LVM 0.9) and this seems to
> > > have killed one of my PVs. I tried the 0.9 utilities and updated to
> > > 0.9.1-beta7 when I noticed the problems. No change. Booting back to 2.2.18
> > > didn't help, the PV was gone there as well.
> > follow-up:
> > vgcfgrestore doesn't work, because LVM thinks my hdc1 is no PV. Here's the
> > output: (...)
>
> I think I found a way: I have found a hex-dump backup of the first megabyte
> of the disk in - apparently - working order.
>
> So: hdc1 was the broken PV, it's the only partition on hdc, and I have a
> file called hdc-first-MB-hexdump.
>
> Does this help? ;)
Yes, in case it really contains the needed actual copy.
>
> The question is, does this already contain file system data or is this
> still all LVM structure data?
If it is just a MB -> unlikely, because LVM typically reserves more
than that for the VGDA.
*But* to be really sure, run "pvdata -PP" on the hex dump and look
for pe_on_disk.base + pe_on_disk.size. This will give you the
actual end (in 512 byte units) of the metadata in the file and should
be used to dd it back to disk.
> I'm quite sure that the LVM structure didn't
> change since this file was created, only (of course) the data changed on
> the filesystem contained in the one (single) LV on data=(hdc1,hda1).
See above: you *need* to be sure. Hopefully the pvcreate/vgcfgrestore pair
works for you.
>
>
> --
> Jens Benecke /* Nobody will ever see this error message :-) */
> panic("Cannot initialize video hardware\n");
> -- Linux 2.0.38, arch/m68k/atari/atafb.c
> http://www.hitchhikers.de/ - Die kostenlose Mitfahrzentrale f�r ganz Europa
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-05-30 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010529010628.E1971@jensbenecke.de>
[not found] ` <20010529093436.A792@jensbenecke.de>
2001-05-29 8:57 ` [linux-lvm] lvm with lfs Guillaume RAMELET
2001-05-29 21:11 ` [linux-lvm] Re: Help! Upgrade 2.2.18 -> 2.4.4 killed a PV Heinz J. Mauelshagen
[not found] ` <20010529214021.A1594@jensbenecke.de>
2001-05-30 9:28 ` Heinz J. Mauelshagen
2001-05-30 14:25 ` AJ Lewis
2001-05-30 14:49 ` Heinz J. Mauelshagen
2001-05-30 20:17 ` Austin Gonyou
2001-05-30 20:52 ` Jesse Stockall
2001-05-30 21:30 ` Austin Gonyou
[not found] ` <20010529202030.A700@jensbenecke.de>
2001-05-30 9:33 ` Heinz J. Mauelshagen [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=20010530113350.D30938@sistina.com \
--to=mauelshagen@sistina.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 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.