Your message dated Wed, 27 Jan 2010 12:15:19 +0000
with message-id <[email protected]>
and subject line Bug#398310: fixed in mdadm 3.1.1-1+incremental
has caused the Debian Bug report #398310,
regarding let user choose when to start which array
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
398310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398310
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mdadm
Version: 2.5.5-1
Severity: grave
it's dangerous to generate an mdadm.conf and start running arrays
automatically at install time! i nearly got bit by this.
i marked this grave because there's a potential for data loss with the
current install scripts.
i had 4 disks which i had experimented with sw raid10 on a few months
back... i never zeroed the superblocks. i ended up putting them into
production in a 3ware hw raid10. today the 3ware freaked out... and i put
the disks into another box to attempt forensics and to try constructing
*read-only* software arrays to see if i could recover the data.
when i did "apt-get install mdadm" it found the old superblocks from my
experiments a few months ago... and tried to start the array!
fortunately i had issued "blockdev --setro /dev/sd[defg]" prior to doing
any of this, so the block layer saved my ass.
otherwise mdadm would have happily screwed around with the data at the end
of the disks... and *even worse* might have decided recovery was necessary
and really screwed things up!
it's *bad* to autostart all discovered arrays. it's unfortunate enough
that you've decided to make initrds start all arrays by default... but at
least this install-time autodiscover and start everything should be
optional.
at a minimum i think there should be a dialog "attempt to autodiscover all
arrays and start them?". even better would be a second step "i found the
following arrays, which ones should i start?"
-dean
p.s. regardless of this complaint, i'm totally happy with the newer
initramfs which handles renames more gracefully... and with the monthly
checkarray default. thanks!
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 3.1.1-1+incremental
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_3.1.1-1+incremental_amd64.udeb
to main/m/mdadm/mdadm-udeb_3.1.1-1+incremental_amd64.udeb
mdadm_3.1.1-1+incremental.debian.tar.gz
to main/m/mdadm/mdadm_3.1.1-1+incremental.debian.tar.gz
mdadm_3.1.1-1+incremental.dsc
to main/m/mdadm/mdadm_3.1.1-1+incremental.dsc
mdadm_3.1.1-1+incremental_amd64.deb
to main/m/mdadm/mdadm_3.1.1-1+incremental_amd64.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: RIPEMD160
Format: 1.8
Date: Wed, 27 Jan 2010 14:42:16 +1300
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 3.1.1-1+incremental
Distribution: experimental
Urgency: low
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: 398310 521547
Changes:
mdadm (3.1.1-1+incremental) experimental; urgency=low
.
* Add EXPERIMENTAL support for incrementally assembling arrays based on udev
events (closes: #398310, #521547).
* Ignore lintian error about not stopping in runlevel 1.
Checksums-Sha1:
fae40765fe47e3ffb74faa00045d7efb33d09f89 1312 mdadm_3.1.1-1+incremental.dsc
112ce887cc13a9a60cc0cda2a6d42ab2764c5b8a 132995
mdadm_3.1.1-1+incremental.debian.tar.gz
75a023f9b41ae78e6ec44556ad1b55d8401854aa 444746
mdadm_3.1.1-1+incremental_amd64.deb
ad82bc12ed458aa60e9a3f9a8b4b2a15fcc56b66 142188
mdadm-udeb_3.1.1-1+incremental_amd64.udeb
Checksums-Sha256:
ac4b5167346f61c011e25360e9bebcd2664df0312cfb68568a673798da9c2c40 1312
mdadm_3.1.1-1+incremental.dsc
0e90832f33b06e2533a5ea0ce16aa1cfb9b3ffc048f8ae0bb7929d669ffa5f87 132995
mdadm_3.1.1-1+incremental.debian.tar.gz
7bedac4a560a144eaa1d8cedc1ef571020ec4571f61f336eed04720c8614c126 444746
mdadm_3.1.1-1+incremental_amd64.deb
f24bdc13150d00d8375be4cbb1a8cd44dbbc997e7c9e423e135aa465b2fed326 142188
mdadm-udeb_3.1.1-1+incremental_amd64.udeb
Files:
e9cb363547f16aa6419f5308b91b72ab 1312 admin optional
mdadm_3.1.1-1+incremental.dsc
1e0d732b504b15e124a042bd39dd65fa 132995 admin optional
mdadm_3.1.1-1+incremental.debian.tar.gz
6f43f69ae6d409298664317e889739d0 444746 admin optional
mdadm_3.1.1-1+incremental_amd64.deb
6f8ceada4fe38f0da6bf9142e83136a3 142188 debian-installer optional
mdadm-udeb_3.1.1-1+incremental_amd64.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAktgDL4ACgkQIgvIgzMMSnUmMgCgvn8UQviiEoFTg2ApvQaZG1JM
9loAniqdLShwfnDscQkbNtUw/Diy3Cyy
=8pWp
-----END PGP SIGNATURE-----
--- End Message ---
