Ben Rockwood wrote: > I have several different NFS environments, in some cases .nfs* files are a > big problem, in others its not. As I understand it, a .nfs* file is created > when a file is removed while its still got an open file handle. > > that's correct the NFS client renames a file to .nfsXXXX when the file is removed when it is still open (since the open still has a ref count on it). > Can I disable this behavior via some tunable? > > no. > What, outside of the application, could cause this to happen? are any other processes or administrative scripts removing files when the applications still have it open? > Problems in lockd/statd? I don't think so. > I have the same code running in two similar environments, one is pleaged with > .nfs files, the other is not. I have no way to explain this currently. > > Does it go/gets removed ultimately or are the files still around after the application closes? Do you know what application(s) the files could be associated with? May be a start to figure out what's happening. Is this while using NFSv3 or NFSv4?
Mahesh
