[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201005060418.o464IxOB012196@demeter.kernel.org>
Date: Thu, 6 May 2010 04:18:59 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 15910] zero-length files and performance degradation
https://bugzilla.kernel.org/show_bug.cgi?id=15910
Eric Sandeen <sandeen@...hat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@...hat.com
--- Comment #3 from Eric Sandeen <sandeen@...hat.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@....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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists