[Bug 244810] Re: {upstream} inconsistency with the --no-degraded option
Thomas Hotz
244810 at bugs.launchpad.net
Sun Apr 28 08:40:39 UTC 2013
Marking to confirmed, hopefully a developer can fix this soon. Thank you
very much for reporting this bug!
** Changed in: mdadm (Ubuntu)
Status: New => Confirmed
** Changed in: mdadm
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/244810
Title:
{upstream} inconsistency with the --no-degraded option
Status in mdadm - Tool for managing linux software RAID arrays.:
Confirmed
Status in “mdadm” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: mdadm
There is inconsistency in the --no-degraded and --incremental option.
They will start degraded arrays, if they have been --run degraded
before.
Its clearer to report problems and and do interventions when staring degraded raids stays the resposibility of startup scripts.
(https://wiki.ubuntu.com/BootDegradedRaid)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mdadm/+bug/244810/+subscriptions
More information about the foundations-bugs
mailing list