From: Jens Axboe <jens.axboe@oracle.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is BIO_RW_FAILFAST really usable?
Date: Tue, 4 Dec 2007 10:13:34 +0100 [thread overview]
Message-ID: <20071204091334.GG23294@kernel.dk> (raw)
In-Reply-To: <18260.49019.684445.303719@notabene.brown>
On Tue, Dec 04 2007, Neil Brown wrote:
>
> I've been looking at use BIO_RW_FAILFAST in md/raid to improve
> handling of some error cases.
>
> This is particularly significant for the DASD driver (s390 specific).
> I believe it uses optic fibre to connect to the drives. When one of
> these paths is unplugged, IO requests will block until an operator
> runs a command to reset the card (or until it is plugged back in).
> The only way to avoid this blockage is to use BIO_RW_FAILFAST. So
> we really need BIO_RW_FAILFAST for a reliable RAID1 configuration on
> DASD drives.
>
> However, I just tested BIO_RW_FAILFAST on my SATA drives: controller
>
> 02:06.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02)
>
> (not using the cards minimal RAID functionality) and requests fail
> immediately and always with e.g.
>
> sd 2:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
> end_request: I/O error, dev sdc, sector 2048
>
> So fail fast obviously isn't generally usable.
>
> What is the answer here? Is the Silicon Image driver doing the wrong
> thing, or is DASD doing the wrong thing, or is BIO_RW_FAILFAST
> under-specified and we really need multiple flags or what?
Hrmpf. It looks like the SCSI layer is a little too trigger happy. Any
chance you could try and trace where this happens?
--
Jens Axboe
next prev parent reply other threads:[~2007-12-04 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 2:46 Is BIO_RW_FAILFAST really usable? Neil Brown
2007-12-04 3:51 ` Jeff Garzik
2007-12-04 4:19 ` Andrey Borzenkov
2007-12-04 9:13 ` Jens Axboe [this message]
2007-12-05 23:14 ` Neil Brown
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=20071204091334.GG23294@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).