From: Eric Sandeen <sandeen@sandeen.net>
To: Greg Banks <gnb@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: LWN article: ext4 and data loss
Date: Thu, 12 Mar 2009 11:36:20 -0500 [thread overview]
Message-ID: <49B93A04.4070405@sandeen.net> (raw)
In-Reply-To: <49B9396D.7060809@sgi.com>
Greg Banks wrote:
> Eric Sandeen wrote:
>> It's simple. Want your data safe on disk? fsync. There's not a lot
>> more to it than that. (and if fsync hurts perf too much, re-think how
>> you are storing your data)
>>
>> Filesystems can hack around some heuristics to try to make unsafe apps
>> safer, but in the end, it's the app's job to make sure a buffered write
>> hits permanent storage when it matters.
>>
>
> Stewart Smith has a highly entertaining presentation on this very topic.
>
> http://www.linux.org.au/conf/2007/talk/278.html
>
and
http://www.flamingspork.com/talks/2007/06/eat_my_data.odp
In hindsight, http://linuxmafia.com/faq/Filesystems/reiserfs.html is
entertaining, too ;)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-03-12 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 11:39 LWN article: ext4 and data loss Michael Monnerie
2009-03-12 13:09 ` Eric Sandeen
2009-03-12 14:14 ` Martin Steigerwald
2009-03-12 15:02 ` Eric Sandeen
2009-03-12 16:33 ` Greg Banks
2009-03-12 16:36 ` Eric Sandeen [this message]
2009-03-12 16:45 ` Greg Banks
2009-03-14 19:42 ` Martin Steigerwald
2009-03-14 20:02 ` Eric Sandeen
2009-03-14 20:08 ` Eric Sandeen
2009-03-14 22:03 ` Martin Steigerwald
2009-03-15 14:26 ` Peter Grandi
2009-03-14 19:43 ` Martin Steigerwald
2009-03-16 16:17 ` Michael Monnerie
2009-03-18 18:52 ` Martin Steigerwald
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=49B93A04.4070405@sandeen.net \
--to=sandeen@sandeen.net \
--cc=gnb@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 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.