Yep. This is consistent with what I observe.
What I have also found is that if I kill ClearCase's vob server process by hand ('ps -elf | grep vob' then kill -15 <pid>') then there are no open files in the vob (storage dir) to be deleted, and the ClearCase "rmvob" command works fine.
Note that I am unmounting the VOB before rmvob'ing it, but not manually finding and kill the vob server process. The ClearCase 'rmview' command doesn't seem to suffer from this problem, so perhaps it does an "endview" command internally as part of deleting a view.
At any rate, the problem is clearly a ClearCase issue, and not a problem with the filer. We are really happy with the filer and the support from NetApp, BTW.
Thanks for the help.
John Sambrook --- "Fox, Adam" Adam.Fox@netapp.com wrote:
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/
__________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/