From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible bug and question about ide_notify_reboot in drivers/ide/ide.c (2.4.19)
Date: 14 Sep 2002 14:37:35 +0100 [thread overview]
Message-ID: <1032010655.12892.8.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020914095356.GA28271@merlin.emma.line.org>
On Sat, 2002-09-14 at 10:53, Matthias Andree wrote:
> How about this: The FLUSH CACHE command has only recently become a
> mandatory command for non-PACKET devices, so there may be drives that do
> implement a write cache, but do NOT implement the FLUSH CACHE -- and
> still adhere to some older edition of the ATA standard.
Worse than that. There are drives that did implement it - as a no-op.
They didn't even say "Umm sorry no can do"
> See above. Disable Write Cache would also do with recent drives.
Except some drives have a habit of turning it back on quietly
> If I recall correctly, Windows' shutdown procedure was at some time in
> the past changed to wait a couple of seconds before switching the ATX
> computers off, to allow the drives to flush their caches. I can't quote
> on a KB article though.
Flush on shutdown was apparently one of the windows 98 service pack/hot
fix additions.
next prev parent reply other threads:[~2002-09-14 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 1:01 Alex Davis
2002-09-14 9:53 ` Matthias Andree
2002-09-14 13:37 ` Alan Cox [this message]
2002-09-14 13:42 ` Miquel van Smoorenburg
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 2:37 Alex Davis
2002-09-13 13:09 ` Alan Cox
2002-09-13 15:10 ` Tomas Szepe
2002-09-13 15:14 ` Alan Cox
2002-09-13 17:54 ` Tomas Szepe
2002-09-14 0:22 ` Matthias Andree
2002-09-13 15:19 ` Alex Davis
2002-09-13 16:15 ` Alan Cox
2002-09-13 17:39 ` Andre Hedrick
2002-09-14 1:08 ` Alex Davis
2002-09-14 0:21 ` Matthias Andree
2002-09-14 17:09 ` jbradford
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=1032010655.12892.8.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.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®