Re: Howto switch off ext4's delayed allocation?

[Theodore Tso <tytso@mit.edu>]

On Wed, Sep 16, 2009 at 08:32:12AM -0400, Clemens Eisserer wrote:
> 
> Just happend again to me.
> After the intel driver crashed my system, the source-file I was
> working on was empty. Fourtunatly eclipse has a history-log.

Sounds like eclipse is broken; most Unix editors (emacs, vim, etc.) do
correctly use fsync() when writing precious files, such people's
source files.  In addition, it must be writing the data through a
decidedly non-standard way.  Is it out-and-out deleting the file
before writing the new version of the file, or something insane like
that?  Ext4's hueristics are designed so that for the most common ways
that applications update files, the data gets forced to disk.  It
sounds like Eclipse is doing something decidedly non-standard.

If you can run a strace on eclipse while and then arrange to edit an
existing file and save it, it would be interesting to see what the
heck it is doing.

> Isn't there a way to switch off the more "dangerous" optimizations in ext4?

The mount option nodelalloc will turn off delayed allocation.  This is
documented in Documentation/filesystems/ext4.txt.

					- Ted