[linux-lvm] Restore after lvmove crash

[linux-lvm] Restore after lvmove crash

[fabsk]

Hi,

Today, I tried to "lvmove" a logical volume (my first one) to another I just
created. But after a few percent, my computer crashed and now I can't use my
LVM anymore. I am using Kubuntu 6.06 and LVM2. More details:

When I try to do an operation on the LVM (using a live CD), I get the following
error:

  Couldn't find volume 'pvmove0' for segment 'start_extent'.
  Couldn't read all logical volumes for volume group lvm2.
  Volume group "lvm2" inconsistent
  Couldn't find volume 'pvmove0' for segment 'start_extent'.
  Couldn't read all logical volumes for volume group lvm2.
  Inconsistent metadata copies found - updating to use version 39

Then I tried to do "vgreduce --removemissing lvm2" ("lvm2" is the name of my VG)
and it destroyed everything. I was able to restore the VG definition with
"vgcfgrestore" by finding the CFG in the partitions, and now I am back to the
previous state: the definitions of my PV and LV seem OK, but there is still
this "pvmove0" around that prevent me to use my LVM.
I don't understand where LVM2 can find this "pvmove0", I thought that if should
only use the definitions in my restore file...

If anyone have any idea, it would be really nice, I am investigating for hours
now and I'm stuck.

Thank you for your attention
Fabien

Re: [linux-lvm] Restore after lvmove crash

[Alasdair G Kergon]

On Sun, Sep 03, 2006 at 02:26:44AM +0200, fabsk@free.fr wrote:
> I don't understand where LVM2 can find this "pvmove0", I thought that if should

Use 'pvmove --abort' to remove that.

Alasdair
-- 
agk@redhat.com

[linux-lvm] Restore after lvmove crash

[Fabien Shum-King]

Hi,

I'm sorry that this message doesn't appear in the existing thread, but I
received the mails in digest mode.

Summary: I used "pvmove /dev/sda2 /dev/sda7", the system crashed and I
get a invalid "pvmove0" LV I could not remove and prevented most actions
on the VG (including destroying the VG!).
"pvmove --abord" did not work (I searched a lot before asking here).

In fact, LVM was still scanning /dev/sda7 even if it was not used as a
physical volume and if I change the type of partition.
I don't know exactly which of these two actions solved the problem
(maybe both), but it did it:
- I removed the unused partition /dev/sda7 (and filled the free space
with /dev/zero so I don't get any problem in the future)
- I restored the metadata under another VG name (so my existing physical
volumes did not appear under the old corrupted VG), and I remove
everything. Then I restored the metadata onder the previous VG name. And
it worked

I hope that it could help someone in the future.

Fabien