Bug#465556: mdadm hotadd flag does not work in its shortform
Philipp Wollschlegel
folken at kabelsalat.ch
Wed Feb 13 08:46:54 UTC 2008
Package: mdadm
Version: 2.5.6-9
Severity: normal
mdadm hotadd flag is not interpreted correctly:
debian:/home/folken# mdadm --manage /dev/md1 -a /dev/sda2
the return value of the above is 0. but the raiddevice is not added to the device.
debian:/home/folken# mdadm --manage /dev/md1 --add /dev/sda2
mdadm: added /dev/sda2
normal behaviour as expected.
-- Package-specific info:
--- mount output
/dev/mapper/system-root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/md0 on /boot type ext3 (rw)
--- mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
# This file was auto-generated on Wed, 13 Feb 2008 06:42:00 +0100
# by mkconf $Id: mkconf 261 2006-11-09 13:32:35Z madduck $
--- /proc/mdstat:
Personalities : [raid1]
md1 : active raid1 sda2[2] sdb2[0]
160336640 blocks [2/1] [U_]
[====>................] recovery = 23.0% (36990464/160336640) finish=37.3min speed=55072K/sec
md0 : active raid1 sda1[1] sdb1[0]
497856 blocks [2/2] [UU]
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
31 0 256 mtdblock0
31 1 13312 mtdblock1
31 2 1408 mtdblock2
31 3 1152 mtdblock3
31 4 4 mtdblock4
31 5 128 mtdblock5
8 0 160836480 sda
8 1 497983 sda1
8 2 160336732 sda2
8 16 160836480 sdb
8 17 497983 sdb1
8 18 160336732 sdb2
9 0 497856 md0
9 1 160336640 md1
253 0 5242880 dm-0
253 1 1048576 dm-1
--- initrd.img-2.6.18-6-iop32x:
--- /proc/modules:
dm_mirror 20948 0 - Live 0xbf0cc000
dm_snapshot 17180 0 - Live 0xbf0c6000
dm_mod 59120 7 dm_mirror,dm_snapshot, Live 0xbf0b6000
raid1 23488 2 - Live 0xbf0af000
md_mod 80628 3 raid1, Live 0xbf09a000
--- /var/log/syslog:
Feb 13 06:41:59 debian kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Feb 13 06:41:59 debian kernel: md: bitmap version 4.39
Feb 13 06:46:40 debian kernel: md: bind<sdb1>
Feb 13 06:46:40 debian kernel: md: md0: raid array is not clean -- starting background reconstruction
Feb 13 06:46:40 debian kernel: md: raid1 personality registered for level 1
Feb 13 06:46:40 debian mdadm: NewArray event detected on md device /dev/md0
Feb 13 06:46:40 debian mdadm: DegradedArray event detected on md device /dev/md0
Feb 13 06:46:49 debian kernel: md: bind<sdb2>
Feb 13 06:46:49 debian kernel: md: md1: raid array is not clean -- starting background reconstruction
Feb 13 06:46:49 debian mdadm: NewArray event detected on md device /dev/md1
Feb 13 06:46:49 debian mdadm: DegradedArray event detected on md device /dev/md1
Feb 13 07:12:14 debian kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Feb 13 07:12:14 debian kernel: md: bitmap version 4.39
Feb 13 07:12:14 debian kernel: md: raid1 personality registered for level 1
Feb 13 07:12:14 debian kernel: md: md0 stopped.
Feb 13 07:12:14 debian kernel: md: bind<sdb1>
Feb 13 07:12:14 debian kernel: md: md1 stopped.
Feb 13 07:12:14 debian kernel: md: bind<sdb2>
Feb 13 07:12:49 debian mdadm: NewArray event detected on md device /dev/md1
Feb 13 07:12:49 debian mdadm: NewArray event detected on md device /dev/md0
Feb 13 07:12:49 debian mdadm: DegradedArray event detected on md device /dev/md0
Feb 13 07:12:50 debian mdadm: DegradedArray event detected on md device /dev/md1
Feb 13 07:50:31 debian kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Feb 13 07:50:31 debian kernel: md: bitmap version 4.39
Feb 13 07:50:31 debian kernel: md: raid1 personality registered for level 1
Feb 13 07:50:31 debian kernel: md: md0 stopped.
Feb 13 07:50:31 debian kernel: md: bind<sdb1>
Feb 13 07:50:31 debian kernel: md: md1 stopped.
Feb 13 07:50:31 debian kernel: md: bind<sdb2>
Feb 13 09:18:35 debian kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Feb 13 09:18:35 debian kernel: md: bitmap version 4.39
Feb 13 09:18:35 debian kernel: md: raid1 personality registered for level 1
Feb 13 09:18:35 debian kernel: md: md0 stopped.
Feb 13 09:18:35 debian kernel: md: bind<sdb1>
Feb 13 09:18:35 debian kernel: md: md1 stopped.
Feb 13 09:18:35 debian kernel: md: bind<sdb2>
Feb 13 09:19:11 debian mdadm: NewArray event detected on md device /dev/md1
Feb 13 09:19:11 debian mdadm: NewArray event detected on md device /dev/md0
Feb 13 09:19:11 debian mdadm: DegradedArray event detected on md device /dev/md0
Feb 13 09:19:12 debian mdadm: DegradedArray event detected on md device /dev/md1
Feb 13 09:28:05 debian kernel: md: bind<sda1>
Feb 13 09:28:05 debian kernel: md: syncing RAID array md0
Feb 13 09:28:05 debian kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Feb 13 09:28:05 debian kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Feb 13 09:28:05 debian kernel: md: using 128k window, over a total of 497856 blocks.
Feb 13 09:28:05 debian mdadm: RebuildStarted event detected on md device /dev/md0
Feb 13 09:28:14 debian kernel: md: md0: sync done.
Feb 13 09:28:14 debian mdadm: RebuildFinished event detected on md device /dev/md0
Feb 13 09:28:14 debian mdadm: SpareActive event detected on md device /dev/md0, component device /dev/sda1
Feb 13 09:31:37 debian kernel: md: bind<sda2>
Feb 13 09:31:37 debian kernel: md: syncing RAID array md1
Feb 13 09:31:37 debian kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Feb 13 09:31:37 debian kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Feb 13 09:31:37 debian kernel: md: using 128k window, over a total of 160336640 blocks.
Feb 13 09:31:37 debian mdadm: RebuildStarted event detected on md device /dev/md1
Feb 13 09:42:37 debian mdadm: Rebuild20 event detected on md device /dev/md1
--- volume detail:
/dev/sda1:
Magic : a92b4efc
Version : 00.90.00
UUID : a4c022f2:773bc777:9d4deba6:47ca997f
Creation Time : Wed Feb 13 06:46:40 2008
Raid Level : raid1
Device Size : 497856 (486.27 MiB 509.80 MB)
Array Size : 497856 (486.27 MiB 509.80 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Wed Feb 13 09:28:14 2008
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 39ac8694 - correct
Events : 0.34
Number Major Minor RaidDevice State
this 1 8 1 1 active sync /dev/sda1
0 0 8 17 0 active sync /dev/sdb1
1 1 8 1 1 active sync /dev/sda1
--
/dev/sda2:
Magic : a92b4efc
Version : 00.90.00
UUID : c00c0756:ec0f9c2f:9d4deba6:47ca997f
Creation Time : Wed Feb 13 06:46:49 2008
Raid Level : raid1
Device Size : 160336640 (152.91 GiB 164.18 GB)
Array Size : 160336640 (152.91 GiB 164.18 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Update Time : Wed Feb 13 09:43:15 2008
State : clean
Active Devices : 1
Working Devices : 2
Failed Devices : 1
Spare Devices : 1
Checksum : d3533b5a - correct
Events : 0.780
Number Major Minor RaidDevice State
this 2 8 2 2 spare /dev/sda2
0 0 8 18 0 active sync /dev/sdb2
1 1 0 0 1 faulty removed
2 2 8 2 2 spare /dev/sda2
--
/dev/sdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : a4c022f2:773bc777:9d4deba6:47ca997f
Creation Time : Wed Feb 13 06:46:40 2008
Raid Level : raid1
Device Size : 497856 (486.27 MiB 509.80 MB)
Array Size : 497856 (486.27 MiB 509.80 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Wed Feb 13 09:28:14 2008
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 39ac86a2 - correct
Events : 0.34
Number Major Minor RaidDevice State
this 0 8 17 0 active sync /dev/sdb1
0 0 8 17 0 active sync /dev/sdb1
1 1 8 1 1 active sync /dev/sda1
--
/dev/sdb2:
Magic : a92b4efc
Version : 00.90.00
UUID : c00c0756:ec0f9c2f:9d4deba6:47ca997f
Creation Time : Wed Feb 13 06:46:49 2008
Raid Level : raid1
Device Size : 160336640 (152.91 GiB 164.18 GB)
Array Size : 160336640 (152.91 GiB 164.18 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Update Time : Wed Feb 13 09:43:15 2008
State : clean
Active Devices : 1
Working Devices : 2
Failed Devices : 1
Spare Devices : 1
Checksum : d3533b6c - correct
Events : 0.780
Number Major Minor RaidDevice State
this 0 8 18 0 active sync /dev/sdb2
0 0 8 18 0 active sync /dev/sdb2
1 1 0 0 1 faulty removed
2 2 8 2 2 spare /dev/sda2
--
--- /proc/cmdline
console=ttyS0,115200 root=/dev/ram0 initrd=0xa0800000,42M mem=512M at 0xa0000000
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: arm (armv5tel)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-iop32x
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to de_CH.utf8)
Versions of packages mdadm depends on:
ii debconf [debconf-2.0] 1.5.11etch1 Debian configuration management sy
ii libc6 2.3.6.ds1-13etch4 GNU C Library: Shared libraries
ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip
ii makedev 2.3.1-83 creates device files in /dev
Versions of packages mdadm recommends:
ii exim4-daemon-light [mail-tran 4.63-17 lightweight exim MTA (v4) daemon
ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
-- debconf information:
mdadm/initrdstart_msg_errexist:
mdadm/initrdstart_msg_intro:
mdadm/autostart: true
mdadm/autocheck: true
mdadm/initrdstart_msg_errblock:
mdadm/mail_to: root
mdadm/initrdstart_msg_errmd:
* mdadm/initrdstart: all
mdadm/initrdstart_msg_errconf:
mdadm/initrdstart_notinconf: false
mdadm/start_daemon: true
More information about the pkg-mdadm-devel
mailing list