pvmove killed vg

linux-lvm [email protected] 2 participants 2 messages Dec 12, 2001 – Dec 17, 2001

lore

Share & tools

lore

[email protected]

author

2001-12-12 06:26 UTC #0 lore raw

[email protected] schrieb am 12.12.01:

Heinz,

thank you for your answer! I've done the pvcreate -ff on all pv. One came up with ...volume group "<somegarbage>" where it should have said volume group "vg0". So that fixed something, I presume.

But how do I run the vgcfgrestore on _all_ PV? When I specify one PV, it complains it can't restore part of active volume group. When I specify all PV's, it complains please enter physical volume name. How do I do this? Does this work with lvm 1.0.1?

Commands like vgdisplay complain the VG does not exist.

As to your second suggestion: I have vg0.conf and vg0.<digit>.old in /etc/lvmconf. I assume you mean the first?

Thanks for your input!

Regards,

Gunther

Quoted 1 line

you need to run vgcfgrestore on *all* PVs which where in your

vg0 *after*

Quoted 1 line

running "pvcreate -ff" on them. YOu can find out which these

where by

Quoted 1 line

"vgcfgrestore -ll -n vg0 -f

/etc/lvmconf/WhateverYourRecentBackupFileIs".

Quoted 2 lines

If that doesn't work a hack to activate it anyway without

running vgscan is

Quoted 7 lines

to copy /etc/lvmconf/WhateverYourRecentBackupFileIs (I assume /etc/lvmconf/vg0.conf.cd in your case) to /etc/lvmtab.d/vg0, "echo -en 'vg0\0vg1\0' > /etc/lvmtab" and "vgchange -ay". Create a dummy LV with 1 PE afterwards and your metadata on all PVs of the VG should be ok again.
Remember to back /etc/lvmconf/ regularly when you change your

LVM configuration!

Quoted 6 lines

Regards,
Heinz -- The LVM Guy --
We recommend to upgrade to LVM 1.0.1 because a couple of bugs

(some related to

Quoted 2 lines

pvmove) have been fixed.
On Tue, Dec 11, 2001 at 10:34:24PM +0100,

Quoted 11 lines · [email protected] wrote:

Quoted 11 lines
Hi,
I've got a broken lvm vg as a result of an unsuccessful pvmove command. My system is a SuSE 7.0 with kernel 2.4.4 and lvm-0.9.1_beta7-10.
The vg spans several partitions on one disks, one of which I wanted to evacuate. I used the pvmove command with chunks of 32 PE (= 1 GB); 10 GB total. The first 8 chunks worked okay, but the 9th (pvmove -v /dev/hda8:256-287 /dev/hda10) fell over with error code 23 while moving the fifth PE. So I checked

using

Quoted 2 lines

Quoted 2 lines
pvdisplay that the four PE had indeed been moved. A further attempt with pvmove -v /dev/hda8:260-287 /dev/hda10 fell over

Quoted 8 lines

Quoted 8 lines
well, again error code 23. (That's error moving physical extent(s)).
I then rebooted the machine which killed the complete volume group. Which in turn did not quite impress me. :-((
During my attempts at recovering I think I did a vgscan, which found the vg "vg1" on /dev/hdb, but not the vg "vg0" on

/dev/hda.

Quoted 3 lines

Quoted 3 lines
I tried the following commands unsuccessfully:
- vgcfgrestore -v -n vg0: please enter physical volume name

(the

Quoted 3 lines

Quoted 3 lines
synopsys of vgcfgrestore did not state it as a mandatory
parameter)
- vgcfgrestore -v -n vg0 /dev/hda10: can't restore part of

active

Quoted 2 lines

Quoted 2 lines
volume grout vg0
- vgcfgrestore -v -n vg0 /dev/hda{6,7,8,10}: please enter

physical

Quoted 11 lines

Quoted 11 lines
volume name
- vgchange -a n vg0: volume group vg0 does not exist
- vgchange -a y vg0: volume group vg0 does not exist
I still have the file /etc/lvmconf/vg0.conf.cd as well as the devices /dev/vg0/lv0{0,1,2,3} and /dev/vg0/group. (And /dev/vg1/..., but that is working.)
Any suggestions on how I can recover the data would be highly appreciated. I found a reference to a program called uuid_fixer/uuid_editor, but usage was discouraged. Do I have

Quoted 2 lines

Quoted 2 lines
try it
or is there a better way? Does upgrading to a newer version of

lvm

Quoted 4 lines

Quoted 4 lines
help? Or do I have to update the kernel as well then? And I definately
do _not_ want to kill my other vg as well.

Quoted 8 lines

Quoted 8 lines
Regards,
Gunther

______________________________________________________________________________

Quoted 9 lines

Quoted 9 lines
Die schönsten Ski-Regionen der Alpen - jetzt bei Ferienklick.de
http://ferienklick.de/ski/?PP=2-5-100-105-38
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at

http://www.sistina.com/lvm/Pages/howto.html

Quoted 5 lines

*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Quoted 2 lines

Heinz Mauelshagen Sistina

Software Inc.

Quoted 1 line

Senior Consultant/Developer Am Sonnenhang

Quoted 1 line

Marienrachdorf

Quoted 4 lines

Germany
[email protected] +49 2626 141200

                                                       FAX 924446

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Quoted 6 lines

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at

http://www.sistina.com/lvm/Pages/howto.html

________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13

Heinz J . Mauelshagen

2001-12-17 05:30 UTC #1 lore raw

Quoted 4 lines · On Wed, Dec 12, 2001 at 01:28:16PM +0100, [email protected] wrote:

[email protected] schrieb am 12.12.01:
Heinz,

Quoted 8 lines

thank you for your answer! I've done the pvcreate -ff on all pv. One came up with ...volume group "<somegarbage>" where it should have said volume group "vg0". So that fixed something, I presume.
But how do I run the vgcfgrestore on _all_ PV? When I specify one PV, it complains it can't restore part of active volume group.

Looks like the kernel still knows about the VG. Check /proc/lvm/global if the VG is really still active.

In that case you need to reboot to get rid of it.

Regards,
Heinz -- The LVM Guy --

Quoted 133 lines

When I specify all PV's, it complains please enter physical volume name. How do I do this? Does this work with lvm 1.0.1?
Commands like vgdisplay complain the VG does not exist.
As to your second suggestion: I have vg0.conf and vg0.<digit>.old in /etc/lvmconf. I assume you mean the first?
Thanks for your input!
Regards,
Gunther
Quoted 1 line
you need to run vgcfgrestore on *all* PVs which where in your
vg0 *after*
Quoted 1 line
running "pvcreate -ff" on them. YOu can find out which these
where by
Quoted 1 line
"vgcfgrestore -ll -n vg0 -f
/etc/lvmconf/WhateverYourRecentBackupFileIs".
Quoted 2 lines
If that doesn't work a hack to activate it anyway without
running vgscan is
Quoted 7 lines
to copy /etc/lvmconf/WhateverYourRecentBackupFileIs (I assume /etc/lvmconf/vg0.conf.cd in your case) to /etc/lvmtab.d/vg0, "echo -en 'vg0\0vg1\0' > /etc/lvmtab" and "vgchange -ay". Create a dummy LV with 1 PE afterwards and your metadata on all PVs of the VG should be ok again.
Remember to back /etc/lvmconf/ regularly when you change your
LVM configuration!
Quoted 6 lines
Regards,
Heinz -- The LVM Guy --
We recommend to upgrade to LVM 1.0.1 because a couple of bugs
(some related to
Quoted 2 lines
pvmove) have been fixed.
On Tue, Dec 11, 2001 at 10:34:24PM +0100,
Quoted 11 lines · [email protected] wrote:
Quoted 11 lines
Hi,
I've got a broken lvm vg as a result of an unsuccessful pvmove command. My system is a SuSE 7.0 with kernel 2.4.4 and lvm-0.9.1_beta7-10.
The vg spans several partitions on one disks, one of which I wanted to evacuate. I used the pvmove command with chunks of 32 PE (= 1 GB); 10 GB total. The first 8 chunks worked okay, but the 9th (pvmove -v /dev/hda8:256-287 /dev/hda10) fell over with error code 23 while moving the fifth PE. So I checked
using
Quoted 2 lines
Quoted 2 lines
pvdisplay that the four PE had indeed been moved. A further attempt with pvmove -v /dev/hda8:260-287 /dev/hda10 fell over
as
Quoted 8 lines
Quoted 8 lines
well, again error code 23. (That's error moving physical extent(s)).
I then rebooted the machine which killed the complete volume group. Which in turn did not quite impress me. :-((
During my attempts at recovering I think I did a vgscan, which found the vg "vg1" on /dev/hdb, but not the vg "vg0" on
/dev/hda.
Quoted 3 lines
Quoted 3 lines
I tried the following commands unsuccessfully:
- vgcfgrestore -v -n vg0: please enter physical volume name
(the
Quoted 3 lines
Quoted 3 lines
synopsys of vgcfgrestore did not state it as a mandatory
parameter)
- vgcfgrestore -v -n vg0 /dev/hda10: can't restore part of
active
Quoted 2 lines
Quoted 2 lines
volume grout vg0
- vgcfgrestore -v -n vg0 /dev/hda{6,7,8,10}: please enter
physical
Quoted 11 lines
Quoted 11 lines
volume name
- vgchange -a n vg0: volume group vg0 does not exist
- vgchange -a y vg0: volume group vg0 does not exist
I still have the file /etc/lvmconf/vg0.conf.cd as well as the devices /dev/vg0/lv0{0,1,2,3} and /dev/vg0/group. (And /dev/vg1/..., but that is working.)
Any suggestions on how I can recover the data would be highly appreciated. I found a reference to a program called uuid_fixer/uuid_editor, but usage was discouraged. Do I have
to
Quoted 2 lines
Quoted 2 lines
try it
or is there a better way? Does upgrading to a newer version of
lvm
Quoted 4 lines
Quoted 4 lines
help? Or do I have to update the kernel as well then? And I definately
do _not_ want to kill my other vg as well.
Quoted 8 lines
Quoted 8 lines
Regards,
Gunther
______________________________________________________________________________
Quoted 9 lines
Quoted 9 lines
Die schönsten Ski-Regionen der Alpen - jetzt bei Ferienklick.de
http://ferienklick.de/ski/?PP=2-5-100-105-38
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at
http://www.sistina.com/lvm/Pages/howto.html
Quoted 9 lines
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at
http://www.sistina.com/lvm/Pages/howto.html
________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13

Quoted 5 lines

_______________________________________________
linux-lvm mailing list
[email protected]
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
[email protected] +49 2626 141200

                                                       FAX 924446

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-