I typically see this when I remove a file that is open, and it renames it to .nfs##### - For example if you have a open file on one machine, try to remove it - the nfs system will rename it to .nfs#####. Until you close the open file everytime you try to erase it will get renamed to .nfs####
My guess is that you have a file open when you do the automated `rm -rf` but the file is gone when you try it manully later on.
--Jason
On Tue, Oct 26, 1999 at 08:24:42AM +0000, Dave Atkin wrote:
Since we moved to 5.3 (actually 5.3.2R1P1) we see occasional failures in various Unix automated management procedures. I've finally traced this to the "rm -rf" command failing. On Solaris systems it fails with:
rm -rf /<filer>/x rm: Unable to remove directory /<filer>/x/y/z: File exists
On SGI systems the slightly more meaningful error message is
/<filer>/x/y/z: Directory not empty
However, just repeating the rm -rf command once more works perfectly and the directory tree has gone.
I don't think it's anything to to with CIFS file locking since some of the directories are old and have not been used for a long time. Has anyone else seen this?
Dave Atkin
Dave Atkin, Head of Technical Services Computing Service, University of York, YORK YO10 5DD Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 Email: D.Atkin@york.ac.uk