Package: mdadm Version: 1.8.1-1 Severity: important
1.8.1 has a severe bug making all newly created RAID arrays get assigned the same exact UUID, regardless og time or even what machine it runs on. The UUID in question is "6b8b4567:327b23c6:643c9869:66334873", do a google search on it, not very unique eh? :) This breaks stuff like array discovery severely if more than one array is present, and may make moving arrays around between machines that used 1.8.1 to create arrays a real PITA. I just had LVM corrupt a array from this. I'd vote for getting 1.8.0 into sarge before this has time to manifest itself permanently on other peoples systems. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (1000, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-s6-up Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages mdadm depends on: ii debconf 1.4.30.11 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii makedev 2.3.1-75 Creates device files in /dev -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
