Yes containers will go offline, but this fix is for a recent change to the driver; if it was 6 months ago, it was a totally different problem. You probably can resolve your problems by making sure you have the latest Firmware. I don't believe there are any changes in the driver in the past 6 months that would have worked around any Firmware/Hardware/Compatibility issues.
Sadly, anything that goes wrong (including card, power supply, drives) can cause containers to go offline; it is a pretty generic symptom to a multitude of possible problems. Martin's initial problems were associated with using the WD JD drives, which are not compatible with RAID cards because their internal error recovery paths. Sincerely -- Mark Salyzyn -----Original Message----- From: Ryan Anderson [mailto:[EMAIL PROTECTED] Sent: Friday, July 08, 2005 1:42 PM To: Mark Haverkamp Cc: James Bottomley; Salyzyn, Mark; linux-scsi; Martin Drab Subject: Re: [PATCH] 2.6 aacraid: Fix for controller load based timeouts On Fri, 2005-07-08 at 10:36 -0700, Mark Haverkamp wrote: > Martin Drab found that he could get aacraid timeouts with high load on > his controller / disk drive combinations. After some experimentation > Mark Salyzyn has come up with a patch to reduce the default max_sectors > to something that will keep the controller from being overloaded and > will eliminate the timeout issues. Would hitting this timeout issue cause the container to go offline? If so, I think this may fix the issues I was having 6 months ago. (We ended up taking the aacraid controller out of our production environment, in frustration.) I'll try to get some testing time in on this next week, though, the problems I've run into were very hard to reproduce on demand. -- Ryan Anderson AutoWeb Communications, Inc. email: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
