Your message dated Tue, 24 May 2005 05:02:50 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#274859: fixed in mdadm 1.9.0-3
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 23 May 2005 12:51:32 +0000
>From [EMAIL PROTECTED] Mon May 23 05:51:32 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp04.mrf.mail.rcn.net [207.172.4.63]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DaCP6-00035g-00; Mon, 23 May 2005 05:51:32 -0700
Received: from 24-148-38-137.arm-bsr1.chi-arm.il.cable.rcn.com (HELO
[172.28.54.160]) (24.148.38.137)
by smtp04.mrf.mail.rcn.net with ESMTP; 23 May 2005 08:51:30 -0400
Message-Id: <[EMAIL PROTECTED]>
X-IronPort-AV: i="3.93,128,1115006400";
d="scan'208"; a="38135707:sNHT21176692"
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Moshe Yudkowsky <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mdadm refuses to start up on boot due to config file version problem
X-Mailer: reportbug 3.12
Date: Mon, 23 May 2005 07:51:29 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: mdadm
Version: 1.9.0-2.3
Severity: critical
Justification: breaks the whole system
After moving to the latest version of mdadm, and kernel 2.6.11-1-k7 (2.6.11-5),
I was unable to reboot my system. I was able to fix this problem by changing
the symbols I use to represent my RAID arrays.
There's been a problem with mdadm for some time. Although I used the symbols
"/dev/md[1-3]" in my /etc/fstab and in /etc/lilo.conf and in
/etc/mdadm/mdadm.conf to configure my RAID arrays, the command in
/boot/initrd.img-<version>/script uses the format "mdadm -A /dev/md/[1-3]"
instead.
After the move to the latest mdadm, kernel , and initrd-tools (0.80.0) I
attempted to reboot and could not do so. The md/3 device would not start,
reiserfs couldn't pass the check, and the system hangs until I intervene.
Once I figured out that the /dev/md3 was not starting at all (and that reiserfs
was reporting, incorrectly, a superblock problem) I was able to start this
device manually. Howver, and this seems to be the crux of the problem, I can't
use "mdadm --assemble /dev/md/3" to start the array if I use the notation
"/dev/md3" in the mdadm.conf file.
After some further fiddling around, I decided to change lilo.conf, mdadm.conf,
and fstab to all use the form "/dev/md/[1-3]". When I made this change, I was
able to reboot without any problems.
So... this seems to be an error in how mdadm configuration works, a mismatch
between the command that generates the "mdadm -A" command that goes into the
system startup and the contents of the conf file. What changed in the most
recent version of mdadm isn't clear to me, but I have my work-around.
What's suprising is that even after I've changed the mdadm.conf file to read
/dev/md/[1-3], the command "mdadm --examine" still produces output in the form
/dev/md[1-3].
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages mdadm depends on:
ii debconf 1.4.49 Debian configuration management sy
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii makedev 2.3.1-78 creates device files in /dev
-- debconf information:
* mdadm/autostart: true
* mdadm/warning:
* mdadm/start_daemon: true
* mdadm/mail_to: moshe
---------------------------------------
Received: (at 274859-close) by bugs.debian.org; 24 May 2005 09:08:06 +0000
>From [EMAIL PROTECTED] Tue May 24 02:08:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DaVOP-0004VU-00; Tue, 24 May 2005 02:08:05 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DaVJK-0007dX-00; Tue, 24 May 2005 05:02:50 -0400
From: [EMAIL PROTECTED] (martin f. krafft)
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#274859: fixed in mdadm 1.9.0-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 24 May 2005 05:02:50 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: mdadm
Source-Version: 1.9.0-3
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.9.0-3_i386.udeb
to pool/main/m/mdadm/mdadm-udeb_1.9.0-3_i386.udeb
mdadm_1.9.0-3.diff.gz
to pool/main/m/mdadm/mdadm_1.9.0-3.diff.gz
mdadm_1.9.0-3.dsc
to pool/main/m/mdadm/mdadm_1.9.0-3.dsc
mdadm_1.9.0-3_i386.deb
to pool/main/m/mdadm/mdadm_1.9.0-3_i386.deb
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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
martin f. krafft <[EMAIL PROTECTED]> (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 [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 24 May 2005 00:03:49 +0200
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 1.9.0-3
Distribution: unstable
Urgency: high
Maintainer: Mario Joussen <[EMAIL PROTECTED]>
Changed-By: martin f. krafft <[EMAIL PROTECTED]>
Description:
mdadm - Manage MD devices aka Linux Software Raid
mdadm-udeb - Manage MD devices aka Linux Software Raid (udeb)
Closes: 274859 310412 310492
Changes:
mdadm (1.9.0-3) unstable; urgency=high
.
* High-urgency upload for sarge targeted RC bugfix.
* Applied patch by Peter Samuelson <[EMAIL PROTECTED]>, which causes mdadm to
follow symlinks of device nodes (closes: #274859, #310412, #310492).
* Added myself as co-maintainer as per agreement with Mario Joussen.
Files:
d3cd638e85c6f5dcd8ec937e9a28f304 623 admin optional mdadm_1.9.0-3.dsc
bd8f672b0c20eca65b88dd96f32f4f0d 35195 admin optional mdadm_1.9.0-3.diff.gz
84987191deed6fcbc36f9dffb79a1703 103824 admin optional mdadm_1.9.0-3_i386.deb
a300962f758506bf3857dee071a8ea0d 41858 debian-installer optional
mdadm-udeb_1.9.0-3_i386.udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iEYEARECAAYFAkKS63IACgkQIgvIgzMMSnV7FACgiP+24mNyDCFWDeGHTiwGU/Ao
uhwAoNYOSUMUqldojbCxd1y6GT5Xc/4Y
=2rXP
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
