public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Johannes Weiner <hnazfoo@googlemail.com>
Cc: linux-kernel@vger.kernel.org, Patrick Mau <mau@oscar.ping.de>
Subject: Re: Question about "Not Ready" SCSI error
Date: Mon, 31 Jul 2006 01:22:06 +0200	[thread overview]
Message-ID: <44CD3F1E.1010101@s5r6.in-berlin.de> (raw)
In-Reply-To: <20060730215257.GA8339@leiferikson.dystopia.lan>

Johannes Weiner wrote:
> On Sun, Jul 30, 2006 at 08:10:19PM +0200, Patrick Mau wrote:
>> Google revealed[1] that the drive is waiting for a START UNIT command,
>> but it seems that the kernel is not attempting to spin up the drive
>> again.
> 
> I don't know exactly if it's enough to requeue the scsi command, please
> comment on this, guys.

AFAIU, the scsi_eh (error handler) already has proper code for exactly 
this purpose, but the code is inactive. Any driver (SCSI low-level 
driver or SCSI command set driver) can activate it by setting 
scsi_device->allow_restart = 1.

Brian King posted a patch which lets you enable that flag at runtime:
"scsi: Add allow_restart sysfs class attribute", 2006-06-27
http://marc.theaimsgroup.com/?l=linux-scsi&m=115142503103468

The patch is in Linus' tree now.
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/scsi/sd.c
-- 
Stefan Richter
-=====-=-==- -=== =====
http://arcgraph.de/sr/

  reply	other threads:[~2006-07-30 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 18:10 Question about "Not Ready" SCSI error Patrick Mau
2006-07-30 21:52 ` Johannes Weiner
2006-07-30 23:22   ` Stefan Richter [this message]
2006-07-30 22:28 ` Johannes Weiner
2006-07-31 23:13 ` Philippe Troin
2006-08-01  5:56   ` Stefan Richter

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=44CD3F1E.1010101@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=hnazfoo@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mau@oscar.ping.de \
    /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