From: Chris Wedgwood <cw@f00f.org>
To: "Kevin P. Fleming" <kevin@labsysgrp.com>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>, linux-kernel@vger.kernel.org
Subject: Re: Disk hardware caching, performance, and journalling
Date: Mon, 26 Nov 2001 11:11:05 +1300 [thread overview]
Message-ID: <20011126111105.B10622@weta.f00f.org> (raw)
In-Reply-To: <3BFFE8A2.1010708@rueb.com> <Pine.LNX.4.10.10111241402420.3696-100000@coffee.psychology.mcmaster.ca> <20011125222313.D9672@weta.f00f.org> <00e001c175fa$90d02b40$6caaa8c0@kevin>
In-Reply-To: <00e001c175fa$90d02b40$6caaa8c0@kevin>
On Sun, Nov 25, 2001 at 02:45:57PM -0700, Kevin P. Fleming wrote:
I think if you have a large mail server and zero power protection,
you've got much larger problems to worry about than write-behind
caching on your disk drives... my servers have never (in my
memory) experienced a catastrophic power failure, because they're
too easy to avoid.
In the specific case of email; you want to make certain guarantees,
and having data written to non-volatile storage is one of them.
As for power-failures, given enough time and enough hardware you will
get them, even if your machines are dual or triple powered of diverse
UPSs or -48V powered; it still is possible and _will eventually
happen_ that something further down the line like the motherboard will
fry or whatever.
People who assume that a small-window is small enough and decide that
is 'good enough' are dangerous :)
--cw
next prev parent reply other threads:[~2001-11-25 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 18:36 Steve Bergman
2001-11-24 19:08 ` Andrew Morton
2001-11-24 19:39 ` Florian Weimer
2001-11-24 21:57 ` Phil Howard
2001-11-25 9:22 ` Chris Wedgwood
2001-11-24 19:39 ` Mark Hahn
2001-11-25 9:23 ` Chris Wedgwood
2001-11-25 21:45 ` Kevin P. Fleming
2001-11-25 22:11 ` Chris Wedgwood [this message]
2001-11-25 22:29 ` Mark Hahn
2001-11-26 1:10 ` Bernd Eckenfels
2001-11-25 9:19 ` Chris Wedgwood
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=20011126111105.B10622@weta.f00f.org \
--to=cw@f00f.org \
--cc=hahn@physics.mcmaster.ca \
--cc=kevin@labsysgrp.com \
--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®