From: Trond Myklebust Subject: Re: nfs exporting my stacked fs Date: 31 May 2003 01:10:09 +0200 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Sharp , linux-fsdevel@vger.kernel.org Return-path: Received: from pat.uio.no ([129.240.130.16]:62111 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S264025AbTE3W5A (ORCPT ); Fri, 30 May 2003 18:57:00 -0400 To: Bryan Henderson In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org >>>>> " " == Bryan Henderson writes: > This is true in any instant, but for most NFS purposes, we also > care about identifying a file uniquely over time, even when > that time might involve sea changes such as a reboot. E.g. one > would like to make sure that a file handle that referred to > file A an hour ago still refers to file A now. According to RFC1813 (which clarifies common practices for RFC1094) file handles are *unique*. More specifically: "If two file handles from the same server are equal, they must refer to the same file, but if they are not equal, no conclusions can be drawn." RFC1813 makes no exceptions to this rule. Including for time.... The one thing that is allowed, is that the server may revoke a filehandle if (and only if) the file no longer exists, or if access to the file has been revoked. IOW: the condition you describe above is trivially observed... Cheers, Trond