I have been able to reproduce the problem on my system. The scenario is that the Windows CIFS client is breaking the connection while there are dozens of CIFS Write requests outstanding. The client appears to break the connection on my system when the oldest outstanding connection has been waiting for 90 seconds.
You can increase the wait period by setting this registry value to a higher value. Perhaps 120 or 180 seconds. [HKLM\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters] SessTimeout This problem is exacerbated by the fact that requests in process within the cache manager are not prioritized by age and they can be processed out of order. When there are many outstanding requests some requests end up waiting longer than is desirable. This problem will only go completely away when the CIFS interface is replaced by an IFS. Only then will there not be an arbitrary timeout applied to operations. Jeffrey Altman Jeffrey Altman wrote: > Frank: > > You are consistently receiving an "IN PAGE ERROR" unfortunately > there do not appear to be any errors occurring on the AFS CIFS > server side of the connection. The CIFS client is simply breaking the > connection at some point. > > A couple of questions: > > * what version of Word are you using? When I monitor Word 2003 SP2 > I see that most of the writing is being performed by SYSTEM and not > by WINWORD.EXE. This is because Word is using asynchronous background > writes. In your log data I see all of the data being written by > WINWORD.EXE. > > * what version of OpenAFS for Windows is this log generated with? > > The debug monitor log shows that shortly after the file monitor > logs the IN PAGE ERROR, the AFS cache manager receives a number of > TellMeAboutYourself requests from AFS File Servers. This often > indicates that there was a network failure of some kind as the > servers are responding to the establishment of a new rx connection. > If the network dropped on the machine, the Windows CIFS client would > respond by closing all of the existing connections. Perhaps that > is what you are seeing. Its not clear from the logs that anything > unusual is taking place. > > Jeffrey Altman > > > Frank Burkhardt wrote: >> Hi, >> >> On Mon, May 22, 2006 at 09:31:04AM -0400, Jeffrey Altman wrote: >>> Please generate the logs again and this time make sure that "Clock Time" >>> and "Show Milliseconds" are selected in both DbgView and FileMon prior >>> to capturing the log data. This will allow the events in one log to be >>> synchronized with the data in the other log. >> Here they are: >> >> http://fbo.no-ip.org/mail-temp/crash-debug-23052006.log >> http://fbo.no-ip.org/mail-temp/crash-filemon-23052006.log >> >> Regards, >> >> Frank >> _______________________________________________ >> OpenAFS-info mailing list >> [email protected] >> https://lists.openafs.org/mailman/listinfo/openafs-info >
smime.p7s
Description: S/MIME Cryptographic Signature
