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/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
