On Fri, 11 Feb 2011 08:35:20 -0600 Wayne Walker <wwalker@xxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, Feb 11, 2011 at 06:53:18AM -0500, Jeff Layton wrote: > > On Thu, 10 Feb 2011 23:14:59 -0600 > > Wayne Walker <wwalker@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > > First, I'm not certain whether this is samba, the linux cifs driver, or > > > something else. > > > > > > He got me involved. I found no useful messages (cifs, IO, kernel mem, > > > network, or samba) in any logs on client or server anywhere near the > > > times of the file creations. > > > > Did the close() or fsync() call return an error? > > No, Jeff. Nothing in the logs and from the user space side there are > no errors. All debug levels are at the system defaults. After 12 > attempts last night I've still not reproduced. I will work with my QA > guy this morning (CST here) to see if we can reproduce. What can I do > to gather the best data for you guys? > To be clear...are you sure that the close(2) or fsync(2) syscalls did not return an error? It's a common bug for programs to ignore the return code from close(2), and that's where errors during writeback get reported. The reason I ask is that there were some issues that were fixed recently in mainline with cifs writeback. The CIFS code treated timeouts during writeback as hard errors instead of retrying them, but in those cases the client should have returned an error during fsync or close. -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
