Can't use LVM1 VG/LVs under LVM2; LV xxx: inconsistent LE count 32 != 64

linux-lvm Jesse Molina 3 participants 5 messages May 9, 2007 – May 10, 2007

Share & tools

Jesse Molina

author

2007-05-09 04:55 UTC #0 lore raw

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.

I've filed a Debian bug, which has additional information, here;

	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422963

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.

Bad error checking, or actual problem? I don't know.

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

Help?

Signature · 5 lines

# Jesse Molina
# Mail = [email protected]
# Page = [email protected]
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/

David Robinson

2007-05-09 07:14 UTC #1 lore raw

Quoted 22 lines · Jesse Molina

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.
I've filed a Debian bug, which has additional information, here;
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422963
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.
Bad error checking, or actual problem? I don't know.
This person seems to have had the same problem, though he had four stripes;

Quoted 8 lines

    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
Help?

You need a newer version of lvm2 (> 2.02.21). The problem has only been fixed recently.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232397

Dave

Bryn M. Reeves

2007-05-09 09:46 UTC #2 lore raw

In reply to Jesse Molina

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 11 lines · Jesse Molina

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.
I've filed a Debian bug, which has additional information, here;
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422963

Quoted 6 lines

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"

Hi Jesse,

This sounds like:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232397

This is fixed upstream in versions from v2_02_24:
- --------
/cvs/lvm2/LVM2/WHATS_NEW:
revision 1.586
date: 2007/03/15 13:38:27; author: agk; state: Exp; lines: +2 -2 Try to fix reading in of lvm1 striped LVs.
There are two fixes other than improving variable names and updating code layout etc.

The loop counter is incremented by area_len instead of area_len * stripes;

the 3rd _check_stripe parameter is no longer multiplied by number of stripes.
- --------

Kind regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGQZcK6YSQoMYUY94RAqenAKCLdOcbDCJSFqvDUwZsUx/yZXQebgCfTdXu Nwz6xK1mCHIiiPVpHp6h0Ss=
=fBTO
-----END PGP SIGNATURE-----

Jesse Molina

author

2007-05-09 18:29 UTC #3 lore raw

Thanks for the replies. I see that Debian has a lvm2 package version 2.02.24-6 out, and I'll try to install that. However, I'll have to force the install, as 2.4 kernels are completely dead on Debian Unstable now, due to recent versions of libc6 requiring NPTL. Hopefully I won't get into a critical dependency problem.

Quoted 59 lines · Bryn M. Reeves

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 11 lines · Jesse Molina
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.
I've filed a Debian bug, which has additional information, here;
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422963
Quoted 6 lines
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"
Hi Jesse,
This sounds like:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232397
This is fixed upstream in versions from v2_02_24:
- --------
/cvs/lvm2/LVM2/WHATS_NEW:
revision 1.586
date: 2007/03/15 13:38:27; author: agk; state: Exp; lines: +2 -2 Try to fix reading in of lvm1 striped LVs.
There are two fixes other than improving variable names and updating code layout etc.
The loop counter is incremented by area_len instead of area_len * stripes;
the 3rd _check_stripe parameter is no longer multiplied by number of stripes.
- --------
Kind regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGQZcK6YSQoMYUY94RAqenAKCLdOcbDCJSFqvDUwZsUx/yZXQebgCfTdXu Nwz6xK1mCHIiiPVpHp6h0Ss=
=fBTO
-----END PGP SIGNATURE-----
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Signature · 5 lines

# Jesse Molina
# Mail = [email protected]
# Page = [email protected]
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/

Jesse Molina

author

2007-05-10 00:25 UTC #4 lore raw

This is confirmed as fixed. Thanks David and Bryn for the referral to the fix!

I am surprised that this bug survived in the wild for so long. I had unsuccessfully tried to upgrade this system several times in the last two years. I had previously thought it was the funky Promise ATA controller in this host.

Thanks for the help. I'll be closing Debian bug #422963 here soon.

For documentation/spidering purposes;

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232397

LVM2 unable to use LVM1 striped logical volumes
LVM2 is unable to import striped LVM1 volumes

Quoted 63 lines · Jesse Molina

Thanks for the replies. I see that Debian has a lvm2 package version 2.02.24-6 out, and I'll try to install that. However, I'll have to force the install, as 2.4 kernels are completely dead on Debian Unstable now, due to recent versions of libc6 requiring NPTL. Hopefully I won't get into a critical dependency problem.
Quoted 57 lines · Bryn M. Reeves
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 10 lines · Jesse Molina
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.
I've filed a Debian bug, which has additional information, here;
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422963
Quoted 6 lines
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"
Hi Jesse,
This sounds like:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232397
This is fixed upstream in versions from v2_02_24:
- --------
/cvs/lvm2/LVM2/WHATS_NEW:
revision 1.586
date: 2007/03/15 13:38:27; author: agk; state: Exp; lines: +2 -2 Try to fix reading in of lvm1 striped LVs.
There are two fixes other than improving variable names and updating code layout etc.
The loop counter is incremented by area_len instead of area_len * stripes;
the 3rd _check_stripe parameter is no longer multiplied by number of stripes.
- --------
Kind regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGQZcK6YSQoMYUY94RAqenAKCLdOcbDCJSFqvDUwZsUx/yZXQebgCfTdXu Nwz6xK1mCHIiiPVpHp6h0Ss=
=fBTO
-----END PGP SIGNATURE-----
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Signature · 5 lines

# Jesse Molina
# Mail = [email protected]
# Page = [email protected]
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/