Comment 5 for bug 331082

Hi Tim - I agree that the vfs_fsync patch is the only one of much interest, but it isn't the cause of Dustin's problems. We have been working together to determine the problem and figured out that he had some non-eCryptfs files in his lower mount point. This is due to a problem where creates can fail and eCryptfs leaves a zero length file around instead of cleaning up after the failed create. The empty file doesn't have the proper eCryptfs header and the kernel module will complain and return -EIO. I've opened a bug up for this:

https://bugs.launchpad.net/ecryptfs/+bug/338826