Your message dated Sat, 20 May 2006 16:07:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line not a bug 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.00.08-4 Severity: important hi! i'm not sure if this is a kernel-bug, or a lvm bug. i'll try to debug this top-down: the machine has 3 disks: /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 /dev/ide/host0/bus1/target0/lun0: p1 p2 /dev/ide/host0/bus1/target1/lun0: p1 p2 it has 3 metadevices: md0: RAID-1 (h0b1t0l0p2, h0b1t1l0p2) md100: RAID-0 (h0b1t0l0p1) md101: RAID-0 (h0b1t1l0p1) it has 2 VGs: lvm-safe: contains md0 lvm-sorry: contains md100 and md101 i have 3 LVs: ACTIVE '/dev/lvm-sorry/cluon-media' [150.00 GB] next free ACTIVE '/dev/lvm-sorry/var-spool' [1.00 GB] next free ACTIVE '/dev/lvm-safe/cluon-root' [1.00 GB] next free all of the above was created running lvm10 on kernel-image-2.4.24-k6. i later upgraded to lvm2 (both package, and then metadata type). when i boot with kernel-image-2.4.24-k6, i have no problems. all 3 LVs are found and available. when i boot the same setup with kernel-image-2.6.3-1-386, i get the following errors on bootup: : Starting RAID devices: /dev/md/0 /dev/md/100 /dev/md/101 done. : Setting up LVM Volume Groups... : Reading all physical volumes. This may take a while ... : Found volume group "lvm-sorry" using metadata type lvm2 : Found volume group "lvm-safe" using metadata type lvm2 : device-mapper ioctl cmd 9 failed: Invalid argument : Couldn't load device 'lvm--sorry-cluon--media'. : device-mapper ioctl cmd 9 failed: Invalid argument : Couldn't load device 'lvm--sorry-var--spool'. : 2 logical volume(s) in volume group "lvm-sorry" now active : 1 logical volume(s) in volume group "lvm-safe" now active after that, lvscan and other lvm2 tools report that all is ok, but i can't use any LV in lvm-sorry. the LV from lvm-safe works fine though. the errors come from the vgchange command in /etc/init.d/lvm. when i run the same command with -v and -d, i don't get more clues: : [EMAIL PROTECTED]:-> /lib/lvm-200/lvm vgchange -a y -d -v --ignorelockingfailure : Finding all volume groups : Finding volume group "lvm-sorry" : Found volume group "lvm-sorry" : Loading lvm--sorry-cluon--media : device-mapper ioctl cmd 9 failed: Invalid argument : Couldn't load device 'lvm--sorry-cluon--media'. : Found volume group "lvm-sorry" : Loading lvm--sorry-var--spool : device-mapper ioctl cmd 9 failed: Invalid argument : Couldn't load device 'lvm--sorry-var--spool'. : 2 logical volume(s) in volume group "lvm-sorry" now active : Finding volume group "lvm-safe" : 1 logical volume(s) in volume group "lvm-safe" already active : Found volume group "lvm-safe" : Found volume group "lvm-safe" : Activated logical volumes in volume group "lvm-safe" : 1 logical volume(s) in volume group "lvm-safe" now active the kernel meanwhile reports the following error: : device-mapper: dm-linear: Device lookup failed : device-mapper: error adding target to table : device-mapper: dm-linear: Device lookup failed : device-mapper: error adding target to table one more strange thing that i found: : 43 [EMAIL PROTECTED]:->pvs : PV VG Fmt Attr PSize PFree : /dev/hdc1 lvm-sorry lvm2 ax 111.72G 0 : /dev/hdd1 lvm-sorry lvm2 ax 111.72G 72.44G : /dev/md0 lvm-safe lvm2 ax 37.25G 36.25G isn't it supposed to report /dev/md100 and /dev/md101 for lvm-sorry? anyway, that's the state on my machine. if you need more information, please let me know. one last thing, the machine is running testing, but pulls the kernel- images from unstable. i've also upgraded lvm2 to the version in unstable in the hope that this might fix things. but it did not, i had the same behaviour with lvm2 from testing. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.3-1-386 Locale: LANG=C, LC_CTYPE=C Versions of packages lvm2 depends on: ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdevmapper1.00 2:1.00.07-3.1 The Linux Kernel Device Mapper use ii lvm-common 1.5.11 The Logical Volume Manager for Lin -- no debconf information
--- End Message ---
--- Begin Message ---This is not a bug. The trace shows several messages from the md detection. Bastian -- You're dead, Jim. -- McCoy, "The Tholian Web", stardate unknown
--- End Message ---
