On 29/06/17 11:14, Gandalf Corvotempesta wrote: > 2017-06-29 12:10 GMT+02:00 Reindl Harald <h.reindl@xxxxxxxxxxxxx>: >> there is nothing like "unused part of the array" since the linux-raid-layer >> knows nothing about the filesystem on top and hence a raid-check (scrub) >> reads every block as said hardware controller > > Yes, this during a scrub. > Without a scrub, kernel know nothing about an unused part of the array. > > Let's assume a unreadable sector is found during a scrub. What > happens? mdadm kick-out the disk from the array? It tried to > reallocate the failed sector somewhere keeping the disk up and running > (and thus, resolving the URE that would prevent a successful resync?) As I said, read up on disk failure modes. If mdadm finds an unreadable sector, it does a full stripe read, recalculates the unreadable sector, and writes it back. If the read failed because the magnetism has decayed, this will reset it and everything will be hunky-dory again. If the read failed because the magnetic layer is failing, it will trigger a relocate (which SMART should pick up) and alarm bells should start ringing. It might be benign, the magnetic properties of the layer might be failing such that that bit can no longer record properly, or it could be that the layer itself is starting to fail, at which point you are heading for platter failure, a head crash, and serious pain. Cheers, Wol -- 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
