From: Patrick Mansfield <patmans@us.ibm.com>
To: Dave Olien <dmo@osdl.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Tim Pepper <tpepper@gmail.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Question about Request Sense case in scsi_lib.c
Date: Tue, 12 Oct 2004 13:13:17 -0700 [thread overview]
Message-ID: <20041012201317.GA14345@beaverton.ibm.com> (raw)
In-Reply-To: <20041012175943.GB27526@osdl.org>
On Tue, Oct 12, 2004 at 10:59:43AM -0700, Dave Olien wrote:
>
> James,
>
> On Tue, Oct 12, 2004 at 12:13:13PM -0500, James Bottomley wrote:
> >
> > Hang on a minute ... if you're ping pong'ing the drives using AVT, those
> > transfers take time to achieve. The device is probably returning UNIT
> > ATTENTION, NOT_READY while the transfer is in progress. This is
> > probably the source of the requeue.
>
> OK, This probably makes sense. I'm going to see if I can
> get a theory of operations for this device somewhere. I'd
> like to have a better understanding of how the device
> works and how long it takes to do these transfers.
I ran that way (use both controllers for one LUN while in AVT mode) a long
time ago, I don't know the timing, but performance was horrid. I can't
think of any reason to run that way, other than trying to duplicate this
bug ;-)
AFAIR the "transfer" is moving cached data from one controller of the disk
array to the other, but it must have some sort of synchronization method.
But try running with the scsi command completion logging on, it should
dump the full sense data.
You can run at this log level without generating extra IO (won't log the
logging), make sure you have CONFIG_SCSI_LOGGING on, and then use:
sysctl -w dev.scsi.logging_level=0x1200
Or just use /proc/sys/dev/scsi/logging_level ...
Set back to zero to turn off logging:
sysctl -w dev.scsi.logging_level=0
And you should get logging for non-zero scmd->result IO completions
(scmd->result is 2 meaning check condition in the below output) like this:
Oct 12 13:00:54 elm3b79 kernel: scsi <0:0:0:0> done SUCCESS 2 scsi0 : destination target 0, lun 0
Oct 12 13:00:54 elm3b79 kernel: command = Inquiry 01 83 00 fe 00
Oct 12 13:00:54 elm3b79 kernel: Current sda: sense key Illegal Request
Oct 12 13:00:54 elm3b79 kernel: Additional sense: Invalid field in cdb
HTH ...
-- Patrick Mansfield
next prev parent reply other threads:[~2004-10-12 20:13 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
2004-10-12 17:13 ` James Bottomley
2004-10-12 17:59 ` Dave Olien
2004-10-12 20:13 ` Patrick Mansfield [this message]
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=20041012201317.GA14345@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=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.