Edward P Rosenbloom wrote:
>
> I have upgraded to OpenAFS Client 1.5.15, and set the Cache to 800MB. I
> did fs setcrypt off. Still got errors.
> Here are some things from the Event Viewer:
>
> {Delayed Write Failed} Windows was unable to save all the data for the
> file \Device\LanmanRedirector. The data has been lost. This error may be
> caused by a failure of your computer hardware or network connection.
> Please try to save this file elsewhere.
>
> Application popup: Windows - Delayed Write Failed : Windows was unable
> to save all the data for the file
> \\afs\PDE\project\pde\common\scratch\rgpfs32trule.epr\src\clone_good\windows\out\debug_win32\proj\mmfs\vc80.pdb.
> The data has been lost. This error may be caused by a failure of your
> computer hardware or network connection. Please try to save this file
> elsewhere.
>
> Any other tuning suggestions? Is there an AFS log kept someplace?Read the release notes. The debugging section describes how to use the SysInternals system monitors (FileMon and DbgView) in conjunction with OAFW's trace logging output to identify the source of errors. Delayed Write errors are the result of the Windows CIFS client breaking the connection to the AFS Client Service because it believes the AFS client service is taking too long to respond. The CIFS client's timeout is computed dynamically. This can be a problem for AFS because reads take place very quickly compared to writes since read data does not involve network traffic. Jeffrey Altman Secure Endpoints Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
