home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!ames!haven.umd.edu!umd5!oberon.umd.edu!matthews
- From: matthews@oberon.umd.edu (Mike Matthews)
- Newsgroups: comp.sys.next.misc
- Subject: Re: .nfs*** files getting left all over
- Message-ID: <17932@umd5.umd.edu>
- Date: 13 Jan 93 01:49:39 GMT
- References: <7325@ucsbcsl.ucsb.edu>
- Sender: news@umd5.umd.edu
- Organization: Los Alamos National Laboratory, NM
- Lines: 32
-
- In article <7325@ucsbcsl.ucsb.edu> doug@foxtrot.ccmrc.ucsb.edu (Douglas Scott) writes:
- >I am finding lots of files named .nfs*** (usually *** = numbers) left around
- >on our filesystem. They seem to be created when using <command>-r to delete
- >files that are on remote filesystems, and I am not sure, but it appears that
- >they do not clear up on their own.
-
- .nfs* files are the result of the NFS client not letting go of a file on the
- NFS server that the server deletes. From the nfsd man pages:
-
- When a file that is opened by a client is unlinked (by the
- server), a file with a name of the form .nfsXXX (where XXX
- is a number) is created by the client. When the open file
- is closed, the .nfsXXX file is removed. If the client
- crashes before the file can be closed, the .nfsXXX file is
- not removed.
-
- I've noticed it happens quite a few times too. Maybe 3.0 isn't closing all
- the files it should?
-
- >Thanks!
-
- >Douglas Scott
-
- It could be if you wait a bit the client will close the file and the .nfs*
- file will be deleted, but I'm too impatient to notice.
- ------
- Mike Matthews, matthews@oberon.umd.edu (NeXTmail accepted)
- ------
- "I prefer the blunted cudgels of the followers of the Serpent God."
- -- Sean Doran the Younger
-
-
-