It's not configurable, it's not even a filer-specific thing. Those .nfs files are being created because some other process out there is currently accessing the file that you asked to be deleted. That's what causes .nfs files. It's part of the NFS spec to do so. If they are still around after the client is no longer accessing the file, then the client did not delete them which again, according to the spec, it the client's responsibility. At that point, you can delete them manually.
Check out the following NTAP Knowledge Base article for more details:
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=ntapcs1105&resou...
Hope this helps.
-- Adam Fox NetApp Professional Services, NC adamfox@netapp.com
-----Original Message----- From: John Sambrook [mailto:john_sambrook@yahoo.com] Sent: Tuesday, July 24, 2001 3:57 PM To: toasters@mathworks.com Subject: .nfsXXXX files cause ClearCase remove commands to fail ...
We have a couple of Sun servers running ClearCase version 4.2, patch level 3, with a NetApp F740 filer providing VOB and view storage. We host VOB databases on the filer as well, not just pools.
When we attempt to delete a VOB, using the ClearCase "rmvob" command, the command fails. Upon investigation, it appears that the filer is creating .nfsXXXX files, corresponding to files that were open at the time they were deleted.
I'd like to know if others have encountered this problem, and if so what they did to resolve it. Perhaps the creation of these files is configurable?
Thanks for any advice.
John Sambrook
Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/