Re: ext4: journal has aborted

[Theodore Ts'o <tytso@mit.edu>]

I've been auditing the ext4 code looking for a potential bug in our
journalling code that might result in fs corruption after a
crash/power failure.

I did find one such instance: http://patchwork.ozlabs.org/patch/367346/

However, I'm fairly sure this is not the cause of most of the problems
folks have been complaining about.  For one thing, this bug has been
around for a long, long time (since v3.5 or so).  For another, hitting
it is incredibly rare.

It would only be noticeable if you crash immediately (within 5 seconds
or so) after allocating the first inode in a block group where both
the inode allocation bitmap and block allocation bitmap are
uninitialized (i.e, no inodes or blocks have ever been allocated from
that block group since the file system was first initialized).

So for people who are indicating that they are seeing problems much
more frequently in 3.15, but not in older kernels, it's almost
certainly something else going on.  But if you can reliably reproduce
the problem, you might want to try applying the patch.  It certainly
won't hurt, and if it does help, please let me know.  :-)

Cheers,

						- Ted