Bug#510261: mdadm: After install if sync is not done when rebooting, it starts over
John McMonagle
johnm at advocap.org
Tue Dec 30 21:14:31 UTC 2008
Package: mdadm
Version: 2.6.7.1-1
Severity: normal
Did a couple raid1 installs of lenny lately.
This one amd64 another a 32 bit install.
In both cases I rebooted before the sync was done.
In both cases arrays re-synced from the beginning.
After it finished syncing a reboot does not cause a re-sync.
I did not touch any mdadm configuration files.
John
-- Package-specific info:
--- mount output
/dev/md0 on / type ext3 (rw,noatime,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)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/mapper/vg0-home on /home type xfs (rw,noatime)
/dev/mapper/vg0-tmp on /tmp type xfs (rw,noatime)
/dev/mapper/vg0-local on /usr/local type xfs (rw,noatime)
/dev/mapper/vg0-var on /var type xfs (rw,noatime)
/dev/mapper/vg0-work on /work type xfs (rw,noatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
server:/extra on /extra type nfs
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,nfsvers=3,tcp,addr=192.168.101.1)
server:/backup on /backup type nfs
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,nfsvers=3,tcp,addr=192.168.101.1)
server:/shared/main on /main type nfs
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,nfsvers=3,tcp,addr=192.168.101.1)
server:/home on /homejm type nfs
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,nfsvers=3,tcp,addr=192.168.101.1)
server:/video on /video type nfs4
(rw,noexec,nodev,noatime,rsize=32768,wsize=32768,addr=192.168.101.1)
fondy:/home on /fondy type nfs4
(rw,nodev,sync,proto=tcp,retry=10,rsize=32768,wsize=32768,hard,intr,addr=192.168.2.1)
--- 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
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=0d8df827:0de622b7:82658f7d:40808bc9
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=a575b291:eb792299:1d6cd8aa:0f2a4770
# This file was auto-generated on Fri, 19 Dec 2008 18:05:14 -0600
# by mkconf $Id$
--- /proc/mdstat:
Personalities : [raid1]
md1 : active raid1 sda2[0] sdb2[1]
371173696 blocks [2/2] [UU]
bitmap: 2/177 pages [8KB], 1024KB chunk
md0 : active raid1 sda1[0] sdb1[1]
19534912 blocks [2/2] [UU]
bitmap: 0/150 pages [0KB], 64KB chunk
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
8 0 488386584 sda
8 1 19535008 sda1
8 2 371189857 sda2
8 3 1 sda3
8 5 19535008 sda5
8 16 390711384 sdb
8 17 19535008 sdb1
8 18 371173792 sdb2
9 0 19534912 md0
9 1 371173696 md1
253 0 26214400 dm-0
253 1 2097152 dm-1
253 2 2097152 dm-2
253 3 2097152 dm-3
253 4 41943040 dm-4
253 5 2097152 dm-5
--- initrd.img-2.6.26-1-amd64:
44415 blocks
etc/mdadm
etc/mdadm/mdadm.conf
lib/modules/2.6.26-1-amd64/kernel/drivers/md/dm-mod.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/dm-snapshot.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/dm-log.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/dm-mirror.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/md-mod.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/linear.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/multipath.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/raid0.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/raid1.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/raid456.ko
lib/modules/2.6.26-1-amd64/kernel/drivers/md/raid10.ko
sbin/mdadm
scripts/local-top/mdadm
--- /proc/modules:
dm_mirror 20608 0 - Live 0xffffffffa0166000
dm_log 13956 1 dm_mirror, Live 0xffffffffa0161000
dm_snapshot 19400 0 - Live 0xffffffffa015b000
dm_mod 58864 16 dm_mirror,dm_log,dm_snapshot, Live 0xffffffffa014b000
raid1 24192 2 - Live 0xffffffffa0144000
md_mod 80164 3 raid1, Live 0xffffffffa012f000
--- volume detail:
--- /proc/cmdline
root=/dev/md0 ro single
--- grub:
module /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/md0 ro console=tty0
kernel /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/md0 ro quiet
kernel /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/md0 ro single
kernel /boot/vmlinuz-2.6.26-1-amd64 root=/dev/md0 ro quiet
kernel /boot/vmlinuz-2.6.26-1-amd64 root=/dev/md0 ro single
kernel /boot/vmlinuz-2.6.27-9-generic root=/dev/md0 ro quiet
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mdadm depends on:
ii debconf 1.5.24 Debian configuration
management sy
ii libc6 2.7-16 GNU C Library: Shared libraries
ii lsb-base 3.2-20 Linux Standard Base 3.2
init scrip
ii makedev 2.3.1-88 creates device files in /dev
ii udev 0.125-7 /dev/ and hotplug
management daemo
Versions of packages mdadm recommends:
ii exim4-daemon-light [mail-tran 4.69-9 lightweight Exim MTA (v4)
daemon
ii module-init-tools 3.4-1 tools for managing Linux
kernel mo
mdadm suggests no packages.
-- debconf information:
mdadm/autostart: true
mdadm/mail_to: root
mdadm/initrdstart_msg_errmd:
mdadm/initrdstart: all
mdadm/initrdstart_msg_errconf:
mdadm/initrdstart_notinconf: false
mdadm/initrdstart_msg_errexist:
mdadm/initrdstart_msg_intro:
mdadm/autocheck: true
mdadm/initrdstart_msg_errblock:
mdadm/start_daemon: true
More information about the pkg-mdadm-devel
mailing list