Package: raidtools2 Version: 1.00.4 Severity: grave Justification: breaks reboot for sites with multiple RAID arrays Tags: sarge
Greetings, The transition from raidtools2 to mdadm breaks all installations with more than one RAID array because /etc/raidtab is ignored during autodetection. I discovered this surprise on reboot, when the order of my site's RAID arrays was switched, and disabling autodetection (which intuition said would use /etc/raidtab) of course resulted in none of them being mounted. So I tried to remove mdadm but of course raidtools2 depends on it (since raidtools2 is empty). (Actually, a grad student noticed the problem when booting our server after a scheduled power outage while I was away. He of course had no idea of what was happening, so our site was down for the better part of a day as a result! The only clue I had was that mdadm had been installed as a dependency of raidtools2...) That the transitional raidtools2 package entered sarge just days before the release (and that sarge had zero testing cycles, unlike potato or woody) means that there was just about zero testing for it, and it is too late for those admins who like me have since rebooted had the same problem. But for those who have not needed to reboot, please upload a fix (translate raidtab to something mdadm understands?) or a *prominent* debconf warning (maybe even a warning in the raidtools2 description) to testing-proposed-updates. If the right place for this is mdadm then please reassign it. I would be happy to produce a candidate patch. Thanks, -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Welcome to the best software in the world today cafe! http://www.take6.com/albums/greatesthits.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
