]> git.baikalelectronics.ru Git - kernel.git/commit
md/raid1: fix test for 'was read error from last working device'.
authorNeilBrown <neilb@suse.com>
Thu, 23 Jul 2015 23:22:16 +0000 (09:22 +1000)
committerNeilBrown <neilb@suse.com>
Fri, 24 Jul 2015 03:37:21 +0000 (13:37 +1000)
commit5353b53c808ab2bac64f258e3a38e464c0759604
tree246eafb8c7a8cf3bea39234e56cca7a5cfe09d21
parent6d052730ca53468545d56b38a9ec038dfc3a5f15
md/raid1: fix test for 'was read error from last working device'.

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: 01c5c367b9f9 ("md/raid1: clean up read_balance.")
Cc: stable@vger.kernel.org (v3.0+)
Signed-off-by: NeilBrown <neilb@suse.com>
drivers/md/raid1.c