On Tue, 22 Feb 2011, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > Unfortunately, I omitted the argument, and that's what's confusing you. That's what I was afraid of. Fortunately we know where to look now. It seems that the problem is really in the lazy init code in ext4. It is possible that due some locking problem we might be zeroing existing inode. Did you tried to run fsck on that filesystem after the crash ? Thanks! -Lukas -- 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
