From: James Bottomley <James.Bottomley@SteelEye.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: usb-storage@lists.one-eyed-alien.net,
linux-usb-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org
Subject: Re: Errors on USB-storage device are ignored.
Date: Mon, 20 Aug 2007 09:03:19 -0400 [thread overview]
Message-ID: <1187614999.3465.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20070820083723.GD21438@bitwizard.nl>
On Mon, 2007-08-20 at 10:37 +0200, Rogier Wolff wrote:
> On Sun, Aug 19, 2007 at 11:09:46PM -0700, Matthew Dharm wrote:
> > Off the cuff, this really looks like something for the SCSI layer. I'll
> > bet there are SCSI devices that do something similar...
> >
> > And, I'm generally reluctant to modify the data to/from a device unless
> > usb-storage *really* has to in order to make it work....
>
> I fully agree, but as the scsi layer has been in existance almost 10
> years longer than USB-storage, and that nobody seems to have encountered
> a device requesting auto-sense, and then reporting no error, I would
> say this is just a classical: "shitty USB implementation".
I'm afraid it is. Reporting NO SENSE is actually a legitimate thing for
a SCSI device to do. Usually it just means that the problem it was
reporting went away in the interim. So, making it mean there's a
serious drive problem would put us in volation of the spec. If this can
be fixed, it will have to be in USB ... probably tied as specificially
as possible to this particular device ... USB storage that correctly
follows the RBC spec is allowed to report NO SENSE for the same reason
as standard SCSI.
James
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
prev parent reply other threads:[~2007-08-20 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 14:58 Errors on USB-storage device are ignored Rogier Wolff
2007-08-20 6:09 ` Matthew Dharm
2007-08-20 8:37 ` Rogier Wolff
2007-08-20 13:03 ` James Bottomley [this message]
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=1187614999.3465.2.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=usb-storage@lists.one-eyed-alien.net \
/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