Date: Thu, 11 Jan 2007 10:09:26 -0800 From: Cstdenis <cstdenis@ctgameinfo.com> To: Scott Long <scottl@samsco.org> Cc: freebsd-scsi@freebsd.org Subject: Re: Bug in aac? Message-ID: <45A67D56.1080706@ctgameinfo.com> In-Reply-To: <45A66576.9010106@samsco.org> References: <45A4E3AD.1040600@ctgameinfo.com> <45A66576.9010106@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes the system does recover. I have not been actively using the system
when this happens so I'm not sure how long, but it looks like a few to
several minutes.
Its a dedicated server at a hosting company -- I don't have physical
access to the hardware so I don't know the exact details. The info I
gave was a combination of dmesg and what I ordered.
Here is what the web control panel says I have
Motherboard SuperMicro PDSMI+ Intel Pentium DualCore SingleProc
Sata [1Proc]
Processor Intel Xeon 3060-Dual Core [2.4GHz]
Drive Controller Adaptec 4800SAS SA-SCSI RAID-1 Controller
Available upgrades
Hard Drive 1 Fujitsu MAX3073 SAS 3073 [73GB] Available upgrades
Hard Drive 2 Fujitsu MAX3073 SAS 3073 [73GB] Available upgrades
I will try requesting a firmware upgrade. If that doesn't work is there
more information I can provide to help get the bug fixed? I tried
compiling AAC_DEBUG=3 into the kernel but it made the system unusable
with the constant flow of debug data. I worry that AAC_DEBUG=1 will also
be too much for the system to be usable, but I'm not sure.
Scott Long wrote:
> Cstdenis wrote:
>
>> I am running 6.1-p11 with a Adaptec SAS RAID 4800SAS running a mirror of
>> 2 15k rpm SCSI drives.
>>
>> Under heavy IO load (Its a database server) I get the following
>> accompanied by serious system lag:
>>
>>
>
> The system recovers after this? Strange. What the messages mean is
> that I/O has been sent to the controller, and the controller has not
> responded in a reasonable period of time. Usually this is a sign of
> the controller has died and will not recover. So if it is recovering
> then either there is a firmware bug that is making the controller pause
> for a long period of time, or there is some sort of yet-undiscovered
> driver bug. Of course you should make sure that you're running the
> latest firmware from Adaptec. These cards are new and SAS in general
> is relatively new, so bugs are not unlikely. One question, though, how
> are you running SCSI drives on a SAS controller? Are you going through
> some sort of converter?
>
> Scott
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45A67D56.1080706>