diff options
| author | NeilBrown <[email protected]> | 2012-09-19 12:52:30 +1000 |
|---|---|---|
| committer | NeilBrown <[email protected]> | 2012-09-19 12:52:30 +1000 |
| commit | e5c86471f933608db5d43679f84cb4346c32033e (patch) | |
| tree | e596b35a134b9cc4e308f90090ecf9998a5b58a4 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | a852d7b8a0cf29499905c9243fa6d3fb93898b82 (diff) | |
md/raid5: fix calculate of 'degraded' when a replacement becomes active.
When a replacement device becomes active, we mark the device that it
replaces as 'faulty' so that it can subsequently get removed.
However 'calc_degraded' only pays attention to the primary device, not
the replacement, so the array appears to become degraded, which is
wrong.
So teach 'calc_degraded' to consider any replacement if a primary
device is faulty.
This is suitable for -stable as an incorrect 'degraded' value can
confuse md and could lead to data corruption.
This is only relevant for 3.3 and later.
Cc: [email protected]
Reported-by: Robin Hill <[email protected]>
Reported-by: John Drescher <[email protected]>
Signed-off-by: NeilBrown <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions