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

Bug#271033: marked as done (bug in drivers/md/md.c related to multipath)

Your message dated Wed, 31 May 2006 16:32:21 -0700
with message-id <E1FlaAn-0004Gp-Bt@spohr.debian.org>
and subject line Bug#271033: fixed in mdadm 2.4.1-2
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: mdadm
Version: 1.6.0-3
Severity: important

mdadm is not able to assemble multipath device except of its own

| # mdadm --create -n 2 -l multipath /.dev/md0 /dev/zfcp/0x2*/*/*
| mdadm: /dev/zfcp/0x2100002037470047/0x0000000000000000/disc appears to be part of a raid array:
|     level=-4 devices=2 ctime=Fri Sep 10 18:15:48 2004
| mdadm: /dev/zfcp/0x2200002037470047/0x0000000000000000/disc appears to be part of a raid array:
|     level=-4 devices=2 ctime=Fri Sep 10 18:15:48 2004
| Continue creating array? y
| mdadm: array /.dev/md0 started.
| # mdadm --examine --scan >> /etc/mdadm/mdadm.conf
| # cat /etc/mdadm/mdadm.conf
| DEVICE /dev/zfcp/*/*/*
| ARRAY /dev/md0 level=multipath num-devices=2 UUID=ac88c560:ad6b1e3d:211de7b0:5d562f61
|    devices=/dev/zfcp/0x2200002037470047/0x0000000000000000/disc,/dev/zfcp/0x2100002037470047/0x0000000000000000/disc
| # mdadm --stop /dev/md0
| # mdadm -A -s -v       
| mdadm: looking for devices for /dev/md0
| mdadm: /dev/zfcp/0x2200002037470047/0x0000000000000000/disc is identified as a member of /dev/md0, slot 1.
| mdadm: /dev/zfcp/0x2100002037470047/0x0000000000000000/disc is identified as a member of /dev/md0, slot 1.
| mdadm: added /dev/zfcp/0x2100002037470047/0x0000000000000000/disc to /dev/md0 as 1
| mdadm: failed to add /dev/zfcp/0x2200002037470047/0x0000000000000000/disc to /dev/md0: Device or resource busy
| mdadm: /dev/md0 has been started with 2 drives and -1 spares.
| # mdadm -D /dev/md0
| /dev/md0:
|         Version : 00.90.01
|   Creation Time : Fri Sep 10 18:19:40 2004
|      Raid Level : multipath
|      Array Size : 35566400 (33.92 GiB 36.42 GB)
|    Raid Devices : 2
|   Total Devices : 1
| Preferred Minor : 0
|     Persistence : Superblock is persistent
|     Update Time : Fri Sep 10 18:20:49 2004
|           State : clean, degraded
|  Active Devices : 1
| Working Devices : 1
|  Failed Devices : 0
|   Spare Devices : 0
|     Number   Major   Minor   RaidDevice State
|        0       8       16        0      active sync   /dev/zfcp/0x2100002037470047/0x0000000000000000/disc
|        1       0        0       -1      removed
|            UUID : ac88c560:ad6b1e3d:211de7b0:5d562f61
|          Events : 0.9
| # dmesg
| [...]
| md: bind<sdb>
| md: bind<sda>
| multipath: array md0 active with 2 out of 2 IO paths
| md: md0 stopped.
| md: unbind<sda>
| md: export_rdev(sda)
| md: unbind<sdb>
| md: export_rdev(sdb)
| md: md0 stopped.
| md: bind<sdb>
| md: export_rdev(sda)
| multipath: array md0 active with 1 out of 2 IO paths
| # l /dev/zfcp/*/*/*
| brw-rw----  1 root root 8, 16 Sep 10 17:56 /dev/zfcp/0x2100002037470047/0x0000000000000000/disc
| brw-rw----  1 root root 8,  0 Sep 10 17:56 /dev/zfcp/0x2200002037470047/0x0000000000000000/disc

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: s390
Kernel: Linux 2.6.8-1-s390x

Star Trek Lives!

Attachment: signature.asc
Description: Digital signature

--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 2.4.1-2

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:

  to pool/main/m/mdadm/mdadm-udeb_2.4.1-2_i386.udeb
  to pool/main/m/mdadm/mdadm_2.4.1-2.diff.gz
  to pool/main/m/mdadm/mdadm_2.4.1-2.dsc
  to pool/main/m/mdadm/mdadm_2.4.1-2_i386.deb

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

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

Debian distribution maintenance software
martin f. krafft <madduck@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)

Hash: SHA1

Format: 1.7
Date: Wed, 31 May 2006 23:07:48 +0200
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 2.4.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian/Ubuntu mdadm maintainers <pkg-mdadm-devel@lists.alioth.debian.org>
Changed-By: martin f. krafft <madduck@debian.org>
 mdadm      - tool to administer Linux MD device arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD device arrays (software RAID) (udeb)
Closes: 271033 299623 310247 318230 321751 323950 323988 333486 337903 344714 345667 345669 352798 356153 360290 361116 363592
 mdadm (2.4.1-2) unstable; urgency=low
   * The "this took way longer than I thought" release.
   * Migrating to unstable.
   * If the init.d script creates the mdadm.conf file, it should remove it on
     purge. To accomplish this, I create a semaphore in /var/lib/mdadm if it
     was generated, and only remove the conffile on purge if the semaphore
   * Added a little helper /usr/share/mdadm/mkconf to aid generation of
     configuration file.
   * Added a bug script to collect some important information when the user
     uses Debian bug reporting tools (such as reportbug).
   * Added a debian/watch file.
 mdadm (2.4.1-1) experimental; urgency=low
   * The "I'll kill that maintainer... uh, wait, it's me" release. Sorry for
     the delay, here's the long awaited new upstream release,
     which closes: Bug#318230, Bug#321751, Bug#337903, Bug#352798, Bug#363592,
                   Bug#356153, Bug#271033
     Oh, and we're moving away from that arch nightmare too. Sorry for the
   * Experimental release, because I really don't want to be responsible for
     data loss. Though I am quite sure that the upgrade is painless, I also
     don't have access to 18 drive RAID 10 with multipath on s390 or similar
   * We now make the /dev/md* devices in postinst unless /dev/md15 exists (no
     longer checking for /dev/md0), or unless devfs is in use. If udev is used,
     /dev/md15 will only exist in complex setups, so the devices will be made
     in /dev/.static by MAKEDEV, which is not really a concern. I opted against
     unconditionally calling MAKEDEV until #367407 is fixed so as to preserve
     custom permissions or owner settings. This also acknowledges the NMU
     closes: Bug#310247, Bug#299623
   * Patched some of the code to make mdadm honour /etc/mdadm/mdadm.conf over
     /etc/mdadm.conf (see NEWS).
   * Fixed a couple of typos in the mdadm(8) manpage; thanks to Reuben Thomas.
     closes: Bug#345669, Bug#345667
   * Pushed Standards-Version to 3.7.2; no changes required.
   * Updated Debconf translations:
     - Vietnamese by Clytie Siddall (closes: Bug#323950)
     - Czech by Miroslav Kure (closes: Bug#360290)
     - Russian by Yuri Kozlov (closes: Bug#361116)
     - French by Eric Madesclair (closes: Bug#323988)
   * Added new Debconf translations:
     - Swedish by Daniel Nylander (closes: Bug#333486)
     - Dutch by Frans Pop (closes: Bug#344714)
 903361e3e085c58ee8b47f25412a52ca 719 admin optional mdadm_2.4.1-2.dsc
 62f7d6779cf7f4b3b85915999e0d0e1a 41979 admin optional mdadm_2.4.1-2.diff.gz
 c11656ab6878c901f21ad5a0de43e6c6 148264 admin optional mdadm_2.4.1-2_i386.deb
 3618c53f064f245931a77c2619a1698d 70378 debian-installer optional mdadm-udeb_2.4.1-2_i386.udeb
Package-Type: udeb

Version: GnuPG v1.4.3 (GNU/Linux)


--- End Message ---

Reply to: