From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jonathan Steinert <hachi@kuiki.net>
Cc: linux-kernel@vger.kernel.org,
Johannes Niess <linux@johannes-niess.de>,
linux-usb@vger.kernel.org
Subject: Re: USB attached SATA disk idle spindown
Date: Tue, 24 Jun 2008 10:54:41 +0200 [thread overview]
Message-ID: <4860B651.9090104@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080624045953.GA24600@miyako.sixapart.com>
(adding Cc: linux-usb and Johannes Niess)
On 6/24/2008 6:59 AM, Jonathan Steinert wrote at LKML:
> Dear list,
>
> I am looking for what the current state of USB SATA timed spindown of-
> disks is ata this time. I've been reading documents and mailing lists-
> for every possible search I can dream up on the subject. Suggested-
> workable solutions include (but are probably not limited to):
>
> $ hdparm -S
> This seems to be the ATA way of telling a disk to spin down, and it
> works in some situations, but doesn't appear to work on USB attached
> disks under 2.6.25
>
> $ sdparm
> This is suggested in a small number of locations. Most of which have
> examples on how to disable STANDBY on a handful of devices. I am
> unable to find any evidence that it can actually be used to enable
> power saving.
I think either of these depend on specific support by the USB to SATA
bridge firmware.
I hear some newer bridges and their firmwares implement ATA
pass-through. Would that help?
> $ scsi_spin
> Requires the disk to be unmounted, and I can't find anything saying
> that this is how the world is supposed to be.-
Johannes recently informed me that he wrote a script which is used like
a background daemon to stop idle USB disks. The script uses
- "cat /sys/block/${device}/stat" to watch disk activity,
- "sdparm -q -C stop /dev/${device}" to stop the motor after
longer inactivity.
> I'm hoping that perhaps I'm missing something from this list.
>
> I don't really know whether this is a topic for the scsi people, or the-
> SATA people, or the USB people. So I'm asking here instead to try and
> get my first hints from the parent group.
>
> Thanks in advance,
>
> hachi
IMO it is firstly an USB topic because it depends on the features and
behaviour of the bridge and its firmware.
(PS: Don't have too high expectations of $15 devices.)
--
Stefan Richter
-=====-==--- -==- ==---
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-06-24 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 4:59 Jonathan Steinert
2008-06-24 8:54 ` Stefan Richter [this message]
2008-06-24 9:12 ` Stefan Richter
2008-07-18 1:15 ` Tejun Heo
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=4860B651.9090104@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=hachi@kuiki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@johannes-niess.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
all inboxes | Powered by JetHome®