Date: Wed, 12 May 2004 13:07:51 -0600 From: Scott Long <scottl@freebsd.org> To: Jens Schweikhardt <schweikh@schweikhardt.net> Cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance Message-ID: <40A27607.9040801@freebsd.org> In-Reply-To: <20040512190429.GA1315@schweikhardt.net> References: <FE045D4D9F7AED4CBFF1B3B813C85337051D8C0D@mail.sandvine.com> <40A26356.409@freebsd.org> <20040512183231.GB3137@schweikhardt.net> <20040512190429.GA1315@schweikhardt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jens Schweikhardt wrote: > On Wed, May 12, 2004 at 08:32:31PM +0200, Jens Schweikhardt wrote: > # On Wed, May 12, 2004 at 11:48:06AM -0600, Scott Long wrote: > # ... > # # I can't remember how the 2100 BIOS works, I'll have to take a look. > # # I thought that it was an attribute that was set when the array is > # # created. > # > # Yes, and once its set at array creation time it apparently can not be > # changed. I deleted the array and created it anew to disable read > # caching. This did not yield any perfomance gain by itself. After I > # changed the cables I now have 79MB/s (formerly only 29MB/s, a single > # disk has a sustained read speed of 71MB/s at the outer sectors). Next > # thing will be going back from forced U160 mode to U320. I'll report the > # results, so watch this space :-) > > Went back to U320 and enabled packetized--even with the Adaptec > cable that came with the controller no joy :-( > > At first, dd reported 83MB/s but after skipping the first 1G the > controller(?) made a high pitched beep, and this was in dmesg > > aac0: **Monitor** SCSI bus reset issued on channel 0 > aac0: **Monitor** <...repeats 2 more times> > aac0: **Monitor** Drive 0:14:0 online on container 0: > aac0: **Monitor** Drive 0:15:0 online on container 0: > aac0: **Monitor** SCSI bus reset issued on channel 0 > aac0: **Monitor** <...repeats 1 more times> > aac0: **Monitor** Drive 0:14:0 online on container 0: > aac0: **Monitor** Drive 0:15:0 online on container 0: > aac0: **Monitor** SCSI bus reset issued on channel 0 > aac0: **Monitor** Drive 0:15:0 returning error > aac0: **Monitor** ID(0:15:0) - Cmd[0x28] failed (retries exhausted) > aac0: **Monitor** Alarm Adapter Event -- turning Alarm On! > aac0: **Monitor** Container 0 returning error on drive 0:15:0 > aacd0: hard error cmd=read 2551359-2551486 > aacd0: hard error cmd=read 5013567-5013694 > ... > aacd0: hard error cmd=read 35094591-35094718 > aacd0: hard error cmd=read 35094719-35094846 > aacd0: hard error cmd=read 35094591-35094718 > aacd0: hard error cmd=read 35094719-35094846 > aacd0: hard error cmd=read 37601343-37601470 > aacd0: hard error cmd=read 37601471-37601598 > aacd0: hard error cmd=read 37601343-37601470 > aacd0: hard error cmd=read 37601471-37601598 > aacd0: hard error cmd=read 37601343-37601470 > aacd0: hard error cmd=read 37601471-37601598 > aac0: **Monitor** ID(0:15:0) - Cmd[0x2a] failed (retries exhausted) > aac0: **Monitor** Last Adapter Alarm Event -- Alarm turning off! > Error probing container 0 > aacd0: detached > aac0: **Monitor** Drive 0:14:0 online > > Hmm. Should I still go for another U320 cable? > > Regards, > > Jens Something on the SCSI bus is very unhappy. What drives are they? What firmware rev? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40A27607.9040801>