From: Mike Anderson <andmike@us.ibm.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/4] 2.4 SCSI error handling fixes
Date: Thu, 12 Sep 2002 12:31:14 -0700 [thread overview]
Message-ID: <20020912193114.GB1170@beaverton.ibm.com> (raw)
In-Reply-To: <20020912192028.E4739@flint.arm.linux.org.uk>
Russell King [rmk@arm.linux.org.uk] wrote:
> On Thu, Sep 12, 2002 at 02:18:06PM -0400, Doug Ledford wrote:
> > On Thu, Sep 12, 2002 at 07:13:54PM +0100, Russell King wrote:
> > > - scsi_setup_cmd_retry(SCpnt);
> > > - scsi_send_eh_cmnd(SCpnt, SCpnt->timeout_per_command);
> > > + do {
> > > + scsi_setup_cmd_retry(SCpnt);
> > > + scsi_send_eh_cmnd(SCpnt, SCpnt->timeout_per_command);
> > > + } while (SCpnt->eh_state == NEEDS_RETRY);
> >
> > > + * If the SCSI device responded with "logical unit
> > > + * is in process of becoming ready", we need to
> > > + * retry this command.
> > > + */
> > > + } while (SCpnt->eh_state == NEEDS_RETRY);
> >
> > > + /*
> > > + * If the SCSI device responded with "logical unit
> > > + * is in process of becoming ready", we need to
> > > + * retry this command.
> > > + */
> > > + } while (SCpnt->eh_state == NEEDS_RETRY);
> >
> > > default:
> > > - SCpnt->eh_state = FAILED;
> > > + ret = FAILED;
> > > + /*FALLTHROUGH*/
> > > + case FAILED:
> > > + case NEEDS_RETRY:
> > > + case SUCCESS:
> > > + SCpnt->eh_state = ret;
> > > break;
> > > }
> > > } else {
> >
> > I don't see any bounding here. You *have* to bound this. It is not that
> > uncommon for a device to report "logical unit is in the process of
> > becoming ready" forever on certain types of hardware failures. Without
> > bounding, we won't ever give up on it.
>
> Shrug. I've not changed the behaviour here. I've just fixed the ONE
> problem where we reissue the command back to the HBA driver with stale
> state information. I never claimed that it fixed ALL bugs.
>
> I'm afraid that I'm going to have to leave the other bugs are for
> someone else to address; I've already spent too long on this issue.
>
In 2.5 we are carrying a change in scsi_eh_completed_normally (I believe
this came from Andries.Brouwer@cwi.nl as I cannot find another
reference to it) that limits the number of retries.
Though this is modifying the original cmds retry count which I do not
believe it is a good thing at least it stops the loop. I know retries
are going to change, but until then I made a similar adjustment to my
scsi_error cleanup and will repost shortly.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2002-09-12 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 18:13 [PATCH 2/4] 2.4 SCSI error handling fixes Russell King
2002-09-12 18:18 ` Doug Ledford
2002-09-12 18:20 ` Russell King
2002-09-12 19:31 ` Mike Anderson [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=20020912193114.GB1170@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.