public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: ncunningham@users.sourceforge.net, john@grabjohn.com,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH: Shutdown IDE before powering off.
Date: Thu, 22 Jan 2004 11:02:59 -0500	[thread overview]
Message-ID: <400FF433.2010906@pobox.com> (raw)
In-Reply-To: <20040122004554.26536158.akpm@osdl.org>

Andrew Morton wrote:
> Nigel Cunningham <ncunningham@users.sourceforge.net> wrote:
> 
>>Hi.
>>
>>On Thu, 2004-01-22 at 21:13, John Bradford wrote:
>>
>>>>This spins down the disk(s) when you're just doing do a reboot.  That's
>>>>fairly irritating and could affect reboot times if one has many disks.
>>>
>>>I think it is an attempt to force some broken drives to flush their
>>>cache, but I wonder whether it will simply move the problem from one
>>>set of broken drives to another :-).
>>
>>Yes, they were trying to get caches flushed. If this attempt is
>>misguided, that's fine. Is there a better way?
> 
> 
> A couple of thoughts come to mind:
> 
> a) Don't do it if the user typed reboot - only do it if we're powering down.
> 
> b) Try to do a cache flush instead.  If that fails (do we know?) then
>    power down the disk instead.


I'm either shock or very very worried that the reboot notifier that 
flushes IDE in 2.4.x, ide_notifier, is nowhere to be seen in 2.6.x :( 
That seems like the real problem -- the code _used_ to be there.

	Jeff




  parent reply	other threads:[~2004-01-22 16:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22  1:42 PATCH: Shutdown IDE before powering off Nigel Cunningham
2004-01-22  7:49 ` Andrew Morton
2004-01-22  8:13   ` John Bradford
2004-01-22  8:26     ` Nigel Cunningham
2004-01-22  8:45       ` Andrew Morton
2004-01-22  9:10         ` Nigel Cunningham
2004-01-22 16:02         ` Jeff Garzik [this message]
2004-01-22 17:13           ` Bartlomiej Zolnierkiewicz
2004-01-22 10:08       ` John Bradford
2004-01-22 19:19     ` James H. Cloos Jr.
2004-01-22 19:36       ` Nigel Cunningham
2004-01-22 19:52         ` James H. Cloos Jr.
2004-01-22 21:07       ` Jeff Garzik
     [not found] <1gC8S-6UB-5@gated-at.bofh.it>
     [not found] ` <1gIHq-3JU-23@gated-at.bofh.it>
     [not found]   ` <1gPzb-1OM-17@gated-at.bofh.it>
     [not found]     ` <1gQET-2Qn-9@gated-at.bofh.it>
2004-03-11 21:46       ` Karol Kozimor

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=400FF433.2010906@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@users.sourceforge.net \
    /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