From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: Help! Upgrade 2.2.18 -> 2.4.4 killed a PV
Date: Wed, 30 May 2001 11:28:09 +0200 [thread overview]
Message-ID: <20010530112809.C30938@sistina.com> (raw)
In-Reply-To: <20010529214021.A1594@jensbenecke.de>; from lvm@jensbenecke.de on Tue, May 29, 2001 at 09:40:21PM +0200
On Tue, May 29, 2001 at 09:40:21PM +0200, Jens Benecke wrote:
> On Tue, May 29, 2001 at 09:11:28PM +0000, Heinz J. Mauelshagen wrote:
> >
> > Jens,
> > you need to run pvcreate on the invalid PV before running vgcfgrestore.
>
> I did so.
>
> Now I have a PV that is associated to an unknown VG, and vgcfgrestore says
>
> vgcfgrestore -- size of physical volume /dev/hdc1 differs from backup
>
> although 'vgcfgrestore -n data -ll' and 'pvdata -PP /dev/hdc1' show EXACTLY
> the same amount of extents (used/free/..), and GB. And hdc1 certainly
> didn't change in size.
>
> Strange: BOTH vgcfgrestore and pvdata -PP know that the PVs belong to the
> VG "data", but vgscan doesn't find it, and pvscan says both belong to an
> unknown VG and I should run vgscan.
If pvdata still tells you, that the PV belongs to some VG it hasn't created
a new one, likely because your didn't use "pvcreate -ff".
Does "pvcreate -ff"/vgcfgrestore help it?
BTW: WRT to your hex dump; see my other answer.
>
>
> So, I am a little further but not yet there =;)
>
>
> Thanks for the help!
>
> --
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-30 9:28 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 [this message]
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 ` [linux-lvm] Solution? found backup hexdump of partition's first MB Heinz J. Mauelshagen
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=20010530112809.C30938@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.