On 1 Oct 2012, Pierre Beck stated: > On 23.09.2012 17:42, Nix wrote: >> On 19 Sep 2012, Chris Murphy outgrape: >> >>> On Sep 19, 2012, at 12:52 PM, Nix wrote: >>> >>>> So I have this x86-64 server running Linux 3.5.1 with a SATA-on-PCIe >>>> Areca 1210 hardware RAID-5 controller >>> Did you find this? Same controller family. Weird that this just shows >>> up now, but perhaps instead of it being "bad hardware" out the gate, >>> something's happened to it and now it's failing as you suspect. >> Hm, it's possible I suppose. Just as possible that a disk is dying. >> >> >> It looks to have been a one-off transient -- no recurrence yet, touch >> wood :) >> > Check the SMART values of the disks if possible. Watch for command > timeouts and the usual bad sector stuff. I've had similar issues with > Adaptec controllers. Bad disks seem to cause havoc. The outstanding > operation isn't answered within [SCSI Timeout, default 30, > /sys/block/sdX/device/timeout] seconds, so Linux performs a loop > reset, eventually resetting the controller. That means between 60 and > 120 seconds of zero I/O operation, varying between controllers and > disk array sizes. It's particularly annoying when in RAID and the disk > could've simply been kicked within few seconds. Something that needs > improvement IMHO. The problem has not recurred in more than three weeks. SMART says no problems... so I guess the controller dropped off the bus for some reason. Probably some sort of subtle firmware bug or something. (There are hints in the driver that such bugs exist, hence the enormous amount of code the driver devotes to resetting the thing when it goes silent.) -- NULL && (void) -- 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
