From: Hannes Reinecke <hare@suse.de>
To: michael.christie@oracle.com,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, Rajashekhar M A <rajs@netapp.com>
Subject: Re: [PATCH] I/O errors for ALUA state transitions
Date: Wed, 8 Sep 2021 08:12:28 +0200 [thread overview]
Message-ID: <783a72db-93c7-92ad-81b4-bc7fee3ce2c1@suse.de> (raw)
In-Reply-To: <0bc96e82-fdda-4187-148d-5b34f81d4942@oracle.com>
On 9/7/21 5:59 PM, michael.christie@oracle.com wrote:
> On 9/7/21 2:16 AM, Hannes Reinecke wrote:
>> From: Rajashekhar M A <rajs@netapp.com>
>>
>> When a host is configured with a few LUNs and IO is running,
>> injecting FC faults repeatedly leads to path recovery problems.
>> The LUNs have 4 paths each and 3 of them come back active after
>> say an FC fault which makes two of the paths go down, instead of
>> all 4. This happens after several iterations of continuous FC faults.
>>
>> Reason here is that we're returning an I/O error whenever we're
>> encountering sense code 06/04/0a (LOGICAL UNIT NOT ACCESSIBLE,
>> ASYMMETRIC ACCESS STATE TRANSITION) instead of retrying.
>>> Signed-off-by: Hannes Reinecke <hare@suse.de>
>> ---
>> drivers/scsi/scsi_error.c | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
>> index 03a2ff547b22..1185083105ae 100644
>> --- a/drivers/scsi/scsi_error.c
>> +++ b/drivers/scsi/scsi_error.c
>> @@ -594,10 +594,11 @@ enum scsi_disposition scsi_check_sense(struct scsi_cmnd *scmd)
>> sshdr.asc == 0x3f && sshdr.ascq == 0x0e)
>> return NEEDS_RETRY;
>> /*
>> - * if the device is in the process of becoming ready, we
>> - * should retry.
>> + * if the device is in the process of becoming ready, or
>> + * transitions between ALUA states, we should retry.
>> */
>> - if ((sshdr.asc == 0x04) && (sshdr.ascq == 0x01))
>> + if ((sshdr.asc == 0x04) &&
>> + (sshdr.ascq == 0x01 || sshdr.ascq == 0x0a))
>> return NEEDS_RETRY;
>
> Why put this here instead of in alua_check_sense with the other ALUA
> state transition check?
>
Good point. Will be updating the patch.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
next prev parent reply other threads:[~2021-09-08 6:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 7:16 [PATCH] I/O errors for ALUA state transitions Hannes Reinecke
2021-09-07 15:59 ` michael.christie
2021-09-08 6:12 ` Hannes Reinecke [this message]
2021-09-08 21:30 ` Ewan Milne
-- strict thread matches above, loose matches on Subject: below --
2025-06-06 13:59 Hannes Reinecke
2025-06-06 14:46 ` Lee Duncan
2025-06-10 2:07 ` Martin K. Petersen
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=783a72db-93c7-92ad-81b4-bc7fee3ce2c1@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=rajs@netapp.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