From: Douglas Gilbert <dougg@torque.net>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org,
thlin@linux.vnet.ibm.com
Subject: Re: [PATCH 1/1] scsi: Add EH Start Unit retry
Date: Thu, 29 Mar 2007 18:02:07 -0400 [thread overview]
Message-ID: <460C375F.1000000@torque.net> (raw)
In-Reply-To: <11751999513070-patch-mail.ibm.com>
Brian King wrote:
> Currently, the scsi error handler will issue a START_UNIT
> command if the drive indicates it needs its motor started
> and the allow_restart flag is set in the scsi_device. If,
> after the scsi error handler invokes a host adapter reset
> due to error recovery, a device is in a unit attention
> state AND also needs a START_UNIT, that device will be placed
> offline. The disk array devices on an ipr RAID adapter
> will do exactly this when in a dual initiator configuration.
> This patch adds a single retry to the EH initiated
> START_UNIT.
I have no objection to this patch. Just seems a pity
that SCSI devices go to the trouble of sending unit
attentions while OSes just throw them away.
Perhaps the scsi_device sysfs directory could have entries
like:
last_ua_asc
last_ua_ascq
last_ua_timestamp
where code could place the asc/ascq codes and a timestamp
then continue doing a retry.
Could we get a log entry, hotplug event?
Logical units may queue unit attentions (sam4r10.pdf
section 5.8.7) so it is possible that one retry may
not be enough. With my suggestion above, only the last
one would persist for a reasonable time.
Doug Gilbert
next parent reply other threads:[~2007-03-29 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11751999513070-patch-mail.ibm.com>
2007-03-29 22:02 ` Douglas Gilbert [this message]
2007-04-02 18:57 ` [PATCH 1/1] scsi: Add EH Start Unit retry Brian King
2007-04-03 3:09 ` James Bottomley
2007-04-03 13:20 ` Brian King
2007-04-01 16:36 ` James Bottomley
2007-04-02 13:38 ` Brian King
2007-03-29 20:25 Brian King
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=460C375F.1000000@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@steeleye.com \
--cc=brking@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=thlin@linux.vnet.ibm.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 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.