🚀 go-pugleaf

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.
> 

I have this line in my daily script file:

# Clean out old .nfs files.
find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune

I know I didn't put it there, so I assume it came with the system.  This  
command will search the entire file system for any and all .nfs*** files  
which have been modified in the past week and remove them.

X

--
\\  /    Who:   Toby Paterson
 \\/     How:   tpaterso@cs.ubc.ca, paterson@gdss.commerce.ubc.ca
 //\     What:  Grunt and NeXT hacker; GDSS Fellowship
//  \    Where: University of British Columbia

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.
>
>I found that I needed to cmd-r the files, and then cmd-r the .nfs files as
>well!
>
>This is definitely new to 3.0 -- anyone have an explanation or suggestion for
>this?  I assume it is some nfs weirdness.
>

That's a UNIXism, and it can be an extremely bad things to remove. I
found out the hard way before I knew what they were, and my system
crashed. The .nfs* files are create when some program has an open
reference to a file. If you try to remove that file, but something is
still accessing it, a .nfs* file is created so that they other process
doesn't loose information it needs. 

These will be cleaned up by cron on a nightly basis, usually around 2
am. Since it's done so late at night, the risk of a system crash due to
removing an important one is minimized. 

Alex
--
______________________________________________________
    Internet: alex@data.acs.calpoly.edu (NeXT mail)
              alex@cosmos.acs.calpoly.edu

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