Your message dated Sat, 05 May 2007 19:47:05 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#415336: fixed in mdadm 2.6.1-1 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.6-9 Severity: wishlist Hello, I wish there would be a special option (or a separate script) that simply does assemble all available devices. Similar to what mdrun did some years ago. Why? Because I need to use it on Knoppix sometimes. The current method means many command calls, one to scan, editor to enable the init script action, calling init script again. I wish to simply run: mdadm-auto-assemble and be done with it, having everything assembled without additional configuration. NOTE: The order does not matter. It is only for convinience. Eduard. -- Package-specific info: --- mount output /dev/md1 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/sda5 on /mnt/d type vfat (rw,noexec,nosuid,nodev,showexec,umask=000,codepage=850,utf8=yes) /dev/sda7 on /mnt/data type ext3 (rw,errors=remount-ro) /dev/sda1 on /mnt/c type vfat (rw,noexec,nosuid,nodev,utf8,umask=000) automount(pid5263) on /misc type autofs (rw,fd=4,pgrp=5263,minproto=2,maxproto=4) none on /sys/fs/fuse/connections type fusectl (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) /dev/md0 on /boot type ext3 (rw,errors=remount-ro) --- mdadm.conf DEVICE partitions MAILADDR root ARRAY /dev/md0 level=raid1 num-devices=3 UUID=93bb93e8:f30d04cb:ac726c50:58520726 ARRAY /dev/md1 level=raid5 num-devices=3 UUID=566bb332:14ee5c2f:d88d0f15:f12bbfb1 --- /proc/mdstat: Personalities : [raid1] [raid6] [raid5] [raid4] md1 : active raid5 sdb7[0] sdc7[1] 58588800 blocks level 5, 64k chunk, algorithm 2 [3/2] [UU_] md0 : active raid1 sdb6[0] sdc6[1] 128384 blocks [3/2] [UU_] unused devices: <none> --- /proc/partitions: major minor #blocks name 8 0 312571224 sda 8 1 40131 sda1 8 2 1 sda2 8 5 97635006 sda5 8 6 39070048 sda6 8 7 175823361 sda7 8 16 312571224 sdb 8 17 32098 sdb1 8 18 1 sdb2 8 21 29294496 sdb5 8 22 128488 sdb6 8 23 29294496 sdb7 8 24 146480638 sdb8 8 25 102542863 sdb9 8 32 312571224 sdc 8 33 32098 sdc1 8 34 1 sdc2 8 37 29294496 sdc5 8 38 128488 sdc6 8 39 29294496 sdc7 8 40 146480638 sdc8 8 41 102542863 sdc9 9 0 128384 md0 9 1 58588800 md1 --- initrd.img-2.6.20: 15828 blocks scripts/local-top/mdadm sbin/mdadm lib/modules/2.6.20/kernel/drivers/md/dm-mod.ko lib/modules/2.6.20/kernel/drivers/md/raid1.ko lib/modules/2.6.20/kernel/drivers/md/raid10.ko lib/modules/2.6.20/kernel/drivers/md/xor.ko lib/modules/2.6.20/kernel/drivers/md/md-mod.ko lib/modules/2.6.20/kernel/drivers/md/raid0.ko lib/modules/2.6.20/kernel/drivers/md/raid456.ko lib/modules/2.6.20/kernel/drivers/md/dm-crypt.ko etc/mdadm etc/mdadm/mdadm.conf --- /proc/modules: dm_crypt 12240 0 - Live 0xffffffff88234000 dm_snapshot 15368 0 - Live 0xffffffff8822f000 dm_mirror 18368 0 - Live 0xffffffff88229000 dm_mod 54256 3 dm_crypt,dm_snapshot,dm_mirror, Live 0xffffffff8821a000 raid456 117280 1 - Live 0xffffffff8807d000 xor 5904 1 raid456, Live 0xffffffff8807a000 raid1 20224 1 - Live 0xffffffff88074000 md_mod 70748 4 raid456,raid1, Live 0xffffffff88061000 --- volume detail: --- /proc/cmdline BOOT_IMAGE=Lin-mit-initrd ro root=900 root=/dev/md1 --- grub: kernel /vmlinuz root=/dev/md1 ro kernel /vmlinuz root=/dev/sda6 ro kernel /vmlinuz root=/dev/sda6 ro single kernel /vmlinuz-2.6.20 root=/dev/sda6 ro kernel /vmlinuz-2.6.20 root=/dev/sda6 ro single kernel /vmlinuz-2.6.20-rc5 root=/dev/sda6 ro kernel /vmlinuz-2.6.20-rc5 root=/dev/sda6 ro single --- lilo: lilo.conf file not readable. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages mdadm depends on: ii debconf [debconf-2.0] 1.5.12 Debian configuration management sy ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii lsb-base 3.1-23 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/autostart: false * mdadm/initrdstart: all mdadm/initrdstart_notinconf: false mdadm/initrdstart_msg_errexist: mdadm/initrdstart_msg_intro: mdadm/initrdstart_msg_errblock: * mdadm/warning: * mdadm/start_daemon: false mdadm/mail_to: root mdadm/initrdstart_msg_errmd: mdadm/initrdstart_msg_errconf: * mdadm/autocheck: true
--- End Message ---
--- Begin Message ---Source: mdadm Source-Version: 2.6.1-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.1-1_i386.udeb to pool/main/m/mdadm/mdadm-udeb_2.6.1-1_i386.udeb mdadm_2.6.1-1.diff.gz to pool/main/m/mdadm/mdadm_2.6.1-1.diff.gz mdadm_2.6.1-1.dsc to pool/main/m/mdadm/mdadm_2.6.1-1.dsc mdadm_2.6.1-1_i386.deb to pool/main/m/mdadm/mdadm_2.6.1-1_i386.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: Sat, 05 May 2007 16:12:29 +0200 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source i386 Version: 2.6.1-1 Distribution: unstable Urgency: low 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: 415336 415441 Changes: mdadm (2.6.1-1) unstable; urgency=low . * Release to unstable. * Start arrays read-only in initramfs to prevent syncing and hence enable resuming/freezing. The arrays will automatically sync as soon something writes to it; thanks to Tim Dijkstra, Neil Brown, and Luis Rodrigo Gallardo Cruz (closes: #415441). * mkconf now tries to preserve existing values for DEVICE, CREATE and HOMEHOST (in addition to MAILADDR, which it preserved previously already). PROGRAM is preserved but only added to mdadm.conf if it occured in the previously existing configuration file. * startall is now mdadm-startall and lives in /sbin, thanks to Eduard Bloch. It now can handle existing mdadm.conf files much more gracefully, mostly thanks to the above mkconf enhancements (closes: #415336). Files: 69967f70cb344a399368cf2b319e7cb9 781 admin optional mdadm_2.6.1-1.dsc 25397af5b56e56a3fddb660403be1588 130957 admin optional mdadm_2.6.1-1.diff.gz e1413d7d598e915ea3565e6578bcf438 240264 admin optional mdadm_2.6.1-1_i386.deb 8b56758126abac2815f4808145eeabff 75772 debian-installer optional mdadm-udeb_2.6.1-1_i386.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGPNydIgvIgzMMSnURAtZ9AKDl0d/wfrKUbaYmDBNun0QGemsRRACfTwMW kK4jdshaZRx/uthknSR05Zc= =rZiJ -----END PGP SIGNATURE-----
--- End Message ---
