Package: lvm2 Version: 2.02.06-3 Severity: important
I'm having a problem getting a Debian system from Linux kernel 2.4 to 2.6 due to LVM. On the 2.4 kernel/LVM1, the VGs and LVs work fine, mount up, and show absolutely no sign of any problem. However, I can't get the 2.6 kernel/LVM2 to activate the VGs at all. The interesting error messages under 2.6 include; "LV tmp: inconsistent LE count 32 != 64" "System ID sorrows1107837513 on /dev/sdd3 differs from sorrows1107837515 for volume group" Notice how the LE count is about half of what it should be (reports 32, but is actually 64). These LVs are striped across the two disks, thus two 32 LE stripes in each PV that make up the VG upon which this LV exists. This person seems to have had the same problem, though he had four stripes; http://www.redhat.com/archives/linux-lvm/2006-October/msg00109.html I originally reported this problem roughly eight months ago, with no resolution or response; http://www.redhat.com/archives/linux-lvm/2006-September/msg00010.html Here is redirected stdout and stderr from the "vgchange -ay -vv" command under 2.6; Setting global/locking_type to 1 Setting global/locking_dir to /var/lock/lvm File-based locking enabled. Finding all volume groups /dev/sda1: lvm1 label detected /dev/hde1: No label detected /dev/sdb1: No label detected /dev/sdb3: lvm1 label detected /dev/sdc1: lvm1 label detected /dev/sdd1: No label detected /dev/sdd2: No label detected /dev/sdd3: lvm1 label detected /dev/hdf1: No label detected Locking /var/lock/lvm/V_vg0 RB Finding volume group "vg0" /dev/sdb3: lvm1 label detected /dev/sdd3: lvm1 label detected Found /dev/sdb3 in VG vg0 Found /dev/sdd3 in VG vg0 System ID sorrows1107837513 on /dev/sdd3 differs from sorrows1107837515 for volume group LV tmp: inconsistent LE count 32 != 64 Internal error: LV segments corrupted in tmp. Volume group "vg0" not found Unlocking /var/lock/lvm/V_vg0 Locking /var/lock/lvm/V_vgbak1 RB Finding volume group "vgbak1" /dev/sda1: lvm1 label detected /dev/sdc1: lvm1 label detected Found /dev/sda1 in VG vgbak1 Found /dev/sdc1 in VG vgbak1 System ID sorrows1157424277 on /dev/sdc1 differs from sorrows1157424270 for volume group LV bak1: inconsistent LE count 6076 != 12152 Internal error: LV segments corrupted in bak1. Volume group "vgbak1" not found Unlocking /var/lock/lvm/V_vgbak1 I searched around for similar problems and didn't find much help. In one case, I saw that it was recommended to do a vgcfgbackup and restore, but this hasn't helped me. vgck under 2.4/LVM1 doesn't show any problems with the VGs. Info about my setup; I've got two VGs, both are showing this problem. In fact, newly created LVM1 VGs have this problem! If I create new LVM1 PVs/VGs/LVs they will also have this problem under the 2.6 kernel and LVM2. Both the 2.4 and 2.6 kernels are custom jobs -- not Debian kernels. The versions are a 2.4.31 and a 2.6.21.x. If I can't get this problem resolved soon, I'm going to have back everything up, blow the old LVM1 PVs, make new LVM2 PVs/VGs/LVs, and restore the data. That's going to be difficult considering that I can't use LVM to combine my physical disks into a single logical partition. Additional info; [EMAIL PROTECTED]>sudo vgdisplay -v --- Volume group --- VG Name vg0 VG Access read/write VG Status available/resizable VG # 0 MAX LV 256 Cur LV 3 Open LV 3 MAX LV Size 2 TB Max PV 256 Cur PV 2 Act PV 2 VG Size 366.34 GB PE Size 32 MB Total PE 11723 Alloc PE / Size 11410 / 356.56 GB Free PE / Size 313 / 9.78 GB VG UUID RpRpg4-bXW7-4FTF-pi3q-OI3i-jPv7-lBs17d --- Logical volume --- LV Name /dev/vg0/tmp VG Name vg0 LV Write Access read/write LV Status available LV # 1 # open 1 LV Size 2 GB Current LE 64 Allocated LE 64 Stripes 2 Stripe size (KByte) 16 Allocation next free Read ahead sectors 1024 Block device 58:0 --- Logical volume --- LV Name /dev/vg0/var-log VG Name vg0 LV Write Access read/write LV Status available LV # 2 # open 1 LV Size 2 GB Current LE 64 Allocated LE 64 Stripes 2 Stripe size (KByte) 16 Allocation next free Read ahead sectors 1024 Block device 58:4 --- Logical volume --- LV Name /dev/vg0/var VG Name vg0 LV Write Access read/write LV Status available LV # 3 # open 1 LV Size 352.56 GB Current LE 11282 Allocated LE 11282 Stripes 2 Stripe size (KByte) 16 Allocation next free Read ahead sectors 1024 Block device 58:5 --- Physical volumes --- PV Name (#) /dev/sda3 (1) PV Status available / allocatable Total PE / Free PE 5778 / 73 PV Name (#) /dev/sdb3 (2) PV Status available / allocatable Total PE / Free PE 5945 / 240 --- Volume group --- VG Name vgbak1 VG Access read/write VG Status available/resizable VG # 2 MAX LV 256 Cur LV 1 Open LV 0 MAX LV Size 2 TB Max PV 256 Cur PV 2 Act PV 2 VG Size 379.75 GB PE Size 32 MB Total PE 12152 Alloc PE / Size 12152 / 379.75 GB Free PE / Size 0 / 0 VG UUID tYH829-eexE-trsb-42bR-bbRj-5hSI-7ydBF3 --- Logical volume --- LV Name /dev/vgbak1/bak1 VG Name vgbak1 LV Write Access read/write LV Status available LV # 1 # open 0 LV Size 379.75 GB Current LE 12152 Allocated LE 12152 Stripes 2 Stripe size (KByte) 16 Allocation next free Read ahead sectors 1024 Block device 58:1 --- Physical volumes --- PV Name (#) /dev/sdc1 (1) PV Status available / allocatable Total PE / Free PE 6076 / 0 PV Name (#) /dev/sdd1 (2) PV Status available / allocatable Total PE / Free PE 6076 / 0 -- System Information: Debian Release: 4.0 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.31-2005062601 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages lvm2 depends on: ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libdevmapper1.02 2:1.02.12-1 The Linux Kernel Device Mapper use ii libncurses5 5.5-5 Shared libraries for terminal hand ii libreadline5 5.2-2 GNU readline and history libraries ii libselinux1 1.32-3 SELinux shared libraries ii libsepol1 1.14-2 Security Enhanced Linux policy lib ii lvm-common 1.5.20 The Logical Volume Manager for Lin lvm2 recommends no packages. -- debconf information: lvm2/snapshots: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]