Issue122

Title Allow clients and servers to negotiate away the .nfsjunkXXX file
Priority required Status resolved-edit-complete
Superseder Nosy List mre, spencer.shepler
Assigned To spencer.shepler Topics

Created on 2006-09-14.11:49:11 by mre, last changed 2006-10-18.19:09:59 by mre.

Messages
msg396 (view) Author: mre Date: 2006-10-18.19:09:59
Made edits in cvs.
msg363 (view) Author: mre Date: 2006-09-14.12:00:14
In NFSv3, a client that unlinks an open file renames it to
.nfsjunkXXXX. In some cases, such as removing a directory,
via rm -r, the presence of open files makes the rm fail.
If the server told the client that it can remove open regular
files without fear of the file's filehandle producing NFS4ERR_STALE,
then clients could avoid the nfsXXXX kludge.

It might be nice if we could do this for directories too, but
that would require an open operation for directories.
msg362 (view) Author: mre Date: 2006-09-14.11:52:43
I suggest adding variable length fields suffixed as:
  opaque  xxx__reserved<>
(xxx is the field prefix)
to the args and results of all new operations. 
This way, the operations can be
revised in a future minor version without replacing them.

We might decide that is too ugly to revise the operation, but this
gives us an option.
History
Date User Action Args
2006-10-18 19:10:00mresetstatus: unread -> resolved-edit-complete
assignedto: mre -> spencer.shepler
messages: + msg396
nosy: + spencer.shepler
2006-09-18 16:48:09mreset
2006-09-14 12:00:14mresetmessages: + msg363
title: New operations: add some reserved fields -> Allow clients and servers to negotiate away the .nfsjunkXXX file
2006-09-14 11:52:43mresetnosy: + mre
messages: + msg362
title: OPEN: add note that if thr session is kept in stable storage, the exclusive create logic is no longer necessary -> New operations: add some reserved fields
2006-09-14 11:49:11mrecreate