From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 16070] Fail to issue Start/Stop Unit
Date: Fri, 28 May 2010 15:20:53 GMT [thread overview]
Message-ID: <201005281520.o4SFKrW3030561@demeter.kernel.org> (raw)
In-Reply-To: <bug-16070-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16070
--- Comment #1 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org> 2010-05-28 15:20:51 ---
Reply-To: dgilbert@interlog.com
On 10-05-28 10:55 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=16070
>
> Summary: Fail to issue Start/Stop Unit
> Product: IO/Storage
> Version: 2.5
> Kernel Version: 2.6.34-rc5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: SCSI
> AssignedTo: linux-scsi@vger.kernel.org
> ReportedBy: ian@beware.dropbear.id.au
> Regression: No
>
>
> I am attempting to save power by spinning down idle scsi disks. These are old
> fashioned parallel (U320) disks on a SCSI storage controller: LSI Logic /
> Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07).
>
> I do:
>
> sg_start --stop /dev/sde
> echo 0xfffffff> /sys/module/scsi_mod/parameters/scsi_logging_level
> dd if=/dev/sde of=/dev/null count=1
> sleep 10
> echo 0> /sys/module/scsi_mod/parameters/scsi_logging_level
>
> I get:
> dd: reading `/dev/sde': Input/output error
> 0+0 records in
> 0+0 records out
> 0 bytes (0 B) copied, 0.00536828 s, 0.0 kB/s
>
> If I manually spin up the disk with sg_start --start /dev/sde, then things work
> again as expected.
<snip>
>
> After getting: "Add. Sense: Logical unit not ready, initializing command
> required" I would expect a Start/Stop unit command, but it appears that none is
> ever issued.
There is a different design philosophy between SCSI and
ATA disks (and has been for a very long time) reflecting
their different markets. When a SCSI disk is spun down, then
it will return errors on any command trying to do IO
until a SCSI START STOP UNIT command (start) is sent and then
time is allowed for the disk to spin up.
What you report as a bug is the long standing behaviour of
SCSI disks which Linux has not tried to modify.
Doug Gilbert
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-05-28 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 14:55 [Bug 16070] New: Fail to issue Start/Stop Unit bugzilla-daemon
2010-05-28 15:20 ` Douglas Gilbert
2010-05-28 15:35 ` Brian King
2010-05-28 15:20 ` bugzilla-daemon [this message]
2010-05-28 15:36 ` [Bug 16070] " bugzilla-daemon
2010-05-29 0:57 ` bugzilla-daemon
2012-07-20 12:41 ` bugzilla-daemon
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=201005281520.o4SFKrW3030561@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).