From: Patrick Mansfield <patmans@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>,
linux-scsi@vger.kernel.org
Subject: Re: BIO_RW_FAILFAST
Date: Fri, 3 Jun 2005 09:38:37 -0700 [thread overview]
Message-ID: <20050603163837.GA32475@us.ibm.com> (raw)
In-Reply-To: <20050602164123.GE22633@marowsky-bree.de>
On Thu, Jun 02, 2005 at 06:41:23PM +0200, Lars Marowsky-Bree wrote:
> On 2005-05-17T15:59:15, Andy <genanr@emsphone.com> wrote:
>
> > I have been having problems with systems getting I/O errors and dropping
> > mounted filesystems, when it is processing a RCSN caused by some other event
> > on the fabric within its' zone. If I unset BIO_RW_FAILFAST in dm-mpath.c I
> > no longer get the I/O errors and of course no filesystem drops. Are there
> > any plans to change this, or make it a settable option? Are there any
> > negatives to not setting it?
>
> What is "RCSN"? What hardware? And why does it show up on all paths at
> once?
He must have meant a RSCN: Registered State Change Notification ...
Likely qlogic or emulex hardware. AFAIUI, the fibre switch sends an RSCN
to all initiators when it sees a change on the fabric, for example
detaching a cable from the switch or target.
AFAIR some RSCN's can cause glitches, and the FC driver generally wants
scsi core (or here, with fail fast set, maybe dm multipath) to just resend
the command.
I recall some recent changes to qlogic for retry handling in this area,
maybe as part of the queue removal code.
Seems likely that the fast fail is hurting if we get a DID_BUS_BUSY or ???
from the driver.
Seeing the actual IO errors and kernel versions might help, cc-ing
linux-scsi.
Maybe Andrew Vasquez (or James Smart) can comment.
-- Patrick Mansfield
parent reply other threads:[~2005-06-03 16:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050602164123.GE22633@marowsky-bree.de>]
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=20050603163837.GA32475@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
/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