public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: fverscheure@wanadoo.fr
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: Problem in IDE Disks cache handling in kernel 2.4.XX
Date: Fri, 10 Jan 2003 10:19:59 +0000 (GMT)	[thread overview]
Message-ID: <200301101019.h0AAJx5w003433@darkstar.example.net> (raw)
In-Reply-To: <20030110095558.E144CFF11@postfix4-1.free.fr> from "Francis Verscheure" at Jan 10, 2003 10:54:53 AM

> And by the way how are powered off the IDE drives ?
> Because a FLUSH CACHE or STANDY or SLEEP is MANDATORY before
> powering off the drive with cache enabled or you will enjoy lost
> data.

This was discussed on the list a few months ago:

http://marc.theaimsgroup.com/?l=linux-kernel&m=103188486216124&w=2

I'm not sure it really got fully resolved, I had disks that would
spin down and then spin up again, because of the order that the
standby and flush cache commands were sent.

John

  reply	other threads:[~2003-01-10 10:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10  9:54 Problem in IDE Disks cache handling in kernel 2.4.XX Francis Verscheure
2003-01-10 10:19 ` John Bradford [this message]
2003-01-10 11:37 ` Alan Cox
2003-01-10 11:07   ` Benjamin Herrenschmidt
2003-01-10 11:14   ` Andre Hedrick
2003-01-10 13:35     ` Alan Cox
2003-01-10 13:03       ` Andre Hedrick
2003-01-10 14:13         ` Alan Cox
2003-01-10 16:48           ` Jens Axboe
2003-01-10 18:12             ` Alan Cox
2003-01-10 18:12               ` PATCH: [2.4.21-pre3] Fix for SMP race condition in IDE code Ross Biro
2003-01-10 19:29                 ` Alan Cox
2003-01-10 20:22                 ` Andre Hedrick
2003-01-10 18:25               ` Problem in IDE Disks cache handling in kernel 2.4.XX Jens Axboe
2003-01-10 17:23 ` Alan Cox
2003-01-10 17:02   ` John Bradford

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=200301101019.h0AAJx5w003433@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=fverscheure@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.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