From: Edward Hibbert Subject: Linux client, SNAP filer, ESTALE Date: Wed, 28 May 2003 14:42:57 +0100 Sender: nfs-admin@lists.sourceforge.net Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Return-path: Received: from smtp2.dataconnection.com ([192.91.191.8] helo=miles.dataconnection.com) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 19L1Cw-00052P-00 for ; Wed, 28 May 2003 06:43:11 -0700 To: "'nfs@lists.sourceforge.net'" Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: I have an ESTALE problem. That probably means it's been discussed to death, but after browsing the archive I'm not much the wiser, so... Here's the scenario: * RH 7.2 running a 2.4.18 kernel * Linux boxes acting as NFS clients to a SNAP filer. * Mount options rw,noac,rsize=4096,wsize=4096,hard,intr,bg We had a power outage on the filer; the clients stayed up. The clients returned stale errors, even once the filer had come back up, until we unmounted and remounted all the mount points. Is this behaviour as expected, a known problem, an unknown problem, or too sloppily described to be able to tell? Regards, Edward Hibbert Internet Applications Group Data Connection Ltd Tel: +44 131 662 1212 Fax: +44 131 662 1345 Email: eh@dataconnection.com Web: http://www.dataconnection.com ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs