All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Greg Stark <gsstark@mit.edu>
Cc: Mark Lord <liml@rtr.ca>,
	linux-kernel@vger.kernel.org,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: SMART support for libata
Date: Fri, 10 Jun 2005 08:38:59 +0200	[thread overview]
Message-ID: <20050610063858.GN5140@suse.de> (raw)
In-Reply-To: <87u0k74cuy.fsf@stark.xeocode.com>

On Thu, Jun 09 2005, Greg Stark wrote:
> 
> Mark Lord <liml@rtr.ca> writes:
> 
> > Greg Stark wrote:
> > ..
> > >>You should be using "-y" (standby) instead of "-Y" (sleep).
> > > I'll try that. But that's not going to make it spin up when it gets a SMART
> > > query is it?
> > 
> > Depends on what SMART items are being queried.
> > 
> > Actually, what you should *really* be using is "hdparm -S"
> > with a suitable timeout value (say, 30 or larger).
> 
> Not really since the drive will just spin up ever few seconds as bdflush (or
> whatever it's called these days) dribbles out pages.
> 
> What I should *really* be using is the noflushd daemon. That's been on hold
> since I found it didn't work with SATA drives. But I wonder if it would work
> these days.

noflushd is ancient, have you tried playing with laptop mode?

-- 
Jens Axboe


  reply	other threads:[~2005-06-10  6:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 19:00 SMART support for libata Greg Stark
2004-12-08 22:12 ` SMART support for libata (SATA) David Greaves
2004-12-09  6:24 ` SMART support for libata Jeff Garzik
2005-06-08 16:59   ` Greg Stark
2005-06-08 18:52     ` Mark Lord
2005-06-09  3:08       ` Greg Stark
2005-06-09 15:25         ` Mark Lord
2005-06-09 18:13           ` Greg Stark
2005-06-10  6:38             ` Jens Axboe [this message]
2005-06-10 15:35               ` Greg Stark
2005-06-11 19:25                 ` Adrian Bunk

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=20050610063858.GN5140@suse.de \
    --to=axboe@suse.de \
    --cc=gsstark@mit.edu \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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 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.