Chris Murphy wrote:
On Oct 28, 2012, at 2:49 PM, Roman Mamedov <rm@xxxxxxxxxx> wrote:
On Sun, 28 Oct 2012 14:34:49 -0600
Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
A drive that can sit there like a bump on the log for 2 minutes before it issues an actual read failure on sector(s) means mdadm is likewise waiting, and everything above it is waiting. That's a long hang. I'd not be surprised to see users go for hard reset with such a system hang after 45 seconds let alone 2 minutes.
Which is not different from what you would get (the same hang) in a non-RAID
environment on the same drive, so I don't see how this would be specifically a
RAID-related problem.
The difference is what you depend on running on that RAID. If it's someone playing movies or games, who cares. If you're a small business running a database or web site off this hardware and everything crawls for two minutes, or implodes because of that delay, now it's just bad design.
Exactly. The whole point of RAID is to keep things going despite a
drive failure, kind of problematic if the RAID hardware/software doesn't
get the message to drop a failing drive from the array.
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
--
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
