On Fri, Feb 11, 2011 at 09:41:17AM -0500, Jeff Layton wrote: > > 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. Gotcha, I will grab a java dev and code review the test app. My java-fu is weak, but I think java will throw an exception on either failure, just have to make sure some dev didn't put in a wide open catch. > 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. Good to know. Thank you. -- Wayne Walker wwalker@xxxxxxxxxxxxxxxxxxxx (512) 633-8076 Senior Consultant Solid Constructs, LLC > A: Because it messes up the order in which people normally read text. > > Q: Why is top-posting such a bad thing? > > > A: Top-posting. > > > > Q: What is the most annoying thing in e-mail? -- 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
