From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: FYI: KDE reintroduces KDE_EXTRA_FSYNC
Date: Sat, 11 Apr 2009 21:42:43 -0500 [thread overview]
Message-ID: <49E15523.1080401@redhat.com> (raw)
Just FYI for the ext4 folks:
http://websvn.kde.org/branches/KDE/4.2/kdelibs/kdecore/io/ksavefile.cpp?r1=949036&r2=949054&pathrev=949054
---
re-introduce KDE_EXTRA_FSYNC for the poor XFS/Ext4/... users
setting this env variable to anything (before kde starts!) will avoid
getting those pesky 0-byte sized files after system crashes - at a
potentially non-trivial performance cost.
BUG: 187172
---
-Eric
reply other threads:[~2009-04-12 2:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49E15523.1080401@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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.