I stand corrected:
Stephen Harris <firstname.lastname@example.org> wrote:
It truely isn't needed.
With normal file system semantics (ie a local UFS disk), if you delete a
file that is open, then the filename is deleted, but the file itself
fully removed until all "opens" are closed on the file. With NFS you
do that, so the renaming to .nfsXXX is a close approximation. When all
processes have closed the file it _is_ unneeded (on the local disk the
file would be finally removed), but there is no way for the server to
know this, so we cheat and assume that any .nfsXXX file over 7 days old
is unused :-)
Joe Pruett <email@example.com> wrote:
those files only exist in a very specific circumstance. when a remote
system (one that has the file system mounted via nfs) has the file open
and that same system unlinks the file. the client knows that it still
needs the data, but the name is supposed to go away so it renames it to
the .nfsxxx file. when the process that has the file open exits, the
remote system should then remove the .nfsxxx file. but if that system
crashes, then the file won't go away. if some other system deletes the
file while a system has it open, then the original client will get an
error when it tries to read the file again.
so generally, if those files are old then no one really cares about
but you could have a long lived process that is working on a "deleted"
Thank you for the corrections.
Home Account Network Inc.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:15 CDT