Bizarre occurrence

Gary S. Moss VLD/VMB <moss> moss at brl.mil
Thu Jan 24 01:49:36 AEST 1991


In article <9101230417.AA05385 at nazgul.physics.mcgill.ca>, loki at NAZGUL.PHYSICS.MCGILL.CA (Loki Jorgenson Rm421) writes:
|> 	I was cleaning out a directory with a /bin/rm -r <directory>
|> command when it failed with "directory not empty".  Since this command
|> recursively cleans out directories *before* removing them, something
|> had to have appeared in mid-remove.
|> 
|> 	I looked in the directory and saw ".nfsE5E79".

|> 	I don't like this much.  Anyone seen this before?
Yes, and I don't like it much either.  I noticed it when doing a recursive
destruction of a directory hierarchy from a C program using directory access
library calls and unlink.  For some reason, I haven't noticed this happening
recently.  One thing that changed is we turned on lockd/statd; I don't know
if it is related, but if you don't have these running you should (on both
server and client machines) to avoid other problems.

-Gary



More information about the Comp.sys.sgi mailing list