From: Joern Quillman <quillman@fbihome.de>
To: linux-scsi@vger.kernel.org
Subject: Spinup of SCSI Disks: allow_restart won't work on 2.6.18
Date: Fri, 17 Nov 2006 18:38:34 +0100 [thread overview]
Message-ID: <455DF39A.6090209@fbihome.de> (raw)
Hi
I'm having troubles using the sysfs interface for enabling automatic
spinup of SCSI Drives.
I searched the archives of this list and after discovering the patches
for enabling automatic spinup for SCSI disk drives I updated to a recent
2.6.18-2 kernel (debian unstable).
I have now the allow_restart entry in sysfs.
It's set to 0 in my machine and it won't let me change it with 'echo 1 >
allow_restart' or echo -n. I always get a write error.
The first thing I thought about was that it may be set to 0 by default
and so I took a look into the original source of my debian kernel.
It's set to 'sdev->allow_restart = 1' everywhere in the source as I can
see and I'm getting confused right now.
Why can't I change the allow_restart setting at runtime? According to
former posts on this list it should be possible.
Is there another way to force automatic spinup of my firewire drives?
My setup consists of a bunch of 8 IDE harddisks connected through some
OXFW911 Firewire Bridges.
Thanks
Joern
next reply other threads:[~2006-11-17 17:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 17:38 Joern Quillman [this message]
2006-11-17 21:44 ` Spinup of SCSI Disks: allow_restart won't work on 2.6.18 Joern Quillmann
2006-11-17 23:34 ` Stefan Richter
2006-11-17 23:36 ` Stefan Richter
2006-11-20 10:52 ` Joern Quillman
2006-11-20 11:48 ` Stefan Richter
2006-11-20 22:32 ` Joern Quillman
2006-11-20 23:53 ` Stefan Richter
2006-11-21 0:54 ` Douglas Gilbert
2006-11-21 4:20 ` James Bottomley
2006-11-21 8:12 ` Stefan Richter
2006-11-21 14:41 ` Brian King
2006-11-21 20:34 ` [PATCH] scsi: sd: configurable allow_restart attribute for all device types Stefan Richter
2006-11-21 1:09 ` Spinup of SCSI Disks: allow_restart won't work on 2.6.18 Joern Quillmann
2006-11-21 20:49 ` 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=455DF39A.6090209@fbihome.de \
--to=quillman@fbihome.de \
--cc=linux-scsi@vger.kernel.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