Your message dated Sun, 06 Feb 2005 13:47:20 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#292282: fixed in mdadm 1.9.0-1
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; 26 Jan 2005 03:49:06 +0000
>From [EMAIL PROTECTED] Tue Jan 25 19:49:06 2005
Return-path: <[EMAIL PROTECTED]>
Received: from host-64-246-146-171.ubr0.dc1-alb.inoc.net (toaster.hq.voxel.net) 
[64.246.146.171] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CteAz-0001cs-00; Tue, 25 Jan 2005 19:49:06 -0800
Received: by toaster.hq.voxel.net (Postfix, from userid 1000)
        id 96D102F460F; Tue, 25 Jan 2005 22:49:14 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Andres Salomon <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mdadm: unable to assemble devices in degraded mode
X-Mailer: reportbug 3.6
Date: Tue, 25 Jan 2005 22:49:14 -0500
Message-Id: <[EMAIL PROTECTED]>
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.8.1-1
Severity: grave
Justification: causes data loss

Hi,

I created a device md0 w/ 3 block devices; hdf1, hdg1, and hdh1.  It was
set to use raid5.  Today, hdg1 disappeared from the machine.
Unfortunately, mdadm 1.8.1 does not appear to be able to assemble md
devices in degraded mode:

[EMAIL PROTECTED]:/dev$ sudo mdadm -A /dev/md0 --scan
mdadm: failed to RUN_ARRAY /dev/md0: Invalid argument
in kernel logs:
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: md0 stopped.
md: bind<hdh1>
md: bind<hdf1>
md: md0: raid array is not clean -- starting background
reconstruction
raid5: measuring checksumming speed
   8regs     :  1352.000 MB/sec
   8regs_prefetch:  1132.000 MB/sec
   32regs    :   924.000 MB/sec
   32regs_prefetch:   916.000 MB/sec
  pII_mmx   :  2388.000 MB/sec
   p5_mmx    :  3204.000 MB/sec
raid5: using function: p5_mmx (3204.000 MB/sec)
md: raid5 personality registered as nr 4
raid5: device hdf1 operational as raid disk 0
raid5: device hdh1 operational as raid disk 2
raid5: cannot start dirty degraded array for md0
RAID5 conf printout:
 --- rd:3 wd:2 fd:1
 disk 0, o:1, dev:hdf1
 disk 2, o:1, dev:hdh1
raid5: failed to run raid set md0
md: pers->run() failed ...
[EMAIL PROTECTED]:/dev$ sudo mdadm -E /dev/hdh1
/dev/hdh1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 47c630a9:142ec28b:a28fb6b2:8fc0ce54
  Creation Time : Mon Feb 24 05:17:28 2003
     Raid Level : raid5
    Device Size : 156288256 (149.05 GiB 160.04 GB)
   Raid Devices : 3
  Total Devices : 2
Preferred Minor : 0
    Update Time : Tue Jan 25 20:46:04 2005
          State : dirty
 Active Devices : 2
Working Devices : 2
 Failed Devices : 1
  Spare Devices : 0
       Checksum : c12cdab5 - correct
         Events : 0.1697073
         Layout : left-symmetric
     Chunk Size : 32K
      Number   Major   Minor   RaidDevice State
this     2      34       65        2      active sync
/dev/ide/host2/bus1/target1/lun0/part1
   0     0      33       65        0      active sync
/dev/ide/host2/bus0/target1/lun0/part1
   1     1       0        0        1      faulty removed
   2     2      34       65        2      active sync
/dev/ide/host2/bus1/target1/lun0/part1


Google informed me that I should try the following:

[EMAIL PROTECTED]:/dev$ sudo mdadm -S /dev/md0
[EMAIL PROTECTED]:/dev$ sudo mdadm -Af /dev/md0 /dev/hdf1 /dev/hdh1
mdadm: failed to RUN_ARRAY /dev/md0: Invalid argument
[EMAIL PROTECTED]:/dev$ sudo mdadm -S /dev/md0
[EMAIL PROTECTED]:/dev$ sudo mdadm -Af --scan /dev/md0 /dev/hdf1 /dev/hdh1
mdadm: failed to RUN_ARRAY /dev/md0: Invalid argument
mdadm: /dev/hdf1 not identified in config file.
mdadm: /dev/hdh1 not identified in config file.

I then downgraded mdadm 1.7.0-1, and:

[EMAIL PROTECTED]:~$ sudo mdadm -S /dev/md0 
[EMAIL PROTECTED]:~$  sudo mdadm -Af /dev/md0 /dev/hdf1 /dev/hdh1
mdadm: /dev/md0 has been started with 2 drives (out of 3).


According to Neil Brown, mdadm 1.8.1 is a development version
(http://www.issociate.de/board/post/141215/Multipath_problem.html);
he recommends 1.8.0.  If this is indeed the case, we should
definitely not be releasing sarge w/ this version.  The severity of this
bug is grave because the whole point of running w/ raid5 is so that
if a drive fails, data can be recovered from the remaining 2 drives.
Not being able to assemble the md device to recover such data is a bit
of a show stopper.



-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

---------------------------------------
Received: (at 292282-close) by bugs.debian.org; 6 Feb 2005 18:53:33 +0000
>From [EMAIL PROTECTED] Sun Feb 06 10:53:33 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 1CxrXI-0000tA-00; Sun, 06 Feb 2005 10:53:33 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1CxrRI-0003yI-00; Sun, 06 Feb 2005 13:47:20 -0500
From: Mario Joussen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#292282: fixed in mdadm 1.9.0-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 06 Feb 2005 13:47:20 -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=-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: 
X-CrossAssassin-Score: 3

Source: mdadm
Source-Version: 1.9.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.9.0-1_i386.udeb
  to pool/main/m/mdadm/mdadm-udeb_1.9.0-1_i386.udeb
mdadm_1.9.0-1.diff.gz
  to pool/main/m/mdadm/mdadm_1.9.0-1.diff.gz
mdadm_1.9.0-1.dsc
  to pool/main/m/mdadm/mdadm_1.9.0-1.dsc
mdadm_1.9.0-1_i386.deb
  to pool/main/m/mdadm/mdadm_1.9.0-1_i386.deb
mdadm_1.9.0.orig.tar.gz
  to pool/main/m/mdadm/mdadm_1.9.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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mario Joussen <[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: Sun,  6 Feb 2005 12:25:03 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 1.9.0-1
Distribution: unstable
Urgency: high
Maintainer: Mario Joussen <[EMAIL PROTECTED]>
Changed-By: Mario Joussen <[EMAIL PROTECTED]>
Description: 
 mdadm      - Manage MD devices aka Linux Software Raid
 mdadm-udeb - Manage MD devices aka Linux Software Raid (udeb)
Closes: 287638 290363 292282 292715 292784 293406
Changes: 
 mdadm (1.9.0-1) unstable; urgency=high
 .
   * New upstream release.
     Solves problems with same UUID for each array.
     Again a stable upstream version.
     (closes: Bug#292282, Bug#293406, Bug#292784, Bug#290363, Bug#292715)
   * Added some typecasts to make it compilable on amd64 with gcc-4.0.
     Thanks to Andreas Jochens <[EMAIL PROTECTED]>.
     (closes: Bug#287638)
Files: 
 9577d30b0972564c8c13144e47f7bc8c 566 admin optional mdadm_1.9.0-1.dsc
 4c5667761ba98890069127e54682e879 94999 admin optional mdadm_1.9.0.orig.tar.gz
 858f5502e65eb5f1162eb466a1d14a3c 32683 admin optional mdadm_1.9.0-1.diff.gz
 5f471c7f3d53670a5c12cc5ed350d129 101410 admin optional mdadm_1.9.0-1_i386.deb
 b16647d09b6a3e3de3ac5e698ed6c418 41844 debian-installer optional 
mdadm-udeb_1.9.0-1_i386.udeb
package-type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCBmJSMHtSKdKmuBARArf9AKC6Zf0GwKXd6fhZ1/fo680f7M1pfQCghxE0
Q3mk6kxame1xiCC0ty82u/Y=
=NNx2
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to