From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: pbog@us.ibm.com
Cc: linux-scsi@vger.kernel.org, "Darrick J. Wong" <djwong@us.ibm.com>,
"Wu, Gilbert" <Gilbert_Wu@adaptec.com>,
Alexis Bruemmer <alexisb@us.ibm.com>,
tom_white@adaptec.com
Subject: Re: Bug in aic94xx driver in 2.6.25-rc3
Date: Wed, 27 Feb 2008 15:37:28 -0800 [thread overview]
Message-ID: <1204155448.3470.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1204151946.7281.23.camel@gnattop>
On Wed, 2008-02-27 at 14:39 -0800, peter wrote:
> My original post was user error and not acutally a bug. I didn't
> realize that there was another patch I need to apply to rc3 to get the
> latest scsi drivers and error handler code. Alexis clued me in. Now
> the error handler appears to be working properly. I included a sample
> at the bottom of this email.
>
> I am still seeing the disk go offline if I run i/o performance tests on
> sas disks connected to the aic94xx (sequencer version 32). It doesn't
> happen right away. The i/o tests will run for several hours before it
> fails. Eventually you see the filesystem abort and then be remounted as
> read only.
Yes, I've seen this one too. in my case it's caused by error handling
tripping a flutter on the disk phy, so the HBA actually sees an
unplug/replug event, but that causes the disk to go offline (even though
it actually reappears almost immediately). I have that on my list of
things to fix ... probably by stealing the devloss tmo from fc.
James
prev parent reply other threads:[~2008-02-27 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1203987834.6909.17.camel@gnattop>
[not found] ` <1203992592.26232.79.camel@alexis>
2008-02-27 22:39 ` Bug in aic94xx driver in 2.6.25-rc3 peter
2008-02-27 23:37 ` James Bottomley [this message]
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=1204155448.3470.40.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Gilbert_Wu@adaptec.com \
--cc=alexisb@us.ibm.com \
--cc=djwong@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=pbog@us.ibm.com \
--cc=tom_white@adaptec.com \
/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