From: Grant Grundler <grundler@dsl2.external.hp.com>
To: "James Braid" <james.braid@peace.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Dodgy SCSI in L2000
Date: Tue, 07 May 2002 00:21:18 -0600 [thread overview]
Message-ID: <20020507062119.F0744482A@dsl2.external.hp.com> (raw)
In-Reply-To: Message from "James Braid" <james.braid@peace.com> of "Tue, 07 May 2002 17:28:13 +1200." <006001c1f587$fbc0c830$5e01000a@bongo>
"James Braid" wrote:
> Okay, I have got my RAID array working now :-)
>
> BUT...
Which kernel version?
> In the window I have open to the GSP (in a console session) on the
> L2000, I see this:
>
> sym4:0:0: ABORT operation started.
> sym4:0:0: ABORT operation timed-out.
> sym4:0:0: ABORT operation started.
> sym4:0:0: ABORT operation timed-out.
...
This suggests something is wrong with that device.
Are all RAID0 disks internal? Or connected to external box?
I see further down they seem to be working fine individually.
...
> It also does the same thing using the sym5c8xx version 1 driver as well
> as the version 2 driver (the above errors are from the version 2
> driver).
Can you post lspci -v output from you L2000?
I just want to verify the built-in SCSI chips are the
same as on my A500: sym53c896.
...
> One thing I have noticed with mke2fs is that the indode table numbers
> tick away pretty fast until it gets to 205, then it slows down big time,
> and then it speeds up again until it gets to ~340, at which point the
> scsi ABORT errors will sometimes start happening.
I noticed the slow down/speed up when I built the RAID0 on the B180 as well.
No idea what causes it though.
> I have tested all the disks individually (making filesystems, running
> dbench), and the filesystems get made fine, and dbench works okay up to
> about 100 odd clients.
Can you try running two different dbench instances at the some time on
two different disks?
I had to steal the serial port from my A500 or I could do more
to at least reproduce this.
> I have *no* idea what is causing any of this....anyone else have any
> hints/info/fixes for this problem? (Sorry for the long email, but I
> figured it would be best to paste the full errors)
>
> I can provide clarification or more details if needed.
>
> Cheers, James
>
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2002-05-07 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 5:28 [parisc-linux] Dodgy SCSI in L2000 James Braid
2002-05-07 6:21 ` Grant Grundler [this message]
2002-05-07 7:00 ` James Braid
2002-05-07 23:50 ` Grant Grundler
2002-05-08 1:57 ` James Braid
2002-05-08 5:10 ` James Braid
2002-05-08 16:08 ` Grant Grundler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020507062119.F0744482A@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=james.braid@peace.com \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox