Skip to contentSkip to conversation

BIO_RW_FAILFAST

DISCUSSION Andy 3 participants 3 messages May 17, 2005 – Jun 3, 2005

Subsystems (2)
lore
Share & tools
lore

Andy

author
#0 lore raw

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?

Andy

#1 lore raw
Quoted 6 lines · Andy

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?

Sincerely,
Lars Marowsky-Brée <[email protected]>

Signature · 4 lines
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business	 -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
#2 lore raw
Quoted 11 lines · Lars Marowsky-Bree
Quoted 6 lines · Andy

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