https://bugzilla.novell.com/show_bug.cgi?id=640358 https://bugzilla.novell.com/show_bug.cgi?id=640358#c0 Summary: mdadm ignores the --no-degraded option and dangerously starts degraded arrays Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: windows2linux@zoho.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-30.1 Firefox/3.6.10 With openSUSE 11.3 and mdadm 3.03, the --no-degraded option is ignored, and mdadm will assemble and START a degraded array which is dangerous, and forces the user to rebuild the missing device when it is reconnected. This happens if done manually with mdadm, or even upon booting up with /etc/init.d/boot.md Degraded arrays should not be started unless explicitly using the --run option. Booting the system without the third disk present (perhaps after opening the case to adjust something) or mistyping a LUKS passphrase a few times, mdadm will START the degraded array without all disks present. Now it must rebuild the array after re-adding the missing disk again. It's a needless use of time and risk. Reproducible: Always Steps to Reproduce: With only 2 of 3 drives present in a raid5 array: 1. mdadm --assemble --no-degraded /dev/md0 Actual Results: The /dev/md0 raid5 array is started as a degraded, even when explicitly using --no-degraded. This means that the third device must needlessly be rebuilt all over again. Expected Results: mdadm should not start the degraded array if a device is missing. Only explicitly using --run should do so. mdadm-3.0.3-9.1.x86_64 kernel-desktop-2.6.34.7-0.2.2.x86_64 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.