From: Mike Christie <michael.christie@oracle.com>
To: Martin Wilck <martin.wilck@suse.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
James Bottomley <jejb@linux.vnet.ibm.com>,
Ewan Milne <emilne@redhat.com>,
linux-scsi@vger.kernel.org
Cc: Bart Van Assche <bvanassche@acm.org>,
Damien Le Moal <dlemoal@kernel.org>,
Martin Wilck <mwilck@suse.com>
Subject: Re: [PATCH v4] I/O errors for ALUA state transitions
Date: Wed, 8 May 2024 10:48:48 -0500 [thread overview]
Message-ID: <fd4b5ed6-6e63-4a71-b2a0-f29ad02a2e7a@oracle.com> (raw)
In-Reply-To: <20240508102426.19358-1-mwilck@suse.com>
On 5/8/24 5:24 AM, Martin Wilck 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.
>
> mwilck: Moved this code to alua_check_sense() as suggested by
> Mike Christie [1]. Evan Milne had raised the question whether pg->state
> should be set to transitioning in the UA case [2]. I believe that doing
> this is correct. SCSI_ACCESS_STATE_TRANSITIONING by itself doesn't cause
> I/O errors. Our handler schedules an RTPG, which will only result in
> an I/O error condition if the transitioning timeout expires.
>
> [1] https://lore.kernel.org/all/0bc96e82-fdda-4187-148d-5b34f81d4942@oracle.com/
> [2] https://lore.kernel.org/all/CAGtn9r=kicnTDE2o7Gt5Y=yoidHYD7tG8XdMHEBJTBraVEoOCw@mail.gmail.com/
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> Signed-off-by: Martin Wilck <mwilck@suse.com>
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> ---
Reviewed-by: Mike Christie <michael.christie@oracle.com>
next prev parent reply other threads:[~2024-05-08 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 10:24 [PATCH v4] I/O errors for ALUA state transitions Martin Wilck
2024-05-08 12:39 ` Christoph Hellwig
2024-05-08 15:48 ` Mike Christie [this message]
2024-05-09 1:47 ` Martin K. Petersen
2024-05-13 13:51 ` Martin Wilck
2024-05-13 14:27 ` 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=fd4b5ed6-6e63-4a71-b2a0-f29ad02a2e7a@oracle.com \
--to=michael.christie@oracle.com \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=martin.wilck@suse.com \
--cc=mwilck@suse.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.