On Wed, 10 Jul 2013, Priya Kamala wrote:
If a single disk develops bad sector(s) that affects only a single
stripe within a given RAID-5 configuration and these bad sectors are
discovered when running a "check/resync" (echo check >
/sys/block/mdX/md/sync_action), does this result in the entire disk
being removed from the RAID? In other words, is access to the other good
stripes on the drive disabled as well? If so, why is it done this way?
In case the kernel version makes a difference to the behaviour, I'm
working with 2.6.21.1.
If drive is kicked, it could be because it's a consumer drive which
doesn't support TLER/ERC.
Do:
for x in /sys/block/sd[a-z] ; do echo 180 > $x/device/timeout ; done
This should mean the disk isn't kicked from the array unless it's really
broken.
But as was mentioned in another mail in your thread, you really should
upgrade your kernel. It's really old.
--
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
