Dear AFS Community, I am preparing a presentation about AFS for our Computer Science Department at UNC. We are running AFS v3.2. Some concerns were raised about the write on close mechanism of the cache manager. I have read several articles, including the "AFS-3 Programmer's Reference: File Server/Cache Manager Interface". I believe I can state fairly succintly what happens when an AFS File Server crashes and a file is open for write access on a Client. My question is: "What happens to a file open for Write on a Client Workstation if the Client Workstation crashes?" My understanding is that the dirty buffers on the Client Workstation are written to the file server on file close. If the file is not closed but the edits have been stored on the Cache Manager disk space, does the File Server and Cache Manager attempt to close the file when the Client Machine reboots, or all edits since last close simply lost? I take it from the 5 minute timeout on locks, that a Client machine crash definitely breaks any lock the Cache Manager might have had on a file if the Cache Manager is not operational within 5 minutes. Sincerely, David Stahl -- [EMAIL PROTECTED] Facilities Group Computer Science Departement University of North Carolina, Chapel Hill NC
