From: John Bradford <john@grabjohn.com>
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: fverscheure@wanadoo.fr, linux-kernel@vger.kernel.org,
marcelo@conectiva.com.br, andre@linux-ide.org
Subject: Re: Problem in IDE Disks cache handling in kernel 2.4.XX
Date: Fri, 10 Jan 2003 17:02:44 +0000 (GMT) [thread overview]
Message-ID: <200301101702.h0AH2iqI013527@darkstar.example.net> (raw)
In-Reply-To: <1042219407.31848.71.camel@irongate.swansea.linux.org.uk> from "Alan Cox" at Jan 10, 2003 05:23:29 PM
> > 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.
>
> We always issue standby or sleep commands to a drive before powering
> off which means the cache flush thing should never have been an
> issue.
I experienced drives spinning back up after they had been flushed on
powerdown, which is not necessarily wrong, (I.E. I never noticed any
data loss), but it's not ideal. Can't we do:
* Standby
* Flush
* Standby
or is there a reason not to? I know there were discussions about the
right order to do the standyby and flush, and as far as I remember, we
never reached a conclusion :-).
John.
prev parent reply other threads:[~2003-01-10 16:55 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
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 [this message]
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=200301101702.h0AH2iqI013527@darkstar.example.net \
--to=john@grabjohn.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.