mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
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 11:53:56 +0200	[thread overview]
Message-ID: <20020914095356.GA28271@merlin.emma.line.org> (raw)
In-Reply-To: <20020914010101.75725.qmail@web40502.mail.yahoo.com>

On Fri, 13 Sep 2002, Alex Davis wrote:

> The cleanup() function in ide-disk.c will flush the write cache. Also, would
> someone please point me to some documentation that states the cache is flushed
> when the disk is put in standby: when I called Maxtor about this, they said that

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.

> the cache is NOT flushed. BTW, if your disk is so broken as to require being put
> in standby mode to flush its write cache, then you are at great risk for data
> corruption.

See above. Disable Write Cache would also do with recent drives.

IBM specified for the DeskStar 40GV and 75GXP drives (DTLA, I use this
manual as I have that handy) that Soft Reset, Standby (Immediate) and
Flush Cache commands would only be executed after the completion of
writing to media (see the OEM manual, section 10.10 write cache
function, p.91 in my edition), and goes on "It is recommended that the
host system verify the completion of the write cache operation by
issuing Soft reset, the Standby (Immediate) command, or the Flush Cache
command to the device before power off."

I think I recall that some notebook drives would need the standby
immediate to flush the cache to work around firmware bugs with other
methods.


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.

-- 
Matthias Andree

  reply	other threads:[~2002-09-14  9:49 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 [this message]
2002-09-14 13:37   ` Alan Cox
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=20020914095356.GA28271@merlin.emma.line.org \
    --to=matthias.andree@stud.uni-dortmund.de \
    --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

all inboxes | Powered by JetHome®