From: Hans Reiser <reiser@namesys.com>
To: "Eric D. Mudama" <edmudama@mail.bounceswoosh.org>
Cc: linux-kernel@vger.kernel.org, Chris Mason <mason@suse.com>
Subject: Re: 2.6.0-test11 data loss
Date: Thu, 25 Dec 2003 09:15:52 +0300 [thread overview]
Message-ID: <3FEA8098.3000004@namesys.com> (raw)
In-Reply-To: <20031225020738.GA24690@bounceswoosh.org>
Eric D. Mudama wrote:
>
>
>
> It seems to me that the problem occurred at a higher system level than
> the disk, and disabling the write cache on the drive (besides being a
> *HUGE* performance loser) will only make the window for failure
> smaller, not eliminate it entirely.
>
You should only use write caching in kernels where write cache flushing
is supported. Chris, which ones are those, could you remind us?
--
Hans
next prev parent reply other threads:[~2003-12-25 6:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 21:59 2.6.0-test11 data loss Keith Lea
2003-12-24 22:22 ` Gergely Tamas
2003-12-24 22:34 ` Con Kolivas
2003-12-25 2:07 ` Eric D. Mudama
2003-12-25 5:17 ` Con Kolivas
2003-12-25 6:15 ` Hans Reiser [this message]
2003-12-25 16:46 ` Tomas Szepe
2003-12-25 23:45 ` Hmamouche, Youssef
2003-12-25 1:21 ` Felipe Alfaro Solana
2003-12-25 6:11 ` Hans Reiser
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=3FEA8098.3000004@namesys.com \
--to=reiser@namesys.com \
--cc=edmudama@mail.bounceswoosh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
/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.