Your message dated Thu, 05 Feb 2009 19:47:10 +0000
with message-id <e1lvabq-00077h...@ries.debian.org>
and subject line Bug#499643: fixed in mdadm 2.6.7.2-1
has caused the Debian Bug report #499643,
regarding Segmentation fault when attempting re-assembly of a failed RAID5 via
"mdadm -v -A --run --force"
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 ow...@bugs.debian.org
immediately.)
--
499643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Version: 2.6.7-3.1
Severity: normal
The system is a clean 1-day old installation of Lenny.
Doing tests of RAID re-assembly, by failing devices and having mdadm rebuild
them. Had manually failed 2 devices on a 5-drive RAID5, causing it to stop.
All attempts at forced re-assembly ended with SegFault, e.g.
# mdadm -v -A --force --run /dev/md0 /dev/loop[0-4]
mdadm: looking for devices for /dev/md0
mdadm: /dev/loop0 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/loop1 is identified as a member of /dev/md0, slot 5.
mdadm: /dev/loop2 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/loop3 is identified as a member of /dev/md0, slot 3.
mdadm: /dev/loop4 is identified as a member of /dev/md0, slot 1.
mdadm: forcing event count in /dev/loop4(1) from 74 upto 80
Segmentation fault
After many retries and failures, I downloaded older version of
mdadm v2.6.4 from neilb's site and compiled it and it worked fine
(no segfault):
# ./mdadm -v -A --run --force /dev/md0 /dev/loop0 /dev/loop2 /dev/loop3 /dev/loo
p4 /dev/loop1
mdadm: looking for devices for /dev/md0
mdadm: /dev/loop0 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/loop2 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/loop3 is identified as a member of /dev/md0, slot 3.
mdadm: /dev/loop4 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/loop1 is identified as a member of /dev/md0, slot 5.
mdadm: forcing event count in /dev/loop4(1) from 74 upto 80
mdadm: clearing FAULTY flag for device 3 in /dev/md0 for /dev/loop4
mdadm: added /dev/loop4 to /dev/md0 as 1
mdadm: added /dev/loop2 to /dev/md0 as 2
mdadm: added /dev/loop3 to /dev/md0 as 3
mdadm: no uptodate device for slot 4 of /dev/md0
mdadm: added /dev/loop1 to /dev/md0 as 5
mdadm: added /dev/loop0 to /dev/md0 as 0
mdadm: /dev/md0 has been started with 4 drives (out of 5) and 1 spare.
Perhaps Lenny could consider the older, apparently more stable version
of mdadm?
-- Package-specific info:
--- mount output
/dev/hda1 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/hda9 on /home type ext3 (rw)
/dev/hda8 on /tmp type ext3 (rw)
/dev/hda5 on /usr type ext3 (rw)
/dev/hda6 on /var 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 Sat, 20 Sep 2008 02:37:26 +0300
# by mkconf $Id$
--- /proc/mdstat:
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
[raid10]
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
3 0 78177792 hda
3 1 273073 hda1
3 2 1 hda2
3 5 4883728 hda5
3 6 2931831 hda6
3 7 2176776 hda7
3 8 393561 hda8
3 9 67513131 hda9
7 0 262144 loop0
7 1 262144 loop1
7 2 262144 loop2
7 3 262144 loop3
7 4 262144 loop4
7 5 262144 loop5
--- initrd.img-2.6.26-1-686:
29479 blocks
scripts/local-top/mdadm
sbin/mdadm
lib/modules/2.6.26-1-686/kernel/drivers/md/md-mod.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/raid10.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/multipath.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/dm-mod.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/raid456.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/raid1.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/dm-log.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/dm-mirror.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/linear.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/raid0.ko
etc/mdadm
etc/mdadm/mdadm.conf
--- /proc/modules:
raid10 18560 0 - Live 0xee94a000
raid456 117264 0 - Live 0xee964000
async_xor 3520 1 raid456, Live 0xee91a000
async_memcpy 2304 1 raid456, Live 0xee918000
async_tx 6284 3 raid456,async_xor,async_memcpy, Live 0xee8cf000
xor 14696 2 raid456,async_xor, Live 0xee926000
raid1 18016 0 - Live 0xee920000
raid0 6368 0 - Live 0xee8ae000
multipath 6112 0 - Live 0xee83b000
linear 4544 0 - Live 0xee866000
md_mod 67036 6 raid10,raid456,raid1,raid0,multipath,linear, Live 0xee930000
dm_mirror 15104 0 - Live 0xee818000
dm_log 8452 1 dm_mirror, Live 0xee8a6000
dm_mod 46184 2 dm_mirror,dm_log, Live 0xee8c2000
--- /var/log/syslog:
--- volume detail:
--- /proc/cmdline
root=/dev/hda1 ro quiet
--- grub:
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro quiet
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro quiet single
kernel /boot/vmlinuz-2.6.24-1-686 root=/dev/hda1 ro quiet
kernel /boot/vmlinuz-2.6.24-1-686 root=/dev/hda1 ro quiet single
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
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.22 Debian configuration management sy
ii libc6 2.7-13 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-6 /dev/ and hotplug management daemo
Versions of packages mdadm recommends:
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
ii postfix [mail-transport-agent 2.5.5-1.1 High-performance mail transport ag
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
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 2.6.7.2-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.6.7.2-1_amd64.udeb
to pool/main/m/mdadm/mdadm-udeb_2.6.7.2-1_amd64.udeb
mdadm_2.6.7.2-1.diff.gz
to pool/main/m/mdadm/mdadm_2.6.7.2-1.diff.gz
mdadm_2.6.7.2-1.dsc
to pool/main/m/mdadm/mdadm_2.6.7.2-1.dsc
mdadm_2.6.7.2-1_amd64.deb
to pool/main/m/mdadm/mdadm_2.6.7.2-1_amd64.deb
mdadm_2.6.7.2.orig.tar.gz
to pool/main/m/mdadm/mdadm_2.6.7.2.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 499...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
martin f. krafft <madd...@debian.org> (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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 03 Feb 2009 21:28:34 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 2.6.7.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers <pkg-mdadm-de...@lists.alioth.debian.org>
Changed-By: martin f. krafft <madd...@debian.org>
Description:
mdadm - tool to administer Linux MD arrays (software RAID)
mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 496334 498505 499643 506245 506572 512475
Changes:
mdadm (2.6.7.2-1) unstable; urgency=low
.
* New upstream release, created for Debian lenny:
- fixes assembly of arrays that are being reshaped (closes: #512475)
- this bug was also responsible for other assembly problems
(closes: #498505, #499643, #496334)
Again, many thanks to Neil Brown for being such an awesome upstream.
.
* Documentation updates:
- Actually install David Pashley's blog post added in 2.6.7.1-1, and
register it with doc-base.
- Update md.txt to version 2.6.26 (the lenny kernel).
- Add a dump of a website detailing md superblock formats.
- Register FAQ, md.txt, RAID5-vs-RAID10, README.recipes with doc-base
- Cherry-picked UID/UUID typo in mdadm.conf(5) manpage fix (commit
0e69da7) (closes: #506245).
.
* Added Italian debconf translation; thanks Luca Monducci (closes: #506572).
Checksums-Sha1:
6c02822c6edb33544e9cfe7b6f856031d5b6ce47 1267 mdadm_2.6.7.2-1.dsc
164b5feed65cd161ce6ca8f2434aee6cde33323e 212733 mdadm_2.6.7.2.orig.tar.gz
885b3171623e64439a9bebb7861af236cc8039ea 136198 mdadm_2.6.7.2-1.diff.gz
9f06887878ce87f8c014a56693adf91c0d18e153 272038 mdadm_2.6.7.2-1_amd64.deb
611aead8344fcbf5c66b98ba3b2642fb2638d5e3 76816 mdadm-udeb_2.6.7.2-1_amd64.udeb
Checksums-Sha256:
2d766a8d1cd4d9d938dcc3ba55208d6c756f3f04f94f0de097dc7d4e6889afb9 1267
mdadm_2.6.7.2-1.dsc
875a1b614f32175bf20aca497d9b9ae3129e6e5e196f3f8383630abe1b00bc92 212733
mdadm_2.6.7.2.orig.tar.gz
e8bb9aa6c384d8a731a8d0839ad45118c031f4237a4f42188adc78b5cc81b1e2 136198
mdadm_2.6.7.2-1.diff.gz
4d894413955c8eaa5b388bf1d3fdbae054a0ef2d9a811796de8ff2d5f93163ef 272038
mdadm_2.6.7.2-1_amd64.deb
6ecb62a1cb4683735d88e84321ae7f0ccc41cb76fa885ccf6eb5f805ea0e65db 76816
mdadm-udeb_2.6.7.2-1_amd64.udeb
Files:
f22f157fa4518df97d788cc4e20c9978 1267 admin optional mdadm_2.6.7.2-1.dsc
e4badb4a8ded4344ba0fa785883955d8 212733 admin optional
mdadm_2.6.7.2.orig.tar.gz
f4c16deea6d3873370a03ae256eb7f7b 136198 admin optional mdadm_2.6.7.2-1.diff.gz
688e86e3f3473d6c63bc8c0464a35020 272038 admin optional
mdadm_2.6.7.2-1_amd64.deb
0100062e906652b5dfc19fd676b2f143 76816 debian-installer optional
mdadm-udeb_2.6.7.2-1_amd64.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkmLPXkACgkQIgvIgzMMSnWhzQCg0xl9pkQ7HulpN3EtC82jGTvw
l9IAn0ZBkknArQwkDD90MZY+s4DraqNW
=V4RU
-----END PGP SIGNATURE-----
--- End Message ---
