From: Olaf Hering <olh@suse.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Brian King <brking@us.ibm.com>,
dougg@torque.net, 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: Tue, 11 Jul 2006 14:57:09 +0200 [thread overview]
Message-ID: <20060711125709.GA14741@suse.de> (raw)
In-Reply-To: <44B39764.3030204@s5r6.in-berlin.de>
On Tue, Jul 11, Stefan Richter wrote:
> Olaf Hering wrote:
> > On Mon, Jun 05, Brian King wrote:
> >>Brian King wrote:
> ...
> >>>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.
> ...
> >>Please try the attached patch. It adds a sysfs device attribute
> >>"allow_restart".
> ...
> >Is it safe to have this attribute be 1 per default, and let the user
> >disable it for problematic drives? The IO errors bother me alot...
>
> Matthew Dharm pointed out that it may confuse USB devices:
> http://marc.theaimsgroup.com/?l=linux-scsi&m=107702811830956
I found that after I sent this. I'm ok with the current default, it can
be tweaked as needed in the startup scripts.
prev parent reply other threads:[~2006-07-11 12:57 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
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 [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=20060711125709.GA14741@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=brking@us.ibm.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=parasietje@gmail.com \
--cc=stefanr@s5r6.in-berlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.