Subject: RENAME

From: "G. Allen Morris III" <[email-masked]>
Date: Wed, 22 Sep 1999 10:30:50 -0700

I don't understand why RENAME returns NFS4ERR_MLINK if it does
a "unlink/link/unlink" sequence for a rename.  I would think that
this should be a filesystem attribute.

I would like to add a mechanism that would inform clients that
filehandles go stale after a rename.

The client could then update any openfiles that it renamed with:

    PUTFH  (source dir)
	RENAME "a" (dest dir) "b"
	SAVEFH
	PUTFH  (dest dir)
	LOOKUPFH "b" ("a"'s filehandle)	 # a new operation
	GETFH
	RESTOREFH

Then we could get rid of this paragraph:

	A file handle may or may not become stale on a rename.  However,
	server implementors are strongly encouraged to attempt to keep file
	handles from becoming stale in this fashion.

--
Allen Morris <[email-masked]>