public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Scott M. Ferris" <sferris@acm.org>
Cc: Mike Christie <mikenc@us.ibm.com>,
	linux-iscsi-devel <linux-iscsi-devel@lists.sourceforge.net>,
	linux-scsi@vger.kernel.org
Subject: Re: [linux-iscsi-devel] [question] deferred sense
Date: Wed, 5 Jan 2005 16:23:33 +0100	[thread overview]
Message-ID: <20050105152333.GA1453@lst.de> (raw)
In-Reply-To: <20050105152112.GA8472@visi.com>

On Wed, Jan 05, 2005 at 09:21:12AM -0600, Scott M. Ferris wrote:
> On Wed, Jan 05, 2005 at 10:21:44AM +0100, Christoph Hellwig wrote:
> > 
> > The kernel still doesn't hadle deferred sense correctly.  In fact I'm
> > not sure it's entirely possible to handle deferred sense correctly.
> > 
> > The iscsi driver variant of "translating" it to normal sense data and
> > that for disks only certainly doesn't make much sense.
> 
> To be more specific, there were some devices that would fail a command
> and return deferred sense.  The command didn't complete at the target,
> and the kernel wasn't retrying it because the sense was deferred
> rather than current.  For those devices, the translation produced the
> desired retry.

Do you remember these devices?  Might be worth adding a midlayer
blacklist entry for them.

And I suspect we should get linux-scsi in the loop for the discussion
about deferred sense handling.

       reply	other threads:[~2005-01-05 15:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41DB21D7.5080904@us.ibm.com>
     [not found] ` <20050104234700.GA18343@visi.com>
     [not found]   ` <20050105092144.GB26793@lst.de>
     [not found]     ` <20050105152112.GA8472@visi.com>
2005-01-05 15:23       ` Christoph Hellwig [this message]
2005-01-05 16:44         ` [linux-iscsi-devel] [question] deferred sense James Bottomley
2005-01-06 16:37           ` Tom Coughlan
2005-01-07  0:06             ` Douglas Gilbert
2005-01-11 11:44               ` Douglas Gilbert
2005-01-05 17:47 Salyzyn, Mark
2005-01-05 21:51 ` James Bottomley
2005-01-05 22:58   ` Matthew Wilcox
2005-01-06 23:09   ` Bryan Henderson
  -- strict thread matches above, loose matches on Subject: below --
2005-01-06 14:23 Salyzyn, Mark
2005-01-06 14:38 ` James Bottomley
2005-01-06 14:57 Salyzyn, Mark
2005-01-06 15:50 ` 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=20050105152333.GA1453@lst.de \
    --to=hch@lst.de \
    --cc=linux-iscsi-devel@lists.sourceforge.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mikenc@us.ibm.com \
    --cc=sferris@acm.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