From: Matthias Andree <matthias.andree@gmx.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: SCSI Write Cache Enable in 2.4.20?
Date: Thu, 19 Jun 2003 22:58:39 +0200 [thread overview]
Message-ID: <20030619205839.GA11080@merlin.emma.line.org> (raw)
In-Reply-To: <3EF1EB2E.8010702@pobox.com>
On Thu, 19 Jun 2003, Jeff Garzik wrote:
> This sounds like a bug, either in an application, or in Linux kernel's
> scsi disk implementation.
>
> Data is only guaranteed to be written onto disk following an
> fsync(2)-like operation in the application. And in turn, it is the
> Linux kernel's responsibility to ensure that such a flush is propagated
> all the down to the low-level driver, in my opinion. Sophisticated
I think file systems also have certain write ordering requirements to
maintain on-disk consistency, these would also need to make sure the
order is correct. AFAICS, SuSE have patched the reiserfs in their
2.4.20 kernel (8.2) to use write barriers (however deep these are
anchored), but ext3 or xfs don't show related log entries at boot-up or
mount time.
Is this something that will be fixed in 2.6 or will 2.6 still require me
to turn off the write cache?
> hosts can have barriers, and "dumb" hosts can simply call the drive's
> flush-cache / sync-cache command.
--
Matthias Andree
next prev parent reply other threads:[~2003-06-19 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 18:25 SCSI Write Cache Enable in 2.4.20? Cress, Andrew R
2003-06-13 20:36 ` Matthias Andree
2003-06-19 16:56 ` Jeff Garzik
2003-06-19 20:58 ` Matthias Andree [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-12 9:24 Matthias Andree
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=20030619205839.GA11080@merlin.emma.line.org \
--to=matthias.andree@gmx.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;
as well as URLs for NNTP newsgroup(s).