linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian King <brking@us.ibm.com>
To: dougg@torque.net
Cc: Andrew Morton <akpm@osdl.org>,
	linux-scsi@vger.kernel.org, Ruben Faelens <parasietje@gmail.com>
Subject: Re: Fw: SCSI device not spinning up on rw
Date: Sun, 04 Jun 2006 17:11:46 -0500	[thread overview]
Message-ID: <44835AA2.1070809@us.ibm.com> (raw)
In-Reply-To: <44825D9F.9070305@torque.net>

Douglas Gilbert wrote:
>> I have a SCSI disk, which I want to spin down when the system is not in
>> use. I do this by using sdparm, scsi-spin or sg-utils. These tools all
>> spin down the SCSI drive by using an IOCTL.
>>
>> Problem is that the kernel doesn't spin the drive back up. When a
>> process requests data from the disk (a simple ls), the kernel responds
>> with an I/O error. After some of these errors, reiserfs marks the drive
>> read-only.

Setting sdev->allow_restart in struct scsi_device will cause sense
key/code/qual of 02/04/02 (not ready, initialization command required)
to wake up the scsi error handler and will force scsi core to issue
a start unit command to the disk. I added this a while back to handle
ipr raid arrays which need a start unit command each time the adapter
gets reset. It would be easy enough for sd to use this, either
all the time, or only when directed to, or we could add a sysfs attribute
to the disk to enable/disable this behavior.

Brian


  reply	other threads:[~2006-06-04 22:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-04  1:23 Fw: SCSI device not spinning up on rw Andrew Morton
2006-06-04  4:12 ` Douglas Gilbert
2006-06-04 22:11   ` Brian King [this message]
2006-06-05 18:04     ` Brian King
2006-07-11  6:20       ` Olaf Hering
2006-07-11 12:19         ` Stefan Richter
2006-07-11 12:57           ` Olaf Hering

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=44835AA2.1070809@us.ibm.com \
    --to=brking@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=parasietje@gmail.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;
as well as URLs for NNTP newsgroup(s).