{upstream} inconsistency with the --no-degraded option
Bug #244810 reported by
ceg
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mdadm |
Confirmed
|
Undecided
|
Unassigned | ||
| mdadm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
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:/
| summary: |
- inconsistency with the --no-degraded option + {upstream} inconsistency with the --no-degraded option |
| Changed in mdadm (Ubuntu): | |
| status: | New → Invalid |
| Changed in mdadm (Ubuntu): | |
| status: | Invalid → New |
Revision history for this message
| Thomas Hotz (thotz-deactivatedaccount) wrote | #4 |
| Changed in mdadm (Ubuntu): | |
| status: | New → Confirmed |
| Changed in mdadm: | |
| status: | New → Confirmed |
To post a comment you must log in.
> clearer when staring degraded raids stays the resposibility of startup scripts.
Or the user manually starting an array. (possibly by right clicking)
Then, when two array disks are pluged in and it doesn't come up it is always clear they the array is not complete.