From: Dave Olien <dmo@osdl.org>
To: Tim Pepper <tpepper@gmail.com>, linux-scsi@vger.kernel.org
Subject: Re: Question about Request Sense case in scsi_lib.c
Date: Tue, 12 Oct 2004 09:59:19 -0700 [thread overview]
Message-ID: <20041012165919.GA27526@osdl.org> (raw)
In-Reply-To: <eada2a07041012092973d35415@mail.gmail.com>
Tim,
Thanks for the feedback. Yes, Automatic volume transfer is on, and I
was expecting there'd be poor performance as a result. I just
didn't expect to get IO errors. The odd thing is that the "bus reset"
leads to the SCSI request being requeued. But every once in a while,
the requeue fails with errors and the request is failed. I'll look at
these cases a little more closely, try to understand why the requeues fail.
I think the dm multipathing software will soon have hooks to
support manual volume transfer in these situations.
Dave
On Tue, Oct 12, 2004 at 09:29:30AM -0700, Tim Pepper wrote:
> I thought on FAStT's while there are dual-active controllers, for a
> given lun they weren't active-active, but rather active-passive with
> either manual or automatic volume transfer. Assuming automatic volume
> transfer is on and you send IOs to both controllers simultaneously you
> would ping-pong the cache, drive IO rates lower and possibly see that
> manifest itself in interesting behaviour in the linux scsi stack.
> With manual volume transfer you should get IO errors from the
> controller which is not active or preferred for the given lun. Maybe
> somebody involved with their RDAC multipathing driver follows this
> list and can comment on their intentions for the 2.6 kernel and dm
> multipathing.
next prev parent reply other threads:[~2004-10-12 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 0:00 Question about Request Sense case in scsi_lib.c Dave Olien
[not found] ` <eada2a07041012092973d35415@mail.gmail.com>
2004-10-12 16:31 ` Tim Pepper
2004-10-12 16:59 ` Dave Olien [this message]
2004-10-12 17:13 ` James Bottomley
2004-10-12 17:59 ` Dave Olien
2004-10-12 20:13 ` Patrick Mansfield
2004-10-12 20:44 ` Dave Olien
2004-10-13 2:10 ` Douglas Gilbert
2004-10-13 17:56 ` Dave Olien
[not found] <53CF1076699CD711B7DD0002A51363F1072A6E3A@exw-ks.ks.lsil.com>
2004-10-13 21:46 ` 'Dave Olien'
2004-10-13 21:56 ` James Bottomley
2004-10-13 22:09 ` 'Dave Olien'
2004-10-14 17:52 ` 'Dave Olien'
2004-10-14 18:05 ` James Bottomley
2004-10-14 20:39 ` James Bottomley
2004-10-14 0:30 ` Douglas Gilbert
2004-10-14 6:49 ` Lan Tran
2004-10-14 15:25 ` James Bottomley
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=20041012165919.GA27526@osdl.org \
--to=dmo@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tpepper@gmail.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.