From: Mike Jagdis Subject: Re: why do i get "Stale NFS file handle" for hours? Date: Sun, 05 Sep 2004 17:20:13 +0100 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <413B3CBD.1000304@eris-associates.co.uk> References: <1094348385.13791.119.camel@lade.trondhjem.org> <413A7119.2090709@upb.de> <1094349744.13791.128.camel@lade.trondhjem.org> <413A789C.9000501@upb.de> <1094353267.13791.156.camel@lade.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Cc: Trond Myklebust , =?ISO-8859-1?Q?Sven_K?= =?ISO-8859-1?Q?=F6hler?= , linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net Return-path: To: Tim Connors In-Reply-To: List-ID: Tim Connors wrote: > I will update one directory with rsync from one host, You mean rsync to the server and change files directly on the fs rather than through an NFS client? > and then try, a > little later on, to operate on that directory from another host. Every > now and then, from a single host only, a few files in that tree will > get stale filehandles - an ls of that directory will mostly be fine > apart from those files. They will also be fine from any other machine. Yeah, that's what happens... Clients that had the file open are liable to get ESTALE. Stale file handles stick around until unmount. As long as they're around automount will consider the mount busy and not expire it (but you can unmount manually or killall -USR1 automountd). Mike -- Mike Jagdis Web: http://www.eris-associates.co.uk Eris Associates Limited Tel: +44 7780 608 368 Reading, England Fax: +44 118 926 6974