[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#344741: marked as done (kernel-source-2.4.27 - device-mapper patch lacks support for major/minor device resolution)



Your message dated Mon, 21 Aug 2006 20:01:43 -0400
with message-id <20060822000143.GA7953@doctormoo.dyndns.org>
and subject line Support for 2.4 kernels is being dropped
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: lvm2
Version: 2.02.00-1
Severity: critical
Justification: breaks the whole system

Problem description:
-------------------
After upgrading to lvm2 2.02.00-1 and the required
libdevmapper1.02, the system was unable to complete booting,
as no LVs were reachable: the system was unusable and could not
be used to fix itself.
(The metadata is in lvm2 format.)


vgscan worked OK.
vgchange -a y was broken, spewing lots of:
    device-mapper: one of name or uuid must be supplied, cmd(9)
      device-mapper ioctl cmd 9 failed: Invalid argument
and finally claiming
     18 logical volume(s) in volume group "base_vg" now active 
However, they were not accessible and the boot process was
unable to finish.

vgchange -a n also failed: 
    device-mapper: one of name or uuid must be supplied, cmd(11)
      device-mapper ioctl cmd 11 failed: Invalid argument
      _deps: task run failed for (254:0)
      Failed to add device (254:0) to dtree
    device-mapper: one of name or uuid must be supplied, cmd(11)
      device-mapper ioctl cmd 11 failed: Invalid argument
      _deps: task run failed for (254:1)
      Failed to add device (254:1) to dtree
    ...

dmsetup ls was OK.
dmsetup table showed only:
    base_vg-usr:
    base_vg-var:
    ...
i.e. the names were known, but the tables were missing.



Solution:
--------
After downgrading to lvm2 2.01.14-3 (and thus libdevmapper1.02)
the system worked again.  

To archive this, a rescue system was needed, as /usr/ (apt-get)
and /var/ (apt/sources.list) etc. were all unreachable.



Note: 
----
I am not 100% sure if it is libdevmapper1.02 or lvm2, however,
lvm2 Version 2.01.14-3 works with:
    rm /lib/libdevmapper.so.1.01
    ln -s /lib/libdevmapper.so.1.02 /lib/libdevmapper.so.1.01
Thus the problem probably is within lvm2 v2.02.00-1.


PS: please CC me.


-- System Information:
Debian Release: testing/unstable
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-k7
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

[NOTE: bug report created with lvm2 v2.01.14-3!]
Versions of packages lvm2 depends on:
ii  debconf [debconf-2.0]        1.4.59      Debian configuration management sy
ii  libc6                        2.3.5-8.1   GNU C Library: Shared libraries an
ii  libdevmapper1.01             2:1.01.05-1 The Linux Kernel Device Mapper use
ii  libncurses5                  5.5-1       Shared libraries for terminal hand
ii  libreadline5                 5.0-11      GNU readline and history libraries
ii  libselinux1                  1.26-1      SELinux shared libraries
ii  lvm-common                   1.5.20      The Logical Volume Manager for Lin

lvm2 recommends no packages.

-- debconf information:
  lvm2/snapshots:


--- End Message ---
--- Begin Message ---
This bug is being 'fixed' by dropping support for 2.4 kernels.  The needed kernel
support is in 2.6.

-- 
Nathanael Nerode  <neroden@fastmail.fm>

"(Instead, we front-load the flamewars and grudges in
the interest of efficiency.)" --Steve Lanagasek,
http://lists.debian.org/debian-devel/2005/09/msg01056.html

--- End Message ---

Reply to: