From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Gustavo Guillermo Pérez" <gustavo@compunauta.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-scsi@vger.kernel.org
Subject: Re: SCSI trow USB-STORAGE or SBP2 Debug for buggy device Kernels 2.6.X
Date: Mon, 24 Apr 2006 17:02:46 -0500 [thread overview]
Message-ID: <1145916166.3528.48.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <200604241630.07453.gustavo@compunauta.com>
On Mon, 2006-04-24 at 16:30 -0500, Gustavo Guillermo Pérez wrote:
> Ok, this is what I've got.
Thanks, this is interesting:
> Apr 24 16:12:14 gusgus kernel: sr 1:0:0:0: Device not ready: <6>: Current:
> sense key=0x2
> Apr 24 16:12:14 gusgus kernel: ASC=0x4 ASCQ=0x8
That's "LU not ready; long write in progress"
> This Other is cause I left the print outside the brackets, cause I want to see
> on closing session.
> Apr 24 16:13:10 gusgus kernel: : Current: sense key=0x2
> Apr 24 16:13:10 gusgus kernel: ASC=0x3a ASCQ=0x0
Yes, that's just medium not present.
So, I could change the long write in progress to a retry. However, I
suspect the reason we got that return is because this device is untagged
(doesn't accept multiple commands at once) and perhaps a better fix
might be to reduce the queue depth down to one to prevent more than one
command being outstanding at any one time.
James
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-04-24 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 15:29 SCSI trow USB-STORAGE or SBP2 Debug for buggy device Kernels 2.6.X Gustavo Guillermo Pérez
2006-04-24 18:38 ` James Bottomley
2006-04-24 21:30 ` Gustavo Guillermo Pérez
2006-04-24 22:02 ` James Bottomley [this message]
2006-04-24 22:12 ` Gustavo Guillermo Pérez
2006-04-25 6:09 ` Stefan Richter
2006-04-25 21:41 ` Gustavo Guillermo Pérez
2006-04-25 21:48 ` James Bottomley
2006-04-27 17:40 ` Gustavo Guillermo Pérez
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=1145916166.3528.48.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=gustavo@compunauta.com \
--cc=linux-scsi@vger.kernel.org \
/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