From: "Felix E. Klee" <felix.klee@inka.de>
To: Martin Steigerwald <Martin@lichtvoll.de>, linux-xfs@oss.sgi.com
Cc: Iustin Pop <iusty@k1024.org>
Subject: Re: Data safety horror stories?
Date: Mon, 18 Feb 2008 22:41:51 +0100 [thread overview]
Message-ID: <1203370911.2394.1237549879@webmail.messagingengine.com> (raw)
In-Reply-To: <200802182228.50631.Martin@lichtvoll.de>
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. :-)
--
Dipl.-Phys. Felix E. Klee
Naunynstr. 2, 76530 Baden-Baden, Germany
Tel.: +49 7221 396961, Fax: +49 7221 396960, Mobile: +49 174 1386060
http://www.linkedin.com/in/feklee
next prev parent reply other threads:[~2008-02-18 21:41 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 [this message]
2008-02-18 21:49 ` Martin Steigerwald
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=1203370911.2394.1237549879@webmail.messagingengine.com \
--to=felix.klee@inka.de \
--cc=Martin@lichtvoll.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