Your message dated Fri, 13 Oct 2006 00:17:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#386315: fixed in mdadm 2.5.4-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)
--- Begin Message ---
Package: mdadm
Version: 2.5.3.git200608202239-2
While upgrading to 2.5.3 (unstable/git) from 2.5.2-7 (testing) as a
result of not wanting to deal with bug #380746 (sync_action not
writeable for RAID0 arrays) any more, I was instructed to read some
upgrading documentation.
The file /usr/share/doc/mdadm/README.upgrading-2.5.3.gz told me to
verify my mdadm.conf and compare it to the output of the
/usr/share/mdadm/mkconf script. While the two files are somewhat
different otherwise, the big issue I notice is that mkconf gives me two
definitions for my /dev/md0 array and no definitions for my /dev/md2
array. It is possible mkconf got confused, as my /dev/md2 array is
RAID0, and one of the /dev/md0 arrays listed by mkconf is also a RAID0.
The brief summary of my RAID devices is as follows.
md0 RAID1 /dev/sd[cd]1
md1 RAID1 /dev/sd[cd]2
md2 RAID0 /dev/sd[ab]
The outputs of mdadm -D will be appended to the outputs of all this
other stuff I'm about to paste.
##### OUTPUT OF MKCONF
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# scan all partitions (/proc/partitions) for MD superblocks"
DEVICE partitions
# auto-create devices with Debian standard permissions and v1 superblocks
CREATE owner=root group=disk mode=0660 auto=yes metadata=1
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon to send mail alerts to root
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md0 level=raid0 num-devices=2
UUID=088d7624:74a14b32:cf60881f:a8034e02
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=c4ab126b:c19ab9ae:d271e909:7a9d7d27
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=99605587:7a5ed746:9f69a596:22c4d0ce
# This file was auto-generated on Wed, 06 Sep 2006 13:43:58 -0400
# by mkconf $Id: mkconf 120 2006-08-20 21:47:38Z madduck $
##### CURRENT MDADM.CONF
MAILADDR root
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes metadata=1
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=c4ab126b:c19ab9ae:d271e909:7a9d7d27
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=99605587:7a5ed746:9f69a596:22c4d0ce
DEVICE /dev/sd[ab]
ARRAY /dev/md2 devices=/dev/sda,/dev/sdb
##### OUTPUTS FROM MDADM -D
/dev/md0:
Version : 00.90.03
Creation Time : Thu Aug 24 01:44:51 2006
Raid Level : raid1
Array Size : 14651136 (13.97 GiB 15.00 GB)
Device Size : 14651136 (13.97 GiB 15.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Wed Sep 6 13:54:21 2006
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : c4ab126b:c19ab9ae:d271e909:7a9d7d27
Events : 0.352223
Number Major Minor RaidDevice State
0 8 49 0 active sync /dev/sdd1
1 8 33 1 active sync /dev/sdc1
/dev/md1:
Version : 00.90.03
Creation Time : Thu Aug 24 01:45:02 2006
Raid Level : raid1
Array Size : 62814080 (59.90 GiB 64.32 GB)
Device Size : 62814080 (59.90 GiB 64.32 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Wed Sep 6 13:52:04 2006
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 99605587:7a5ed746:9f69a596:22c4d0ce
Events : 0.105855
Number Major Minor RaidDevice State
0 8 50 0 active sync /dev/sdd2
1 8 34 1 active sync /dev/sdc2
/dev/md2:
Version : 00.90.03
Creation Time : Sun Apr 17 20:50:24 2005
Raid Level : raid0
Array Size : 273478208 (260.81 GiB 280.04 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Sun Apr 17 20:50:24 2005
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 64K
UUID : 088d7624:74a14b32:cf60881f:a8034e02
Events : 0.1
Number Major Minor RaidDevice State
0 8 0 0 active sync /dev/sda
1 8 16 1 active sync /dev/sdb
Thanks.
Colin
--
Colin W. Wetherbee
http://www.colinwetherbee.com/
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 2.5.4-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_2.5.4-1_amd64.udeb
to pool/main/m/mdadm/mdadm-udeb_2.5.4-1_amd64.udeb
mdadm_2.5.4-1.diff.gz
to pool/main/m/mdadm/mdadm_2.5.4-1.diff.gz
mdadm_2.5.4-1.dsc
to pool/main/m/mdadm/mdadm_2.5.4-1.dsc
mdadm_2.5.4-1_amd64.deb
to pool/main/m/mdadm/mdadm_2.5.4-1_amd64.deb
mdadm_2.5.4.orig.tar.gz
to pool/main/m/mdadm/mdadm_2.5.4.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.
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: Fri, 13 Oct 2006 08:32:20 +0200
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 2.5.4-1
Distribution: unstable
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: 385726 385951 386315 388172
Changes:
mdadm (2.5.4-1) unstable; urgency=low
.
* New upstream release:
- --examine now reports chunk size also for RAID6 and RAID10
- fix endianness issues with v1 superblocks (closes: #385726) and bitmap
metadata.
- improved message when mdadm detects similar superblocks
(closes: #385951).
- documents that the automatic update of the super-minor field in the
superblock when using a 2.6 kernel only applies to RAID levels 1 and
higher. RAID0 array superblocks must be manually updated
(closes: #386315, #388172).
- removes partition table from any whole device added to an array.
- allow --auto=yes to specify a number; if mdadm determines from the
device name that you want a partitionable array, this number determines
the number of sub-device nodes to create.
* Removed patch previously used to fix #385951 because it's not adequate.
See the bug log for reasons.
Files:
bd5501cafec20ae19546fa80045a0d4d 771 admin optional mdadm_2.5.4-1.dsc
167f6fe5b55a82766cf397377e080bea 177756 admin optional mdadm_2.5.4.orig.tar.gz
4797024e3770a5a8b0d6869b8a13eba1 95117 admin optional mdadm_2.5.4-1.diff.gz
a48bfb8cfd4fcbda08147c55229c881b 212448 admin optional mdadm_2.5.4-1_amd64.deb
cd4dfc752ade07e7fc51d5d6de0cad6f 70754 debian-installer optional
mdadm-udeb_2.5.4-1_amd64.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFLzpmIgvIgzMMSnURAqEwAKCZKsF9ofHdva5bEvNCVbQGIQm+FgCfYqT5
y0gr9ndIvUrEel+aJyp3358=
=iA2L
-----END PGP SIGNATURE-----
--- End Message ---
