From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Possible bug and question about ide_notify_reboot in drivers/ide/ide.c (2.4.19)
Date: Sat, 14 Sep 2002 13:42:06 +0000 (UTC) [thread overview]
Message-ID: <alvebe$45r$1@ncc1701.cistron.net> (raw)
In-Reply-To: 1032010655.12892.8.camel@irongate.swansea.linux.org.uk
In article <1032010655.12892.8.camel@irongate.swansea.linux.org.uk>,
Alan Cox <alan@lxorguk.ukuu.org.uk> 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"
Putting the drive in stand-by mode has the side effect of flushing
the cache. So before poweroff, send the FLUSH CACHE command,
then send the standby command, hope that one of them works ..
I put put-the-drive-in-standby-mode stuff in halt.c of sysvinit
after several reports of fs corruption at poweroff and it seems
to have fixed the problems for the people who reported them.
Mike.
next prev parent reply other threads:[~2002-09-14 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 1:01 Possible bug and question about ide_notify_reboot in drivers/ide/ide.c (2.4.19) Alex Davis
2002-09-14 9:53 ` Matthias Andree
2002-09-14 13:37 ` Alan Cox
2002-09-14 13:42 ` Miquel van Smoorenburg [this message]
-- 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='alvebe$45r$1@ncc1701.cistron.net' \
--to=miquels@cistron.nl \
--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 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).