On Fri, 21 Feb 2014, Samer, Michael (I/ET-83, extern) wrote:
In short: smartctl lists one pending sector. A dd of that disk provokes an i/o error
as expected. A raid 'sync_action=check' does not find a problem and does *not* trigger
an i/o error. Why?
Hello Eyal
Why not using ddrescue (or dd_rescue) instead (errorprone).
Probably because he wants to have the pending sector recalculated from
parity and written to with correct data.
Eyal, I had the same problem. I have reported this in the thread named
"Re: read errors not corrected when doing check on RAID6". The problem
wasn't found then and I have since worked around the problem by doing a
want-replace of the bad drive, so good you too reported this. Perhaps the
problem can be found and corrected now that I am not the only one
reporting this behavior.
--
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
