Debian Bug report logs - #231823
mdadm: mdrun fails with upstream kernels 2.6.2 and 2.6.3-rc1

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Andre Tomt <andre@tomt.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: mdadm: mdrun fails with upstream kernels 2.6.2 and 2.6.3-rc1

Date: Mon, 09 Feb 2004 04:05:43 +0100

Package: mdadm
Version: 1.3.0-2
Severity: important

mdrun fails to autostart the arrays when using kernel 2.6.2 and 2.6.3-rc1. it
just exits with no errors, with no arrays started. kernel has devfs compiled in,
but not mounted after the initrd is done running.

I suspect it is because /proc/partitions is different from 2.4+devfs (but not
mounted there either)

2.6 /proc/partitions

major minor  #blocks  name

   1     0       4096 ram0
   1     1       4096 ram1
   1     2       4096 ram2
   1     3       4096 ram3
   1     4       4096 ram4
   1     5       4096 ram5
   1     6       4096 ram6
   1     7       4096 ram7
   1     8       4096 ram8
   1     9       4096 ram9
   1    10       4096 ram10
   1    11       4096 ram11
   1    12       4096 ram12
   1    13       4096 ram13
   1    14       4096 ram14
   1    15       4096 ram15
   3     0   16511040 hda
   3     1     999904 hda1
   3     2          1 hda2
   3     5    4992088 hda5
   3     6   10518952 hda6
  33     0  117220824 hde
  33     1    2996091 hde1
  33     2          1 hde2
  33     5  114222118 hde5
  34     0  117220824 hdg
  34     1    2971993 hdg1
  34     2          1 hdg2
  34     5  114246216 hdg5
  56     0   30018240 hdi
  56     1          1 hdi1
  56     5     995967 hdi5
  56     6     995998 hdi6
  56     7    1004031 hdi7
  56     8    4996183 hdi8
  56     9   10522543 hdi9
  56    10   11502508 hdi10
   9     0     999808 md0
   9     2   10518848 md2
   9     1    4992000 md1
 254     0  234430464 dm-0

2.4 /proc/partitions

major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect wuse running use aveq

  56     0   30018240 ide/host4/bus0/target0/lun0/disc 2889 3962 53176 16740 604 1779 19312 15810 -1 112760 42859352
  56     1          1 ide/host4/bus0/target0/lun0/part1 2 0 4 0 0 0 0 0 0 0 0
  56     5     995967 ide/host4/bus0/target0/lun0/part5 4 2 48 60 0 0 0 0 0 60 60
  56     6     995998 ide/host4/bus0/target0/lun0/part6 4 2 48 30 0 0 0 0 0 30 30
  56     7    1004031 ide/host4/bus0/target0/lun0/part7 1927 3734 45108 9710 285 901 9592 7260 0 9080 16970
  56     8    4996183 ide/host4/bus0/target0/lun0/part8 901 95 7428 6130 300 863 9472 8540 0 6760 14670
  56     9   10522543 ide/host4/bus0/target0/lun0/part9 38 82 420 580 19 15 248 10 0 590 590
  56    10   11502508 ide/host4/bus0/target0/lun0/part10 3 13 32 50 0 0 0 0 0 50 50
  34     0  117220824 ide/host2/bus1/target0/lun0/disc 168 85 614 80 3 0 24 0 -3 122920 42581012
  34     1    2971993 ide/host2/bus1/target0/lun0/part1 71 33 208 20 0 0 0 0 0 20 20
  34     2          1 ide/host2/bus1/target0/lun0/part2 2 0 4 0 0 0 0 0 0 0 0
  34     5  114246216 ide/host2/bus1/target0/lun0/part5 90 33 354 30 3 0 24 0 0 30 30
  33     0  117220824 ide/host2/bus0/target0/lun0/disc 149 85 468 120 0 0 0 0 -2 122920 42703952
  33     1    2996091 ide/host2/bus0/target0/lun0/part1 71 33 208 20 0 0 0 0 0 20 20
  33     2          1 ide/host2/bus0/target0/lun0/part2 2 0 4 0 0 0 0 0 0 0 0
  33     5  114222118 ide/host2/bus0/target0/lun0/part5 71 33 208 40 0 0 0 0 0 40 40
   3     0   16511040 ide/host0/bus0/target0/lun0/disc 2672 3979 51978 31380 605 1778 19312 46250 -1 107060 42904382
   3     1     999904 ide/host0/bus0/target0/lun0/part1 1737 3520 41594 19770 285 901 9592 17350 0 17400 37120
   3     2          1 ide/host0/bus0/target0/lun0/part2 2 0 4 20 0 0 0 0 0 20 20
   3     5    4992088 ide/host0/bus0/target0/lun0/part5 909 401 10150 11300 301 862 9472 28890 0 12470 40190
   3     6   10518952 ide/host0/bus0/target0/lun0/part6 18 36 174 190 19 15 248 10 0 200 200
   9     0     999808 md/0 0 0 0 0 0 0 0 0 0 0 0
   9     1    4992000 md/1 0 0 0 0 0 0 0 0 0 0 0
   9     2   10518848 md/2 0 0 0 0 0 0 0 0 0 0 0


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux pelle 2.4.24-s2-server-k7 #1 Wed Jan 28 02:41:09 CET 2004 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages mdadm depends on:
ii  debconf                     1.3.22       Debian configuration management sy
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  makedev                     2.3.1-64     Creates device files in /dev

-- debconf information:
* mdadm/autostart: true
* mdadm/mail_to: atomt
* mdadm/start_daemon: true

Message #10 received at 231823@bugs.debian.org (full text, mbox, reply):

From: Andre Tomt <andre@tomt.net>

To: 231823@bugs.debian.org

Subject: Re: Bug#231823: mdadm: mdrun fails with upstream kernels 2.6.2 and 2.6.3-rc1

Date: Mon, 09 Feb 2004 05:30:27 +0100

Changing line 39 of /sbin/mdrun from:
if [ -z "$AUTOCREATE" ] && grep "        devfs" /proc/filesystems 
>/dev/null 2>&1 && ! grep "^devfs" /proc/mounts >/dev/null 2>&1 ; then

to:
if ! uname -r | grep "2.6" 1>/dev/null && [ -z "$AUTOCREATE" ] && grep " 
       devfs" /proc/filesystems >/dev/null 2>&1 && ! grep "^devfs" 
/proc/mounts >/dev/null 2>&1 ; then

Fixed the problem.. Most likely not the right fix, but it pretty much 
tells whats going on ;-)

ie, /proc/partitions is not devfs-munged with devfs compiled in with 
2.6, or something..

Message #15 received at 231823@bugs.debian.org (full text, mbox, reply):

From: Adrian Bunk <bunk@fs.tum.de>

To: 231823@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Making this bug RC

Date: Sun, 16 May 2004 00:53:06 +0200

severity 231823 grave
thanks

This bug has a serious impact on several kernel 2.6 users, and a way how 
to colve it was already proposed by the submitter.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Message #22 received at 231823@bugs.debian.org (full text, mbox, reply):

From: Andre Tomt <andre@tomt.net>

To: 231823@bugs.debian.org

Subject: Re: Bug#231823: mdadm: mdrun fails with upstream kernels 2.6.2 and, 2.6.3-rc1

Date: Sat, 05 Jun 2004 21:02:01 +0200

Ping.

Message #27 received at 231823@bugs.debian.org (full text, mbox, reply):

From: Mario Joussen <mario@joussen.org>

To: Andre Tomt <andre@tomt.net>, 231823@bugs.debian.org

Cc: blade@debian.org

Subject: Re: Bug#231823: mdadm: mdrun fails with upstream kernels 2.6.2 and, 2.6.3-rc1

Date: Thu, 10 Jun 2004 19:55:16 +0200

On Sat, Jun 05, 2004 at 09:02:01PM +0200, Andre Tomt wrote:
> Ping.

Pong. :-)

I'm still waiting for a reaction from Eduard Bloch. I hope that he will
provide a fix for this problem.

Cheers, Mario

-- 
                                      ,,,
                   Mario Joußen      (o o)      mario@joussen.org
+--------------------------------oOO--(_)--OOo--------------------------------+
  "I WILL STOP TALKING ABOUT THE TWELVE INCH PIANIST" -- Bart Simpson in 3F07

Message #32 received at 231823@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: Mario Joussen <mario@joussen.org>

Cc: Andre Tomt <andre@tomt.net>, 231823@bugs.debian.org

Subject: Re: Bug#231823: mdadm: mdrun fails with upstream kernels 2.6.2 and, 2.6.3-rc1

Date: Thu, 17 Jun 2004 01:25:01 +0200

#include <hallo.h>
* Mario Joussen [Thu, Jun 10 2004, 07:55:16PM]:

> Pong. :-)
> 
> I'm still waiting for a reaction from Eduard Bloch. I hope that he will
> provide a fix for this problem.

I don't have a strong opinion, I have no time or motivation to work on
it and I forgot most things about the internals. If you have a working
fix, use it.

Side comment:

I remember that I used some workarounds to simulate arrays in the POSIX
shell syntax. Since Herbert did not want to use mdrun, I do not see why
not switch to use bash extensions... so if somebody is going to rewrite
mdrun or so, consider this.

Eduard.
-- 
<Aquariophile> Aber wofuer kann ich dann einen MBR gekauft?

Message #37 received at 231823@bugs.debian.org (full text, mbox, reply):

From: Fabio Massimo Di Nitto <fabbione@fabbione.net>

To: 231823@bugs.debian.org

Cc: control@bugs.debian.org

Subject: patch

Date: Mon, 5 Jul 2004 12:44:33 +0200 (CEST)

tag 231823 patch
stop

Hi,
	a patch to fix this bug, based on the previous information can be
found here:

http://we.give.back.to.debian.even.if.we.have.no-name-yet.com/patches/mdadm.231823.diff

It has been tested and known to work both for 2.6 and 2.4 kernels.
The only difference with the suggested patch is to match for ^2.6 instead
of 2.6.

Thanks
Fabio

-- 
<user> fajita: step one
<fajita> Whatever the problem, step one is always to look in the error log.
<user> fajita: step two
<fajita> When in danger or in doubt, step two is to scream and shout.

Message #44 received at 231823@bugs.debian.org (full text, mbox, reply):

From: albert@sedifa.com

To: 231823@bugs.debian.org

Subject: Report working patch

Date: Wed, 14 Jul 2004 09:57:38 +0200

I had the same problem and the patch by fabbione works correctly for me with 
kernel image 2.6.6-1-686-smp on sarge



 

Message #51 received at 231823-close@bugs.debian.org (full text, mbox, reply):

From: Mario Joussen <joussen@debian.org>

To: 231823-close@bugs.debian.org

Subject: Bug#231823: fixed in mdadm 1.6.0-1

Date: Tue, 20 Jul 2004 18:17:16 -0400

Source: mdadm
Source-Version: 1.6.0-1

We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive:

mdadm-udeb_1.6.0-1_i386.udeb
  to pool/main/m/mdadm/mdadm-udeb_1.6.0-1_i386.udeb
mdadm_1.6.0-1.diff.gz
  to pool/main/m/mdadm/mdadm_1.6.0-1.diff.gz
mdadm_1.6.0-1.dsc
  to pool/main/m/mdadm/mdadm_1.6.0-1.dsc
mdadm_1.6.0-1_i386.deb
  to pool/main/m/mdadm/mdadm_1.6.0-1_i386.deb
mdadm_1.6.0.orig.tar.gz
  to pool/main/m/mdadm/mdadm_1.6.0.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 231823@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mario Joussen <joussen@debian.org> (supplier of updated mdadm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


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

Format: 1.7
Date: Tue, 20 Jul 2004 21:40:33 +0200
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 1.6.0-1
Distribution: unstable
Urgency: low
Maintainer: Mario Joussen <joussen@debian.org>
Changed-By: Mario Joussen <joussen@debian.org>
Description: 
 mdadm      - Manage MD devices aka Linux Software Raid
 mdadm-udeb - Manage MD devices aka Linux Software Raid (udeb)
Closes: 231823 250792 253339 257357
Changes: 
 mdadm (1.6.0-1) unstable; urgency=low
 .
   * New upstream release.
     Detect degraded arrays in --monitor mode now.
     (closes: Bug#257357)
   * Changed default to autostart RAID array.
     (closes: Bug#250792)
   * Fixed mdrun problem with kernel 2.6.
     Thanks to Andre Tomt <andre@tomt.net> and Fabio Massimo Di Nitto
     <fabbione@fabbione.net>
     (closes: Bug#231823)
   * Changed reuse warning to be less misleading.
     (closes: Bug#253339)
Files: 
 6925d616c82695e8775b2fb2c9d81ae6 610 admin optional mdadm_1.6.0-1.dsc
 49b6f89709d95f103ca7c8fd83986c16 114172 admin optional mdadm_1.6.0.orig.tar.gz
 1e3ee69b922b066efcae9034bc449681 23918 admin optional mdadm_1.6.0-1.diff.gz
 a83bd43afff4f98d08ce2a5ce0d8c207 86372 admin optional mdadm_1.6.0-1_i386.deb
 668f43bc6ca24e4a0b7a6ee7699aea4b 38362 debian-installer optional mdadm-udeb_1.6.0-1_i386.udeb
package-type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFA/ZWCMHtSKdKmuBARAn8dAJ9PXM8ITPsBLmS9F3BYtOZTlLSsOACg3SkN
qRWh/5742HTs7bY43tyZyg4=
=SG1Y
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.