From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15910] zero-length files and performance degradation
Date: Thu, 6 May 2010 04:18:59 GMT [thread overview]
Message-ID: <201005060418.o464IxOB012196@demeter.kernel.org> (raw)
In-Reply-To: <bug-15910-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=15910
Eric Sandeen <sandeen@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@redhat.com
--- Comment #3 from Eric Sandeen <sandeen@redhat.com> 2010-05-06 04:18:57 ---
(In reply to comment #2)
> May be it is useful to introduce compat mount option which force fsync()
> internaly inside rename(). Renames is not what frequent operation so it has
> much less performance penalty as real ordered mode.
ext4 does already have allocate-on-rename heuristics, though not exactly
fsync()
if (retval == 0 && force_da_alloc)
ext4_alloc_da_blocks(old_inode);
from
commit 8750c6d5fcbd3342b3d908d157f81d345c5325a7
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Feb 23 23:05:27 2009 -0500
ext4: Automatically allocate delay allocated blocks on rename
still, more mount options doesn't seem to solve the problem to me, in the end
applications can't rely on it...
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-05-06 4:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 13:49 [Bug 15910] New: zero-length files and performance degradation bugzilla-daemon
2010-05-05 18:54 ` [Bug 15910] " bugzilla-daemon
2010-05-06 4:06 ` bugzilla-daemon
2010-05-06 4:18 ` bugzilla-daemon [this message]
2010-05-09 18:19 ` bugzilla-daemon
2010-05-10 2:56 ` tytso
2010-05-10 14:22 ` Peng Tao
2010-05-10 14:34 ` tytso
2010-05-10 3:49 ` bugzilla-daemon
2010-05-10 14:36 ` bugzilla-daemon
2010-05-10 14:52 ` bugzilla-daemon
2010-05-10 17:23 ` bugzilla-daemon
2010-05-10 22:33 ` bugzilla-daemon
2011-03-07 0:30 ` bugzilla-daemon
2011-03-09 19:09 ` bugzilla-daemon
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=201005060418.o464IxOB012196@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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.