bogus debconf question "mdadm/boot_degraded"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: mdadm
Raid is designed to provide redundancy and failure tolerance. If a raid member fails and redundancy allows it, system operation is not compromised. Upon failure of components the raid array is properly degraded on the fly, and the system *will happily boot* anytime with that degraded array afterwards (without nonsense console droping).
The boot_degraded=NO option (or even default) is therefore an unreliable, disrupting, improper and misleading way to notify an admin about a failed raid member. (It is triggered only by raid members disconnected/
A better way to notify admins (about all kinds of raid events) is to make the mdadm package depend on a local mail transport agent or wall/notify-send mechanism and stop suppressing the debconf questions for the monitoring deamon.
Please
- Remove the bogus boot_degraded debconf option and question.
- Rely on (don't suppress but depend and inform about) proper means to notify admins about raid events.
/var/log/
Name: mdadm/boot_degraded
Defaulting to boot_degraded=false is bad replacement for buggy handling of raid degradation. (not a valid fix) https:/ /wiki.ubuntu. com/ReliableRai d