From: Hannes Reinecke <hare@suse.de>
To: SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
Martin George <Martin.George@netapp.com>
Subject: Flood of SCSI retries when a port is in transitioning
Date: Thu, 25 Aug 2011 15:36:07 +0200 [thread overview]
Message-ID: <4E564FC7.10507@suse.de> (raw)
Hi all,
our friends from NetApp discovered a SCSI retry flood when a remote
port is in ALUA 'transitioning' state.
The device will then return
Not ready/LUN Not Accessible - ALUA state transition
which will be evaluated in scsi_dh_alua.c:alua_check_sense()
as ADD_TO_MLQUEUE.
This will cause an immediate retry of the command and hence the
target will be pounded with a flood of retries.
I have now tried to alleviate this by returning 'NEEDS_RETRY',
--- a/drivers/scsi/device_handler/scsi_dh_alua.c
+++ b/drivers/scsi/device_handler/scsi_dh_alua.c
@@ -451,7 +451,7 @@ static int alua_check_sense(struct scsi_device
*sdev,
/*
* LUN Not Accessible - ALUA state transition
*/
- return ADD_TO_MLQUEUE;
+ return NEEDS_RETRY;
if (sense_hdr->asc == 0x04 && sense_hdr->ascq == 0x0b)
/*
* LUN Not Accessible -- Target port in
standby state
but then the command will be aborted after the retry count has been
exhausted. Which will then cause I/O errors. Also not good.
Is there a way of forcing a delayed retry, like BLKPREP_DEFER does?
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2011-08-25 13:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E564FC7.10507@suse.de \
--to=hare@suse.de \
--cc=Martin.George@netapp.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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