Bug#436964: Bug in 2.4 kernels with latest lvm2

Alex Deucher · External Since: Jun 15, 2006 Posts: 13

Package: Kernel
Version: 2.4.27-3-sparc64-smp

I had a server go down during a power outage and upon rebooting, lvm
failed to work (2.4 kernel). I could access the PVs, VGs, and LVs ok,
but I could not activate the VG. Attempting to activate the VG
resulted in this error:

vgchange -a y vg00
Huge memory allocation (size 67108864) rejected - metadata corruption?
Couldn't create ioctl argument.
Huge memory allocation (size 67108864) rejected - metadata corruption?
Couldn't create ioctl argument.
Huge memory allocation (size 67108864) rejected - metadata corruption?
Couldn't create ioctl argument.
Huge memory allocation (size 67108864) rejected - metadata corruption?
Couldn't create ioctl argument.
Huge memory allocation (size 67108864) rejected - metadata corruption?
Couldn't create ioctl argument.
Huge memory allocation (size 67108864) rejected - metadata corruption?
Couldn't create ioctl argument.
0 logical volume(s) in volume group "vg00" now active

Kernel 2.6 worked fine. After several hours of debugging on #lvm, we
tracked to problem down to an int to size_t change in
drivers/md/dm-ioctl.c.

(12:41:31) agd5f: agk__: FWIW, I just rebooted into a 2.6 kernel and
dmsetup targets works
(12:43:25) agd5f: the printf is right before if (dmi->flags &
DM_BUFFER_FULL_FLAG) {
(12:44:55) agk__: ah. I'm remembering something
(12:45:55) agd5f: 2.6 works fine. I got my volume back
(12:46:01) agk__: - int *needed = param;
(12:46:01) agk__: + size_t *needed = needed_param;
(12:46:1 Cool

agd5f: but I'm happy to help track down the issue
(12:46:29) agk__: I think it's a bug in the 2.4 patches that we fixed
in 2.6 but hasn't been backported
(12:46:44) agk__: there's an int->size_t change
(12:46:49) agd5f: ah
(12:47:19) agk__: dmsetup targets has probably always been broken for
you on sparc,
(12:47:36) agk__: but lvm2 package update started to use it -
previously it wasn't used
(12:47:39) agd5f: yeah. I'd never used it until today
(12:48:19) agk__: so updating userspace lvm2 started to call 'dmsetup
targets' which doesn't work
(12:48:46) agk__: if debian is still supporting 2.4, then someone
needs to patch the kernel I think to include the patch
(12:49:0 Cool

agk__: and we should update our upstream patches to include it too
(12:50:2 Cool

agk__: what's happening is a size_t is being passed to a
function, which thinks it is an int
(12:50:43) agk__: it changes the value, based on int, and the caller
uses it as size_t again
(12:50:50) agd5f: ah, that makes sense
(12:51:04) agk__: this causes it to think the buffer is too small and
set that flag
(12:51:41) agd5f: right
(12:51:45) agk__: (it passes a pointer to the variable)
(12:55:0 Cool

agk__: drivers/md/dm-ioctl.c:
(12:55:31) agk__: list_versions 'needed' variable vs. list_version_get_needed
(12:55:4 Cool

agk__: compare with the same code in 2.6

Alex

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST DeleteThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org

Steve Langasek · External Since: Dec 13, 2004 Posts: 2073

On Thu, Aug 09, 2007 at 03:01:43PM -0400, Alex Deucher wrote:
> Package: Kernel
> Version: 2.4.27-3-sparc64-smp

> I had a server go down during a power outage and upon rebooting, lvm
> failed to work (2.4 kernel). I could access the PVs, VGs, and LVs ok,
> but I could not activate the VG. Attempting to activate the VG
> resulted in this error:

Which version of lvm2 are you referring to as the "latest"? This bug report
is not useful in its current state; either the bug lies in the lvm2 package
in etch for depending on features not compatible with 2.4 kernels, or this
is user error and not a bug at all because you're trying to use packages
newer than etch with a 2.4 kernel which is not supported at all.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon RemoveThis @debian.org http://www.debian.org/

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org

Alex Deucher · External Since: Jun 15, 2006 Posts: 13

On 8/9/07, Steve Langasek <vorlon.TakeThisOut@debian.org> wrote:
> On Thu, Aug 09, 2007 at 03:01:43PM -0400, Alex Deucher wrote:
> > Package: Kernel
> > Version: 2.4.27-3-sparc64-smp
>
> > I had a server go down during a power outage and upon rebooting, lvm
> > failed to work (2.4 kernel). I could access the PVs, VGs, and LVs ok,
> > but I could not activate the VG. Attempting to activate the VG
> > resulted in this error:
>
> Which version of lvm2 are you referring to as the "latest"? This bug report
> is not useful in its current state; either the bug lies in the lvm2 package
> in etch for depending on features not compatible with 2.4 kernels, or this
> is user error and not a bug at all because you're trying to use packages
> newer than etch with a 2.4 kernel which is not supported at all.

This box is still sarge. I just thought I bring it to your attention.

lvm2 2.02.06-4
libdevmapper1.02 2:1.02.05-2.1 through 2:1.02.12-1
dmsetup 2:1.02.05-2.1 through 2:1.02.12-1

lvm2 used to work. I've kept the box upgraded consistently, but it
hadn't been rebooted in quite a while, When the power went out and
the box rebooted lvm stopped working. presumably something lvm
related.

Alex

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org

Steve Langasek · External Since: Dec 13, 2004 Posts: 2073

reassign 436964 lvm2
found 436964 2.02.06-4
severity 436964 serious
tags 436964 etch
thanks

On Thu, Aug 09, 2007 at 06:51:30PM -0400, Alex Deucher wrote:
> On 8/9/07, Steve Langasek <vorlon.TakeThisOut@debian.org> wrote:
> > On Thu, Aug 09, 2007 at 03:01:43PM -0400, Alex Deucher wrote:
> > > Package: Kernel
> > > Version: 2.4.27-3-sparc64-smp

> > > I had a server go down during a power outage and upon rebooting, lvm
> > > failed to work (2.4 kernel). I could access the PVs, VGs, and LVs ok,
> > > but I could not activate the VG. Attempting to activate the VG
> > > resulted in this error:

> > Which version of lvm2 are you referring to as the "latest"? This bug report
> > is not useful in its current state; either the bug lies in the lvm2 package
> > in etch for depending on features not compatible with 2.4 kernels, or this
> > is user error and not a bug at all because you're trying to use packages
> > newer than etch with a 2.4 kernel which is not supported at all.

> This box is still sarge.

Except clearly it's not, because you have etch versions of lvm2,
libdevmapper1.02, and dmsetup installed.

> lvm2 2.02.06-4
> libdevmapper1.02 2:1.02.05-2.1 through 2:1.02.12-1
> dmsetup 2:1.02.05-2.1 through 2:1.02.12-1

> lvm2 used to work. I've kept the box upgraded consistently, but it
> hadn't been rebooted in quite a while, When the power went out and
> the box rebooted lvm stopped working. presumably something lvm
> related.

Etch userspace packages are expected to be compatible with the 2.4 kernels
in sarge. In cases where they aren't this is a bug in etch, not in sarge;
even if someone was inclined to do an ABI-changing, oldstable upload of the
2.4 kernel for a non-security bug, there's no guarantee at all that users
will install that package before attempting an upgrade to etch, so the only
reliable way to deal with the problem is on the etch side.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon.TakeThisOut@debian.org http://www.debian.org/

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org