Your message dated Wed, 13 Sep 2006 05:47:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#384614: fixed in mdadm 2.5.3.git200608202239-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)

--- Begin Message ---
Package: mdadm
Version: 2.5.3.git200608202239-2
Severity: grave

| # mdadm --create -l 1 -n 2 /dev/md0 /dev/sdb2 missing 
| mdadm: /dev/sdb2 appears to be part of a raid array:
|     level=raid1 devices=2 ctime=Fri Aug 25 08:36:37 2006
| mdadm: ADD_NEW_DISK for /dev/sdb2 failed: Invalid argument
| md: invalid superblock checksum on sdb2
| md: sdb2 has invalid sb, not importing!
| md: md_import_device returned -22
| # mdadm -Q /dev/sdb2 --examine
| /dev/sdb2:
|           Magic : a92b4efc
|         Version : 01
|     Feature Map : 0x0
|      Array UUID : b1ffb858:a3939b9e:ed702d8a:42b61d1e
|            Name : 0
|   Creation Time : Fri Aug 25 08:37:30 2006
|      Raid Level : raid1
|    Raid Devices : 2
| 
|     Device Size : 12683610995768164352 (15875456.35 GiB -18178225.-
|      Array Size : 12683610995768164352 (15875456.35 GiB -18178225.-
|    Super Offset : 3999152 sectors
|           State : active
|     Device UUID : 6e0b6282:1a0e0cc6:817db255:9f7d49aa
| 
|     Update Time : Fri Aug 25 08:37:30 2006
|        Checksum : 50fc91a - correct
|          Events : 0
| 
| 
|     Array Slot : 0 (0, 65279)
|    Array State : U_
| # uname -a
| Linux zee 2.6.17-2-sparc64-smp #1 SMP Sat Aug 12 19:08:00 BST 2006 sparc64 
GNU/Linux

Bastian

-- 
... The prejudices people feel about each other disappear when they get
to know each other.
                -- Kirk, "Elaan of Troyius", stardate 4372.5


--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 2.5.3.git200608202239-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_2.5.3.git200608202239-3_i386.udeb
  to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-3_i386.udeb
mdadm_2.5.3.git200608202239-3.diff.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-3.diff.gz
mdadm_2.5.3.git200608202239-3.dsc
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-3.dsc
mdadm_2.5.3.git200608202239-3_i386.deb
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-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: Thu,  7 Sep 2006 14:32:04 +0200
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 2.5.3.git200608202239-3
Distribution: unstable
Urgency: medium
Maintainer: Debian mdadm maintainers <[EMAIL PROTECTED]>
Changed-By: martin f. krafft <[EMAIL PROTECTED]>
Description: 
 mdadm      - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 384614 384754 385017 385690 385951 385994 386468 387017
Changes: 
 mdadm (2.5.3.git200608202239-3) unstable; urgency=medium
 .
   * Urgency medium because of RC bugs.
   * Add versioned dependency to debconf (closes: #385994); temporary fix until
     we find a proper fix for #386439.
   * Add patch by Steinar H. Gunderson to ensure mdadm does not interpret
     a superblock as belonging to a device when it's actually part of
     a partition on that device (closes: #385951).
   * Do not override the superblock default version in mdadm.conf to prevent
     creation of superblocks that the kernel can't handle (closes: #384614).
   * Added a note to alert people that the warning about arrays not listed in
     the configuration file is only relevant if the arrays are needed to be
     brought up by mdadm from initramfs during boot (closes: #385017).
   * Added bootloader/cmdline info to bugscript so that future bug reports via
     bug/reportbug include information on how the system is booted with respect
     to RAID (the root partition).
   * If mdadm is being configured in a chroot, it now defaults to starting all
     arrays from the initial ramdisk, rather than trying to figure out the root
     MD array (we're using /proc information, so it would be the one of the
     host, not the one of the chroot) (closes: #386468).
   * Added LSB headers to init scripts.
   * Reworked the documentation with respect to the use of "MD" and "RAID", and
     added a FAQ entry on the meaning of "MD". Thanks to Frans Pop for his
     help!
   * Updated debconf translations:
     - Czech by Miroslav Kure (closes: #384754).
     - French by Florentin Duneau (closes: #385690).
     - Russian by Yuri Kozlov (closes: #387017).
Files: 
 ab3afa3d115d66238d13f5b59312a123 760 admin optional 
mdadm_2.5.3.git200608202239-3.dsc
 c66a67dc5d71ae8b1a99f9ad121718b1 89230 admin optional 
mdadm_2.5.3.git200608202239-3.diff.gz
 eff02d5b331491a5e84be2e05ebe1870 198692 admin optional 
mdadm_2.5.3.git200608202239-3_i386.deb
 ed4e1efa7c3e782a5f0045d7a9b82324 68348 debian-installer optional 
mdadm-udeb_2.5.3.git200608202239-3_i386.udeb
Package-Type: udeb

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

iD8DBQFFB/WXIgvIgzMMSnURApjdAKCGM7Um0aJpgzXF6CCwLHmBhMEPKgCg0HPu
GOzEoOXeoK3R3xbEy3rBxCU=
=Ys1W
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to