From: Stewart Smith <stewart@flamingspork.com>
To: lachlan@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: review: propogate return codes from flush routines
Date: Wed, 06 Sep 2006 19:04:41 +1000 [thread overview]
Message-ID: <1157533481.12018.33.camel@localhost.localdomain> (raw)
In-Reply-To: <44FD476C.3080009@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On Tue, 2006-09-05 at 10:46 +0100, Lachlan McIlroy wrote:
> What's a really catastrophic error?
I think I've just spent too much time with HA database clusters... good
temporary errors "out of resource", okay temp errors "node failed" or
"lost connection", bad errors "cluster failure", catastrophic "and your
data is gone too and backups haven't been working". :)
I sometimes forget that the rest of the world can just have "errors".
--
Stewart Smith (stewart@flamingspork.com)
http://www.flamingspork.com/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-09-06 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 11:25 review: propogate return codes from flush routines Lachlan McIlroy
2006-09-05 7:54 ` Stewart Smith
2006-09-05 9:46 ` Lachlan McIlroy
2006-09-06 9:04 ` Stewart Smith [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=1157533481.12018.33.camel@localhost.localdomain \
--to=stewart@flamingspork.com \
--cc=lachlan@sgi.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox