Hello Stephen,
can you reproduce this on a fresh filesystem and on a system that you
can easily update? If you can, can you update the kernel to a
stable/recent version (i.e. longterm 3.10) and e2fsprogs to a current
version, re-create a fresh file system and try to reproduce again? If
you still can, can you try to figure out which order of syscalls is
causing the corruption? Or anything else that might help to figure out
the root cause?
In general, using a rather old kernel and user space tools and pointing
to an issue isn't going to help you much.
Cheers,
Bernd
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
