From: Tejun Heo <htejun@gmail.com>
To: "Renato S. Yamane" <renatoyamane@mandic.com.br>
Cc: Jim Paris <jim@jtan.com>, Jeff Garzik <jeff@garzik.org>,
debian-devel@lists.debian.org, linux-ide@vger.kernel.org,
miquels@cistron.nl
Subject: Re: Warnings on shutdown (Debian Etch and Kernel 2.6.22.9)
Date: Wed, 24 Oct 2007 22:39:29 +0900 [thread overview]
Message-ID: <471F4B11.9030206@gmail.com> (raw)
In-Reply-To: <471F493C.8050804@mandic.com.br>
Renato S. Yamane wrote:
> Jim Paris escreveu:
>> Tejun Heo wrote:
>>> Ehh... I meant something along the line of...
>>>
>>> "Info for Debian VERSION users : if you see this warning there are
>>> several solutions... blah blah".
>>
>> For Debian, I don't think there are any complete solutions yet.
>> The related bug is
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426224
>
> I think that we can fix this if someone can answer this:
>
> $ man halt
> "-h flag: This is important for IDE drives, since the kernel doesn’t
> flush the write cache itself before power-off.."
>
> How can I know if kernel write cache itself? :-)
Kernel has been flushing write cache for many many years now. Man page
needs update. Also, flushing cache from halt is okay. What's hurting
is spinning down the drive from halt.
--
tejun
next prev parent reply other threads:[~2007-10-24 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 2:55 Warnings on shutdown (Debian Etch and Kernel 2.6.22.9) Renato S. Yamane
2007-10-23 8:00 ` Tejun Heo
2007-10-23 10:04 ` Renato S. Yamane
2007-10-23 10:12 ` Tejun Heo
2007-10-23 10:18 ` Renato S. Yamane
2007-10-23 10:21 ` Tejun Heo
2007-10-23 10:52 ` Renato S. Yamane
2007-10-23 12:26 ` Tejun Heo
2007-10-23 23:47 ` Jim Paris
2007-10-24 13:31 ` Renato S. Yamane
2007-10-24 13:39 ` Tejun Heo [this message]
2007-10-25 11:43 ` Renato S. Yamane
2007-10-25 19:45 ` Jim Paris
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=471F4B11.9030206@gmail.com \
--to=htejun@gmail.com \
--cc=debian-devel@lists.debian.org \
--cc=jeff@garzik.org \
--cc=jim@jtan.com \
--cc=linux-ide@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=renatoyamane@mandic.com.br \
/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).