From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Cc: "Felix E. Klee" <felix.klee@inka.de>, Iustin Pop <iusty@k1024.org>
Subject: Re: Data safety horror stories?
Date: Mon, 18 Feb 2008 22:49:22 +0100 [thread overview]
Message-ID: <200802182249.22577.Martin@lichtvoll.de> (raw)
In-Reply-To: <1203370911.2394.1237549879@webmail.messagingengine.com>
Am Montag 18 Februar 2008 schrieb Felix E. Klee:
> On Mon, 18 Feb 2008 22:28:45 +0100, "Martin Steigerwald"
>
> <Martin@lichtvoll.de> said:
> > I recommend to read my article about write barriers and journalling
> > filesystems for some basic understanding.
> >
> > http://www.linux-magazin.de/heft_abo/sonderheft/2006/04/beschraenktes
> >_schreiben?category=0
> >
> > its in german tough.
>
> Dankeschön - Deutsch ist doch kein Problem. :-)
One thing to add: We have XFS also running on a web cluster for a customer
with softraid 1 over two RAID arrays. We made sure that write caching is
disabled as those RAID arrays are not equipped with NVRAM (could be added
tough, but the customer did not yet). Runs marvelously. Its also running
on some individual servers in that cluster as well.
Well and although the cluster is spread across two locations about 1
kilometer from each other and it was said that power supply could not
fail... well it failed once for both data centers and the cluster
survived that just fine ;-).
BZW I didn't broke that GPG signature. It seems the mailinglist software
being used for the xfs mailinglist mangles mails.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2008-02-18 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 16:46 Data safety horror stories? Felix E. Klee
2008-02-11 17:12 ` Iustin Pop
2008-02-11 21:23 ` Felix E. Klee
2008-02-18 21:28 ` Martin Steigerwald
2008-02-18 21:41 ` Felix E. Klee
2008-02-18 21:49 ` Martin Steigerwald [this message]
2008-02-18 22:50 ` David Chinner
2008-02-11 22:03 ` David Chinner
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=200802182249.22577.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=felix.klee@inka.de \
--cc=iusty@k1024.org \
--cc=linux-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