Skip to contentSkip to conversation

Recovering inconsistent vg

linux-lvm Shane Wegner 3 participants 6 messages Jun 4, 2002 – Jun 5, 2002

lore
Share & tools
lore

Shane Wegner

author
#0 lore raw

Hi all,

I'm not sure how this happened but after rebooting, I am getting the following from vgscan.

continuum:~# vgscan
vgscan -- reading all physical volumes (this may take a
while...)
vgscan -- found inactive volume group "vg0"
vgscan -- ERROR "lv_check_consistency(): LV status" volume
group "vg0" is inconsistent
vgscan -- ERROR: unable to do a backup of volume group
"vg0"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing
volume group "vg0" from "/etc/lvmtab"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully
created
vgscan -- WARNING: This program does not do a VGDA backup
of your volume group

I have no idea what this means, what I can do to recover and am hoping someone could help me out. A pvscan yeilds:

continuum:~# pvscan
pvscan -- reading all physical volumes (this may take a
while...)
pvscan -- inactive PV "/dev/hdi1"  is associated to unknown
VG "vg0" (run vgscan)
pvscan -- inactive PV "/dev/hde1"  is associated to unknown
VG "vg0" (run vgscan)
pvscan -- inactive PV "/dev/hda1"  is associated to unknown
VG "vg0" (run vgscan)
pvscan -- total: 3 [215.74 GB] / in use: 3 [215.74 GB] / in
no VG: 0 [0]

Looks right to me. vg0 is hda1, hde1, and hdi1.

Thanks in advance,
Shane

#1 lore raw
Quoted 4 lines · Shane Wegner

Hi all,

I'm not sure how this happened but after rebooting, I am getting the following from vgscan.

Quoted 15 lines
continuum:~# vgscan
vgscan -- reading all physical volumes (this may take a
while...)
vgscan -- found inactive volume group "vg0"
vgscan -- ERROR "lv_check_consistency(): LV status" volume
group "vg0" is inconsistent
vgscan -- ERROR: unable to do a backup of volume group
"vg0"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing
volume group "vg0" from "/etc/lvmtab"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully
created
vgscan -- WARNING: This program does not do a VGDA backup
of your volume group

If this is a recent debian unstable upgrade then you should get the latest 1:1.0.4-4 deb (uploaded this morning GMT) that fixes the problem.

patrick

author
#2 lore raw
Quoted 7 lines · Patrick Caulfield
Quoted 2 lines · Shane Wegner

vgscan -- ERROR "lv_check_consistency(): LV status" volume group "vg0" is inconsistent

If this is a recent debian unstable upgrade then you should get the latest 1:1.0.4-4 deb (uploaded this morning GMT) that fixes the problem.

Yes, that was it. Thank you for the help.

Shane

#3 lore raw
In reply to Shane Wegner

Hi,

I've the same problem. The VG was originally created with LVM 1.0.4, then used (and extended) with 1.1rc1. Now I've the problem after downgrading to 1.0.4.

	# ./vgscan
	vgscan -- ERROR "lv_check_consistency(): LV status" volume group "vg00" is inconsistent
	vgscan -- ERROR: unable to do a backup of volume group "vg00"
	vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group "vg00" from "/etc/lvmtab"
	vgscan -- reading all physical volumes (this may take a while...)
	vgscan -- found active volume group "vg00"
	vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
	vgscan -- WARNING: This program does not do a VGDA backup of your volume group

Stephan

Quoted 44 lines · Shane Wegner

Hi all,

I'm not sure how this happened but after rebooting, I am getting the following from vgscan.

continuum:~# vgscan
vgscan -- reading all physical volumes (this may take a
while...)
vgscan -- found inactive volume group "vg0"
vgscan -- ERROR "lv_check_consistency(): LV status" volume
group "vg0" is inconsistent
vgscan -- ERROR: unable to do a backup of volume group
"vg0"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing
volume group "vg0" from "/etc/lvmtab"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully
created
vgscan -- WARNING: This program does not do a VGDA backup
of your volume group

I have no idea what this means, what I can do to recover and am hoping someone could help me out. A pvscan yeilds:

continuum:~# pvscan
pvscan -- reading all physical volumes (this may take a
while...)
pvscan -- inactive PV "/dev/hdi1"  is associated to unknown
VG "vg0" (run vgscan)
pvscan -- inactive PV "/dev/hde1"  is associated to unknown
VG "vg0" (run vgscan)
pvscan -- inactive PV "/dev/hda1"  is associated to unknown
VG "vg0" (run vgscan)
pvscan -- total: 3 [215.74 GB] / in use: 3 [215.74 GB] / in
no VG: 0 [0]

Looks right to me. vg0 is hda1, hde1, and hdi1.

Thanks in advance,
Shane

_______________________________________________
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

#4 lore raw
Quoted 15 lines · Stephan Austermuehle

Hi,

I've the same problem. The VG was originally created with LVM 1.0.4, then used (and extended) with 1.1rc1. Now I've the problem after downgrading to 1.0.4.

	# ./vgscan
	vgscan -- ERROR "lv_check_consistency(): LV status" volume group "vg00" is inconsistent
	vgscan -- ERROR: unable to do a backup of volume group "vg00"
	vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group "vg00" from "/etc/lvmtab"
	vgscan -- reading all physical volumes (this may take a while...)
	vgscan -- found active volume group "vg00"
	vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
	vgscan -- WARNING: This program does not do a VGDA backup of your volume group
Quoted 2 lines

Stephan

yeah, it's a bug in 1.1 which is fixed in the debian patched 1.0.4-4. If you built from source here's the workaround:

lv_check_consistency.c 5 Jun 2002 10:12:01 -0000 1.4.2.1 renamed from lv_check_consistency.c 7 Feb 2002 16:19:46 -0000 1.4 +3 -0
diff -u -r1.4 -r1.4.2.1
@@ -42,6 +42,9 @@
 
    debug_enter ( "lv_check_consistency -- CALLED\n");
 
+   /* Don't barf on broken LVM1.1 created metadata */
+   if (lv->lv_status > 2) lv->lv_status = 1;
+
    if ( lv == NULL)                                   ret = -LVM_EPARAM;
    else if ( lv_check_name ( lv->lv_name) != 0)       ret = -LVM_ELV_LVNAME;
    else if ( vg_check_name ( lv->vg_name) != 0)       ret = -LVM_ELV_VGNAME;

patrick

#5 lore raw
Quoted 2 lines · Patrick Caulfield

yeah, it's a bug in 1.1 which is fixed in the debian patched 1.0.4-4. If you built from source here's the workaround:

Thanks, that worked.

Stephan