All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Limpach <chris@Pin.LU>
To: linux-lvm@sistina.com, Matt <lightning@aci.net>
Subject: Re: [linux-lvm] Removing an old disk, and some vgexport/import love..
Date: Thu Sep 19 09:50:39 2002	[thread overview]
Message-ID: <1032446901.3d89e3b5b98de@lola.Pin.LU> (raw)
In-Reply-To: <000d01c2615f$7f7d7130$ddc67140@nolove>

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>

  parent reply	other threads:[~2002-09-19  9:50 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 [this message]
2002-09-19 16:46       ` Matt
2002-09-20  4:44         ` Heinz J . Mauelshagen
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=1032446901.3d89e3b5b98de@lola.Pin.LU \
    --to=chris@pin.lu \
    --cc=lightning@aci.net \
    --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.