From: Pavel Machek <pavel@ucw.cz>
To: Theodore Tso <tytso@mit.edu>, Andi Kleen <andi@firstfloor.org>,
Frans Pop <elendil@planet.nl>,
Chris Mason <chris.mason@oracle.com>,
jack@suse.cz, linux-kernel@vger.kernel.org, linux-
Subject: Re: What happened to data=guarded?
Date: Mon, 10 Aug 2009 18:42:05 +0200 [thread overview]
Message-ID: <20090810164205.GC1505@ucw.cz> (raw)
In-Reply-To: <20090811185703.GQ1756@mit.edu>
On Tue 2009-08-11 14:57:03, Theodore Tso wrote:
> On Tue, Aug 11, 2009 at 05:29:14PM +0200, Andi Kleen wrote:
> > > Good to hear. I've so far stayed with data=ordered as I think I'd prefer
> > > data=guarded over data=writeback. I'll certainly give it a try when it's
> > > available.
> >
> > Same here. data=writeback already cost me a few files after crashes here :/
>
> What sort of files were you losing? I don't know if we can improve
> the implied flush hueristics, but we should at least try to see if we
> do something about it.
IIRC... the flush heuristics invoke async flush, so you can still lose
data if you are unlucky, no?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-08-11 21:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 20:03 [PATCH, RFC] ext3: Update Kconfig description of EXT3_DEFAULTS_TO_ORDERED Theodore Ts'o
2009-08-10 20:28 ` Jan Kara
2009-08-10 20:55 ` Ric Wheeler
2009-08-11 3:49 ` Al Boldi
2009-08-11 9:33 ` Jan Kara
2009-08-11 11:41 ` Al Boldi
2009-08-11 13:35 ` What happened to data=guarded? (was: ext3: Update Kconfig description of EXT3_DEFAULTS_TO_ORDERED) Frans Pop
2009-08-11 13:37 ` Chris Mason
2009-08-11 14:54 ` What happened to data=guarded? Frans Pop
2009-08-11 15:29 ` Andi Kleen
2009-08-11 15:34 ` Jan Kara
2009-08-11 18:04 ` Eric Sandeen
2009-08-11 18:57 ` Theodore Tso
2009-08-10 16:42 ` Pavel Machek [this message]
2009-08-12 20:37 ` Jan Kara
2009-08-11 19:09 ` Andi Kleen
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=20090810164205.GC1505@ucw.cz \
--to=pavel@ucw.cz \
--cc=andi@firstfloor.org \
--cc=chris.mason@oracle.com \
--cc=elendil@planet.nl \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).