From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Removing an old disk, and some vgexport/import love..
Date: Fri Sep 20 04:44:50 2002 [thread overview]
Message-ID: <20020920113750.A5931@sistina.com> (raw)
In-Reply-To: <001501c261b7$c1f6ed90$ddc67140@nolove>; from lightning@aci.net on Sat, Sep 21, 2002 at 02:42:18PM -0700
On Sat, Sep 21, 2002 at 02:42:18PM -0700, Matt wrote:
> Chris... I think I love you, that was indeed the problem and your solution
> solved it. I'd like to thank you both for helping me out, have a good one..
Which LVM version was it again.
Need to check if that bug still exists...
Regards,
Heinz -- The LVM Guy --
>
> --Matt
>
> ----- Original Message -----
> From: "Christian Limpach"
> To: <linux-lvm@sistina.com>
> Sent: Thursday, September 19, 2002 7:48 AM
> Subject: Re: [linux-lvm] Removing an old disk, and some vgexport/import
> love..
>
>
> > Quoting Matt <lightning@aci.net>:
> >
> > > > > PV Name (#) /dev/hde1 (1)
> > > > > PV Name (#) /dev/hdg1 (3)
> > > > > PV Name (#) /dev/hdf1 (4)
> >
> > what happened here is that vgreduce doesn't renumber the PVs and if you
> > export the VG and try to reimport it, vgimport complains because it
> expects
> > the PVs to be numbered contiguously. I had this same problem a couple of
> > weeks ago. I solved it by patching the VGDA on the new disk, renumbering
> the
> > PV to get the number of the PV I had removed and then everything was ok
> again.
> >
> > It seems like you'll need to renumber /dev/hdf1 to be PV#2 from being
> PV#4.
> > Check with pvdata that the PVs are indeed numbered as above, make a copy
> of
> > the first few sectors of /dev/hdf1 and then try the following:
> > printf "\0002" | dd of=/dev/hdf1 bs=1 count=1 seek=432 conv=notrunc
> >
> > --
> > Christian Limpach <chris@Pin.LU>
> >
> > _______________________________________________
> > 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
> >
> >
>
>
> _______________________________________________
> 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
*** 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:[~2002-09-20 4:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 1:39 [linux-lvm] Removing an old disk, and some vgexport/import love Matt
2002-09-19 5:00 ` Heinz J . Mauelshagen
2002-09-19 6:13 ` Matt
2002-09-19 8:48 ` Heinz J . Mauelshagen
2002-09-19 9:50 ` Christian Limpach
2002-09-19 16:46 ` Matt
2002-09-20 4:44 ` Heinz J . Mauelshagen [this message]
2002-09-20 5:23 ` Matt
2002-09-20 5:38 ` Heinz J . Mauelshagen
2002-09-20 6:07 ` 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=20020920113750.A5931@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox