On Wed, 10 Oct 2012, Stan Hoeppner wrote:
Precisely what it says. It doesn't tell you WHY it was blocked, as it can't know. The fact that your md array was in recovery and having problems with one of the member drives is a good reason for xfssyncd to block.
Doesn't he still have 3 good drives? So since sdb was failed, there would be no reason for sdb to cause blocking or writes to the (now degraded) raid5? OP said he saw write IO errors to the array (?), which I thought was strange.
-- 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
