diff options
| author | NeilBrown <neilb@suse.com> | 2015-07-24 09:22:16 +1000 |
|---|---|---|
| committer | Sasha Levin <sasha.levin@oracle.com> | 2015-08-27 13:25:44 -0400 |
| commit | ed220ba145d8f966a235d04f3cda64d9c2976475 (patch) | |
| tree | e0b3cdbe747c7d5e04f333f887e06ca7a68df0c0 /arch/tile/Kconfig | |
| parent | b98982262ccdb0d3f24f1c4858553c3c1c3b84d5 (diff) | |
md/raid1: fix test for 'was read error from last working device'.
[ Upstream commit 34cab6f42003cb06f48f86a86652984dec338ae9 ]
When we get a read error from the last working device, we don't
try to repair it, and don't fail the device. We simple report a
read error to the caller.
However the current test for 'is this the last working device' is
wrong.
When there is only one fully working device, it assumes that a
non-faulty device is that device. However a spare which is rebuilding
would be non-faulty but so not the only working device.
So change the test from "!Faulty" to "In_sync". If ->degraded says
there is only one fully working device and this device is in_sync,
this must be the one.
This bug has existed since we allowed read_balance to read from
a recovering spare in v3.0
Reported-and-tested-by: Alexander Lyakas <alex.bolshoy@gmail.com>
Fixes: 76073054c95b ("md/raid1: clean up read_balance.")
Cc: stable@vger.kernel.org (v3.0+)
Signed-off-by: NeilBrown <neilb@suse.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Diffstat (limited to 'arch/tile/Kconfig')
0 files changed, 0 insertions, 0 deletions