On Sun, 12 Jan 2014, Peter Grandi wrote:
[ ... ]
So here now in the replace function, md decided to correct the
read errors on /dev/sds. Now the pending sectors are down to 7
on /dev/sds. There were some more errors which were also
corrected, and now the pending count is down to 5. Recovery is
still ongoing. [ ... ] I expected it to correct the read
errors on the drive then, but it seems it didn't. [ ... ]
That seems to me a big misunderstanding (or delusion).
Which of it? Pending sectors (which from my understanding is the same as
UNC when reading) on a component drive in RAID6 wouldn't be re-calculated
from parity and written to fix the problem?
But from my other email, it seems "pending sector" doesn't mean it always
gives read errors, but just sometimes. The read errors I got from the
check doesn't match up with the read errors I got when I did replace, and
it also seems the read errors didn't always occur.
--
Mikael Abrahamsson email: swmike@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
