Please help with lvextend problems
Trying to enlarge a LV after adding a new PV to the VG.
I get an horrible string of messages:
lvextend -L+400M /dev/vg1/lvusr Extending logical volume lvusr to 3.09GB Inconsistent length 66 71
PV segment pe_alloc_count mismatch: 1436 != 1520 PV segment VG free_count mismatch: 1570 != 1486
Internal error: PV segments corrupted in vg1
Am I toast ???
Here follows some additional data. Thank you Bob Alexander
bob@t40:~$ uname -a Linux t40 2.6.11.4T40237392G-RJA #1 Mon Mar 28 19:36:30 CEST 2005 i686 GNU/Linux t40:/home/bob# pvdisplay --- Physical volume --- PV Name /dev/hda9 VG Name vg1 PV Size 6.77 GB / not usable 0 Allocatable yes PE Size (KByte) 4096 Total PE 1733 Free PE 313 Allocated PE 1420 PV UUID CSxEXj-LPQv-VAlv-gTxv-zLfa-2dZ4-MGN7T1
--- Physical volume ---
PV Name /dev/hda8 VG Name vg1 PV Size 4.97 GB / not usable 0 Allocatable yes PE Size (KByte) 4096 Total PE 1273 Free PE 1273 Allocated PE 0 PV UUID FmDlz8-gBJ6-oH5X-Cg26-ZDdm-pTSh-obtzqG t40:/home/bob# vgdisplay --- Volume group --- VG Name vg1 System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 19 VG Access read/write VG Status resizable MAX LV 0 Cur LV 5 Open LV 5 Max PV 0 Cur PV 2 Act PV 2 VG Size 11.74 GB PE Size 4.00 MB Total PE 3006 Alloc PE / Size 1420 / 5.55 GB Free PE / Size 1586 / 6.20 GB VG UUID sLbPHD-Fxe8-sMkh-pMk8-dvgK-2c8K-DKCEt8 t40:/home/bob# lvdisplay /dev/vg1/lvusr --- Logical volume --- LV Name /dev/vg1/lvusr VG Name vg1 LV UUID PeGQ6L-dqE6-KH7G-ErcU-pzAD-A6JM-ZEHM6x LV Write Access read/write LV Status available # open 1 LV Size 2.70 GB Current LE 690 Segments 2 Allocation inherit Read ahead sectors 0 Block device 254:1
Quoted 1 line · Bob Alexander
Internal error: PV segments corrupted in vg1
No - that's an assertion that triggers as the last thing *before* any metadata changes are made on disk.
First check you're using the latest lvm2 package.
(Run 'lvm version')
Alasdair
Signature · 1 line
[email protected]
Quoted 5 lines · Alasdair G Kergon
Quoted 1 line · Bob Alexander
Internal error: PV segments corrupted in vg1
Quoted 7 lines
No - that's an assertion that triggers as the last thing *before* any metadata changes are made on disk.
First check you're using the latest lvm2 package.
(Run 'lvm version')Alasdair
Al,
thanks for trying to help.
Not sure I understand what you say (English is a bit exotic for me :->).
In any case here is what you request:
bob@t40:~$ sudo lvm version LVM version: 2.01.12 (2005-06-14) Library version: 1.01.03 (2005-06-13) Driver version: 4.4.0
FWIW I am using LVM2 on my customized Debian system with a 2.6.11 kernel (and need to resize my bloody /usr to go to 2.6.13 :-< ).
Take care,
Bob
Quoted 4 lines · Bob Alexander
bob@t40:~$ sudo lvm version LVM version: 2.01.12 (2005-06-14) Library version: 1.01.03 (2005-06-13) Driver version: 4.4.0
FWIW after backing up data I tried to be brave :-)
Booted off a 2005.1 Gentoo LiveCD and used the lvm of this distro (version 2.91.05 2005-04-04) to resize the LV and it worked just fine.
I therefore still believe version 2.01.12 (at least, cannot say for the more recent ones) has a buglet.
Thank you
Bob