Your message dated Thu, 21 Sep 2006 15:47:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#388355: fixed in mdadm 2.5.3.git200608202239-6 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-5 Severity: important Here is the output from aptitude of my upgrade of mdadm <snip> Setting up mdadm (2.5.3.git200608202239-5) ... update-initramfs: Generating /boot/initrd.img-2.6.16-2-amd64-k8 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . /usr/share/mdadm/mkconf: line 77: 8341 Segmentation fault $MDADM --examine --scan --config=partitions W: mdadm: failed to auto-generate temporary mdadm.conf file. W: mdadm: using the unchecked file and hoping for the best... I: mdadm: will start MD array /dev/md1 from the initial ramdisk. I: mdadm: use `dpkg-reconfigure --priority=low mdadm` to change this. </snip> I had to hit CTRL-C here as it just hangs <snip> update-initramfs: Generating /boot/initrd.img-2.6.16-2-amd64-generic W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . /usr/share/mdadm/mkconf: line 77: 10223 Segmentation fault $MDADM --examine --scan --config=partitions W: mdadm: failed to auto-generate temporary mdadm.conf file. W: mdadm: using the unchecked file and hoping for the best... I: mdadm: will start MD array /dev/md1 from the initial ramdisk. I: mdadm: use `dpkg-reconfigure --priority=low mdadm` to change this. </snip> I hit CTRL-C again just to tell aptitude to quit trying this package My largest concern right now, is what happens when I reboot? -- Package-specific info: --- mount output /dev/md1 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) /sys on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,nodev) /dev/md0 on /boot type ext3 (rw) /dev/md4 on /home type ext3 (rw) /dev/md3 on /usr type ext3 (rw) /dev/md2 on /var type ext3 (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) --- mdadm.conf DEVICE partitions ARRAY /dev/md4 level=raid1 num-devices=2 UUID=9036ff0f:f69b9dff:0366ed22:ac2f9ff9 ARRAY /dev/md3 level=raid1 num-devices=2 UUID=5a95f245:e8ef8ece:ac213102:fec16e93 ARRAY /dev/md2 level=raid1 num-devices=2 UUID=e501db1f:eff938b9:e16fb903:83614185 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=94d4c9bb:76fe218d:958dc611:99fce453 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=a7bc7ae5:b643b1c2:44e1fa02:314d47a9 MAILADDR root --- /proc/mdstat: Personalities : [raid1] md0 : active raid1 sda1[0] sdb1[1] 256896 blocks [2/2] [UU] md2 : active raid1 sda6[0] sdb6[1] 5004096 blocks [2/2] [UU] md3 : active raid1 sda7[0] sdb7[1] 20008832 blocks [2/2] [UU] md4 : active raid1 sda8[0] sdb8[1] 130849280 blocks [2/2] [UU] md1 : active raid1 sda5[0] sdb5[1] 2008000 blocks [2/2] [UU] unused devices: <none> --- /proc/partitions: major minor #blocks name 8 0 199148544 sda 8 1 257008 sda1 8 3 1004062 sda3 8 4 1 sda4 8 5 2008093 sda5 8 6 5004216 sda6 8 7 20008926 sda7 8 8 130849393 sda8 8 16 199148544 sdb 8 17 257008 sdb1 8 19 1004062 sdb3 8 20 1 sdb4 8 21 2008093 sdb5 8 22 5004216 sdb6 8 23 20008926 sdb7 8 24 130849393 sdb8 3 0 80043264 hda 3 1 6835720 hda1 3 2 1 hda2 3 5 500440 hda5 3 6 62960152 hda6 3 7 9746824 hda7 9 1 2008000 md1 9 4 130849280 md4 9 3 20008832 md3 9 2 5004096 md2 9 0 256896 md0 --- initrd.img-2.6.17-1-amd64-k8: zcat: /boot/initrd.img-2.6.17-1-amd64-k8: unexpected end of file cpio: premature end of file etc/mdadm etc/mdadm/mdadm.conf lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/md-mod.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/linear.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/multipath.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid0.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid1.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/xor.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid5.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid6.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid10.ko --- /proc/modules: dm_snapshot 17592 0 - Live 0xffffffff88153000 dm_mirror 20928 0 - Live 0xffffffff8814c000 dm_mod 62256 2 dm_snapshot,dm_mirror, Live 0xffffffff8813b000 raid1 22784 5 - Live 0xffffffff880f0000 md_mod 80988 6 raid1, Live 0xffffffff880db000 --- volume detail: --- /proc/cmdline root=/dev/md1 ro --- grub: kernel /vmlinuz-2.6.17-1-amd64-k8 root=/dev/md1 ro kernel /vmlinuz-2.6.17-1-amd64-k8 root=/dev/md1 ro single kernel /vmlinuz-2.6.16-2-amd64-k8 root=/dev/md1 ro kernel /vmlinuz-2.6.16-2-amd64-k8 root=/dev/md1 ro single kernel /vmlinuz-2.6.16-2-amd64-generic root=/dev/md1 ro kernel /vmlinuz-2.6.16-2-amd64-generic root=/dev/md1 ro single kernel /vmlinuz-2.6.16-1-amd64-k8 root=/dev/md1 ro kernel /vmlinuz-2.6.16-1-amd64-k8 root=/dev/md1 ro single kernel /vmlinuz-2.6.16-1-amd64-generic root=/dev/md1 ro kernel /vmlinuz-2.6.16-1-amd64-generic root=/dev/md1 ro single kernel /vmlinuz-2.6.15-1-amd64-k8 root=/dev/md1 ro kernel /vmlinuz-2.6.15-1-amd64-k8 root=/dev/md1 ro single kernel /vmlinuz-2.6.15-1-amd64-generic root=/dev/md1 ro kernel /vmlinuz-2.6.15-1-amd64-generic root=/dev/md1 ro single kernel /vmlinuz-2.6.12-1-amd64-generic root=/dev/md1 ro kernel /vmlinuz-2.6.12-1-amd64-generic root=/dev/md1 ro single kernel /boot/vmlinuz-2.6.10-9-amd64-k8 root=/dev/hda7 ro kernel /boot/vmlinuz-2.6.10-9-amd64-k8 root=/dev/hda7 ro single kernel /boot/vmlinuz-2.6.15-1-k7 root=/dev/hda1 ro kernel /boot/vmlinuz-2.6.15-1-k7 root=/dev/hda1 ro single kernel /boot/vmlinuz-2.6.14-2-k7 root=/dev/hda1 ro kernel /boot/vmlinuz-2.6.14-2-k7 root=/dev/hda1 ro single kernel /boot/vmlinuz-2.6.11-9-amd64-k8 root=/dev/hda1 ro kernel /boot/vmlinuz-2.6.11-9-amd64-k8 root=/dev/hda1 ro single kernel /boot/vmlinuz-2.6.11-1-k7 root=/dev/hda1 ro kernel /boot/vmlinuz-2.6.11-1-k7 root=/dev/hda1 ro single kernel /boot/vmlinuz-2.6.9-2-k7 root=/dev/hda1 ro kernel /boot/vmlinuz-2.6.9-2-k7 root=/dev/hda1 ro single -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-amd64-k8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages mdadm depends on: ii debconf [debconf-2.0] 1.5.4 Debian configuration management sy ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii lsb-base 3.1-15 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-3 lightweight exim MTA (v4) daemon -- debconf information: * mdadm/autostart: true mdadm/initrdstart: /dev/md1 mdadm/initrdstart_notinconf: false mdadm/initrdstart_msg_errexist: mdadm/initrdstart_msg_intro: mdadm/initrdstart_msg_errblock: * mdadm/warning: mdadm/start_daemon: true mdadm/mail_to: root mdadm/initrdstart_msg_errmd: mdadm/initrdstart_msg_errconf: mdadm/autocheck: true
--- End Message ---
--- Begin Message ---Source: mdadm Source-Version: 2.5.3.git200608202239-6 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.3.git200608202239-6_amd64.udeb to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-6_amd64.udeb mdadm_2.5.3.git200608202239-6.diff.gz to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-6.diff.gz mdadm_2.5.3.git200608202239-6.dsc to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-6.dsc mdadm_2.5.3.git200608202239-6_amd64.deb to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-6_amd64.deb 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: Thu, 21 Sep 2006 15:25:21 +0200 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source amd64 Version: 2.5.3.git200608202239-6 Distribution: unstable Urgency: high 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: 388355 Changes: mdadm (2.5.3.git200608202239-6) unstable; urgency=high . * Bumping urgency to high because previous version has been in unstable for three days and this one really only fixes a stupid segfault: * Reworked the parsing of /proc/partitions and spotted a mean segfault (closes: #388355). Files: 287559f4bdec4cf5f9c7b13e21766c02 760 admin optional mdadm_2.5.3.git200608202239-6.dsc a0bae5242e2fdc339e1ec2cf301a4b30 89878 admin optional mdadm_2.5.3.git200608202239-6.diff.gz 3b161283731dc45143ecc6ffc599af25 195896 admin optional mdadm_2.5.3.git200608202239-6_amd64.deb e1c951fbf4fc6ac5194e7e07aac23739 70898 debian-installer optional mdadm-udeb_2.5.3.git200608202239-6_amd64.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFEpaxIgvIgzMMSnURAmaNAKDYfU067wheQZF4cjLOifgwAMASlgCgsjj2 jsaeFCr7eoIsBVaPoa7X2gg= =mW8l -----END PGP SIGNATURE-----
--- End Message ---
