From: James Bottomley <James.Bottomley@SteelEye.com>
To: 'Dave Olien' <dmo@osdl.org>
Cc: "Qi, Yanling" <yanling.qi@engenio.com>,
Douglas Gilbert <dougg@torque.net>,
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: 14 Oct 2004 13:05:02 -0500 [thread overview]
Message-ID: <1097777109.2198.31.camel@mulgrave> (raw)
In-Reply-To: <20041014175218.GA31885@osdl.org>
On Thu, 2004-10-14 at 12:52, 'Dave Olien' wrote:
> comp cmd cfa9d8a0 good_bytes 0 nr_phys_req 5 use_sg 10
> Incorrect number of segments after building list cmd cfa9d8a0
> counted 10, received 5
> req nr_sec 1024, cur_nr_sec 8
> Buffer I/O error on device sda, logical block 5489
Well, I managed to create a test rig that randomly rejects commands with
UNIT ATTENTION (and QUEUE FULL just for good measure). So far I've seen
this condition once so it looks like you have the better ability to
reproduce.
What happens is that nr_phys_segments is being reduced *after* the
sgtable is allocated the first time (otherwise there would be an
Incorrect segments message for its initial mapping). Why this is
happening, I still can't fathom.
James
next prev parent reply other threads:[~2004-10-14 18:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53CF1076699CD711B7DD0002A51363F1072A6E3A@exw-ks.ks.lsil.com>
2004-10-13 21:46 ` Question about Request Sense case in scsi_lib.c '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 [this message]
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
2004-10-12 0:00 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
2004-10-12 20:44 ` Dave Olien
2004-10-13 2:10 ` Douglas Gilbert
2004-10-13 17:56 ` Dave Olien
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=1097777109.2198.31.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=dmo@osdl.org \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=tpepper@gmail.com \
--cc=yanling.qi@engenio.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox