Your message dated Sun, 28 Oct 2012 18:47:28 +0000 with message-id <[email protected]> and subject line Bug#686703: fixed in mdadm 3.2.5-4+mdmon has caused the Debian Bug report #686703, regarding [Fwd: mdadm: --uuid never overrides --homehost] 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 [email protected] immediately.) -- 686703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686703 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mdadm Version: 3.1.4-1+8efb9d1+squeeze1 Severity: normal The man page says "Also, using --uuid= when creating a v0.90 array will silently override any --homehost= setting." This is not true: root@squeeze00:~# date; mdadm --create /dev/md1 --uuid=6f05ff4e:b4d49c1f:7fa21d88:ad0c50a9 --homehost=migrate08 --metadata=0.90 --leve\ l=mirror --raid-devices=2 /dev/sdb3 missing Tue Sep 4 12:33:37 PDT 2012 mdadm: /dev/sdb3 appears to be part of a raid array: level=raid1 devices=2 ctime=Fri Aug 31 20:59:50 2012 Continue creating array? y mdadm: array /dev/md1 started. root@squeeze00:~# mdadm --examine /dev/sdb3 /dev/sdb3: Magic : a92b4efc Version : 0.90.00 UUID : 6f05ff4e:b4d49c1f:1b351879:7d3a4743 I also tried with homehost after uuid and with no homehost at all. The uuid is always rewritten. This is a problem for me because I am attempting to reconstruct an array of virtual disks for a lenny VM that expects the uuid I specified. As an aside, I'm not sure why this system has a mdadm.conf (below). The base VM (before mount the 2 virtual disks to repair) uses no s/w raid. Note the 2 virtual disks support 2 different RAID devices, based on the 1st and 3rd partitions respectively. -- Package-specific info: --- mdadm.conf DEVICE partitions CREATE owner=root group=disk mode=0660 auto=yes HOMEHOST <system> MAILADDR root ARRAY /dev/md0 UUID=b0247721:1d41bea7:7fa21d88:ad0c50a9 --- /etc/default/mdadm INITRDSTART='none' AUTOSTART=false AUTOCHECK=true START_DAEMON=true DAEMON_OPTIONS="--syslog" VERBOSE=false --- /proc/mdstat: Personalities : [raid1] unused devices: <none> --- /proc/partitions: major minor #blocks name 8 0 10485760 sda 8 1 9984366 sda1 8 2 1 sda2 8 5 497983 sda5 8 32 8388608 sdc 8 33 96358 sdc1 8 34 104422 sdc2 8 35 8187795 sdc3 8 16 8388608 sdb 8 17 96358 sdb1 8 18 104422 sdb2 8 19 8187795 sdb3 --- LVM physical volumes: LVM does not seem to be used. --- mount output /dev/sda1 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) 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) --- initrd.img-2.6.32-5-amd64: 55146 blocks 79246b981b4d424653bcabc1192b7161 ./sbin/mdadm 078b1dc76a3a2d4500122570e20506d7 ./etc/mdadm/mdadm.conf f4fbd9099399ab08ba9b9f6c71d77595 ./scripts/local-top/mdadm 2613966c4ad244d2020546606edf881d ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/linear.ko ac72e0740fbbed1d4a7b771a0b98b2ac ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid0.ko 912cd85e91564b2da63cf5d2cd87ce59 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid6_pq.ko 0bdeea8ac1da08d22e9f341b57ed3240 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/md-mod.ko 1707ef1ad879edbd28669595280e1380 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-mod.ko 626ce1750d8050656dbac2ca18877747 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid456.ko 86a641df9b740ea7194c73ba0b5cf153 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid10.ko 1284687180c2447540b9e65acbf84bde ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid1.ko 9560815ed4d481c31ba7ee0d0f43dfd6 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/multipath.ko --- initrd's /conf/conf.d/md: MD_HOMEHOST='squeeze00' MD_DEVS=none MD_MODULES='' --- /proc/modules: raid1 18431 0 - Live 0xffffffffa0052000 md_mod 73920 1 raid1, Live 0xffffffffa02cf000 --- /var/log/syslog: --- volume detail: /dev/sda is not recognised by mdadm. /dev/sda1 is not recognised by mdadm. /dev/sda2 is not recognised by mdadm. /dev/sda5 is not recognised by mdadm. /dev/sdb is not recognised by mdadm. dev/sdb1: Magic : a92b4efc Version : 0.90.00 UUID : b0247721:1d41bea7:7fa21d88:ad0c50a9 Creation Time : Mon Jun 27 13:34:19 2011 Raid Level : raid1 Used Dev Size : 96256 (94.02 MiB 98.57 MB) Array Size : 96256 (94.02 MiB 98.57 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Update Time : Fri Aug 31 20:13:27 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 418bd296 - correct Events : 28 Number Major Minor RaidDevice State this 0 3 1 0 active sync 0 0 3 1 0 active sync 1 1 3 65 1 active sync -- /dev/sdb2 is not recognised by mdadm. /dev/sdb3: Magic : a92b4efc Version : 0.90.00 UUID : 6f05ff4e:b4d49c1f:1b351879:7d3a4743 Creation Time : Tue Sep 4 12:33:54 2012 Raid Level : raid1 Used Dev Size : 8187712 (7.81 GiB 8.38 GB) Array Size : 8187712 (7.81 GiB 8.38 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Update Time : Tue Sep 4 12:33:54 2012 State : active Active Devices : 1 Working Devices : 1 Failed Devices : 1 Spare Devices : 0 Checksum : 67ee952 - correct Events : 1 Number Major Minor RaidDevice State this 0 8 19 0 active sync /dev/sdb3 0 0 8 19 0 active sync /dev/sdb3 1 0 0 0 0 spare -- /dev/sdc is not recognised by mdadm. /dev/sdc1: Magic : a92b4efc Version : 0.90.00 UUID : b0247721:1d41bea7:7fa21d88:ad0c50a9 Creation Time : Mon Jun 27 13:34:19 2011 Raid Level : raid1 Used Dev Size : 96256 (94.02 MiB 98.57 MB) Array Size : 96256 (94.02 MiB 98.57 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Update Time : Fri Aug 31 20:13:27 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 418bd2d8 - correct Events : 28 Number Major Minor RaidDevice State this 1 3 65 1 active sync 0 0 3 1 0 active sync 1 1 3 65 1 active sync -- /dev/sdc2 is not recognised by mdadm. /dev/sdc3 is not recognised by mdadm. --- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=5214601b-a9c6-496a-95cf-99962f6bb215 ro clock=pit quiet --- grub2: set root='(hd0,msdos1)' set root='(hd0,msdos1)' set root='(hd0,msdos1)' set root='(hd0,msdos1)' linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=5214601b-a9c6-496a-95cf-99962f6bb215 ro clock=pit quiet set root='(hd0,msdos1)' linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=5214601b-a9c6-496a-95cf-99962f6bb215 ro single clock=pit --- udev: ii udev 164-3 /dev/ and hotplug management daemon 4a574fcd059040d33ea18a8aa605a184 /lib/udev/rules.d/64-md-raid.rules --- /dev: brw-rw---- 1 root disk 9, 1 Sep 4 12:35 /dev/md1 /dev/disk/by-id: total 0 lrwxrwxrwx 1 root root 9 Sep 3 21:13 ata-QEMU_HARDDISK_QM00001 -> ../../sda lrwxrwxrwx 1 root root 10 Sep 3 21:13 ata-QEMU_HARDDISK_QM00001-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 ata-QEMU_HARDDISK_QM00001-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 3 21:13 ata-QEMU_HARDDISK_QM00001-part5 -> ../../sda5 lrwxrwxrwx 1 root root 9 Sep 3 21:13 ata-QEMU_HARDDISK_QM00002 -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 3 21:13 ata-QEMU_HARDDISK_QM00002-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 ata-QEMU_HARDDISK_QM00002-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Sep 4 12:33 ata-QEMU_HARDDISK_QM00002-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 9 Sep 3 21:13 ata-QEMU_HARDDISK_QM00003 -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 3 21:13 ata-QEMU_HARDDISK_QM00003-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 ata-QEMU_HARDDISK_QM00003-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 3 21:13 ata-QEMU_HARDDISK_QM00003-part3 -> ../../sdc3 lrwxrwxrwx 1 root root 9 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00001 -> ../../sda lrwxrwxrwx 1 root root 10 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00001-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00001-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00001-part5 -> ../../sda5 lrwxrwxrwx 1 root root 9 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00002 -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00002-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00002-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Sep 4 12:33 scsi-SATA_QEMU_HARDDISK_QM00002-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 9 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00003 -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00003-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00003-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 3 21:13 scsi-SATA_QEMU_HARDDISK_QM00003-part3 -> ../../sdc3 /dev/disk/by-path: total 0 lrwxrwxrwx 1 root root 9 Sep 3 21:13 pci-0000:00:01.1-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Sep 3 21:13 pci-0000:00:01.1-scsi-0:0:0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 pci-0000:00:01.1-scsi-0:0:0:0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 3 21:13 pci-0000:00:01.1-scsi-0:0:0:0-part5 -> ../../sda5 lrwxrwxrwx 1 root root 9 Sep 3 21:13 pci-0000:00:01.1-scsi-0:0:1:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 3 21:13 pci-0000:00:01.1-scsi-0:0:1:0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 pci-0000:00:01.1-scsi-0:0:1:0-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Sep 4 12:33 pci-0000:00:01.1-scsi-0:0:1:0-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 9 Sep 3 21:13 pci-0000:00:01.1-scsi-1:0:0:0 -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 3 21:13 pci-0000:00:01.1-scsi-1:0:0:0-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 3 21:13 pci-0000:00:01.1-scsi-1:0:0:0-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 3 21:13 pci-0000:00:01.1-scsi-1:0:0:0-part3 -> ../../sdc3 /dev/disk/by-uuid: total 0 lrwxrwxrwx 1 root root 10 Sep 3 21:13 383bd487-edb6-46b8-9396-e76903bd47e6 -> ../../sda5 lrwxrwxrwx 1 root root 10 Sep 3 21:13 5214601b-a9c6-496a-95cf-99962f6bb215 -> ../../sda1 Auto-generated on Tue, 04 Sep 2012 13:07:35 -0700 by mdadm bugscript 3.1.4-1+8efb9d1+squeeze1 -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mdadm depends on: ii debconf 1.5.36.1 Debian configuration management sy ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii udev 164-3 /dev/ and hotplug management daemo Versions of packages mdadm recommends: ii exim4-daemon-light [mail 4.72-6+squeeze2 lightweight Exim MTA (v4) daemon ii module-init-tools 3.12-2 tools for managing Linux kernel mo mdadm suggests no packages. -- debconf information: mdadm/initrdstart_msg_errexist: mdadm/initrdstart_msg_intro: * mdadm/autostart: false mdadm/autocheck: true mdadm/initrdstart_msg_errblock: mdadm/mail_to: root mdadm/initrdstart_msg_errmd: * mdadm/initrdstart: none mdadm/initrdstart_msg_errconf: mdadm/initrdstart_notinconf: false mdadm/start_daemon: true
--- End Message ---
--- Begin Message ---Source: mdadm Source-Version: 3.2.5-4+mdmon 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. 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. Michael Tokarev <[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.8 Date: Sat, 20 Oct 2012 19:20:12 +0400 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source i386 Version: 3.2.5-4+mdmon Distribution: experimental Urgency: low Maintainer: Debian mdadm maintainers <[email protected]> Changed-By: Michael Tokarev <[email protected]> Description: mdadm - tool to administer Linux MD arrays (software RAID) mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb) Closes: 684708 686100 686703 691668 691670 691671 Changes: mdadm (3.2.5-4+mdmon) experimental; urgency=low . * fix `/etc/init.d/mdadm-raid status' inverse logic (Closes: #686100) * /etc/init.d/mdadm: change RUNDIR to /run instead of /var/run. Mdadm itself uses /run internally, we properly depend on initscripts version which creates /run, and the initscript itself is started after local_fs is processed, so this is merely a no-op, but let's do it for consistency. * Fix 'enough' function for RAID10, to prevent starting of a RAID10 array which does not have required minimum of component devices. (Closes: #691668). * fix segfaults in Detail() - mdadm --detail may segfault if a drive has been removed from the array (Closes: #691670) * super0: do not override uuid with homehost. The bug prevented re-creating an array with v0.90 superblock with the specified uuid when homehost is also specified. (Closes: #686703) * several fixes for mdmon argument processing (Closes: #691671): - allow --takeover when original was started with --offroot - fix arg parsing. - fix arg processing for -a * Changes based on a patch by Miquel van Smoorenburg (Closes: #684708): - install mdmon in udeb and initramfs, so imsm arrays can work. mdadm runs mdmon automatically when needed (currently for imsm arrays), and mdmon is required to make such arrays read-write (they're read-only by default) so merely presence of mdmon is enough to be able to use imsm arrays. - /etc/init.d/mdadm start: if a mdmon pidfile is found in /run/mdadm, restart mdmon (--takeover --all) - /etc/init.d/mdadm stop: link pidfiles of mdmon processes into /run/sendsigs.omit.d, and make sure that happens before sendsigs runs. - stop mdadm before sendsigs, so that the above code works - add script mdadm-waitidle that runs just before reboot/halt. For each array that is still running, it sets sync_action to idle, and uses mdadm --wait-clean to wait for all arrays to go idle (it has a short timeout). Checksums-Sha1: 027c92cc31020cab097bd84a5f156ffb4fa7508f 1515 mdadm_3.2.5-4+mdmon.dsc 10e9e0437d895b462c3ce793873bb32455393ba3 127483 mdadm_3.2.5-4+mdmon.debian.tar.bz2 b67034f130aa1007088ff78940dad09743024b37 565840 mdadm_3.2.5-4+mdmon_i386.deb 6874df31b5ed4ed67bd076509819076aaddd82c2 196250 mdadm-udeb_3.2.5-4+mdmon_i386.udeb Checksums-Sha256: 416ff0990bbe2f76f9eb6cc37cf0264aaf1771a82b4dc13a5592964ca5f92e73 1515 mdadm_3.2.5-4+mdmon.dsc 099b3f816db45c46ca0ae267c9b81549e1e1bc2023d7bff04279b867cfa3f7f9 127483 mdadm_3.2.5-4+mdmon.debian.tar.bz2 e075e22c5d232932f6811af27d4c2011cb29eca7bafd84ab7294df75cff9e8cf 565840 mdadm_3.2.5-4+mdmon_i386.deb 62742a3bb2d649d1de5bef817092632dbda35016d48a8afa8049239d121dfbcc 196250 mdadm-udeb_3.2.5-4+mdmon_i386.udeb Files: 91a614a28b83b127ba9e4539e21cf0d4 1515 admin optional mdadm_3.2.5-4+mdmon.dsc 4ba1ed5148c8edf9b2b62fe3dae534e4 127483 admin optional mdadm_3.2.5-4+mdmon.debian.tar.bz2 e0b1ec4744e126416b18efe2c4e10706 565840 admin optional mdadm_3.2.5-4+mdmon_i386.deb 56f51cd65bff7e3fcbfc6e30d6f14b0b 196250 debian-installer optional mdadm-udeb_3.2.5-4+mdmon_i386.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iJwEAQECAAYFAlCNe/4ACgkQUlPFrXTwyDhXEwP9FY68VaxgwftKj8pWUjUUZONm OpRmb95okOXfRt5KebXMV72lTUcE/WwHxlN5rZ6ZMFKRfvzobZ55DPDotCdr+262 Jg4666D81s377S+PZdYkccceXr9DPs4wW4hiXrBiKQ5lBkfowUTchzGKfYb470DO SeaTk7iyl1dBH7XZ3uM= =2IZ7 -----END PGP SIGNATURE-----
--- End Message ---
