Filesystem full with .nfs files

[Anish Xavier]

Hi all,
We hve a two node Service guard cluster with HANFS configured in cross mount way.

Now the problem is file system is getting full because of .nfs files creating after a clent to server application acess.

Is there any way to solve this issue other than removing these files manually.

Regrds

Anish

[Steven E. Protter]

Shalom Anish,

If you have time, you could use a find command with +mtime to get the old ones and rm -f them.

This depends on if you have lots of old files lying around or the situation is crtical.

A cron based general delete would also probably work, as files with a file handle would remain and stay locked. There would be errors from this approach.

SEP

[Anish Xavier]

Hi all

Is there any way other than deleting these files.

[A. Clay Stephenson]

Sure, simply execute the following:

cd /
rm -r *

After that, I assure you that you will never see those files again (nor any other files because you just clobbered your system).

There are no magic bullets because what was created using mistakes, ignorance, and/or stupidity requires intelligence to safely undo.

You probably need to unmount your NFS filesystems, correct any cross mount links, fix your automount maps (if applicable), remove files, and then remount your NFS directories/filesystems.

[Dennis Handly]

These .nfs files are typically created when the file is removed on the server but still used on the client. Does this sound like your case?

If the file is still in use, the rm .nfs would just create another .nfs file.

[sumit_jain]

Hi Dennis,
Is there a way out to suppress NFS alerts in OVO, because template pushed on servers having NFS
OSSPI-AIX-FilesystemMsg_4 is not able to suppress NFS alerts .

Is there a way out as NFS is pushed on many servers and we get numorous alerts rather than one.

Thanks,
Sumit

[Dave Olker]

Hi Sumit,

I think you'd be better served by starting a new thread with your question rather than asking an off-topic question at the end of an existing thread.

Dave

[anandganjihal]

Just to clarify:

>> These .nfs files are typically created when the file is removed on the server but still used on the client. Toes this sound like your case?

.nfsxxx files will be created only when client-1 is using a file and the same file is removed on the same client-1 by another user/window.

If some body removes file on NFS server /or by another client-2 then client-1 will see stale file handle message instead of .nfsxxx file.

>> If the file is still in use, the rm .nfs would just create another .nfs file.

NOP, it doesn't create new .nfs file. Its same as another client or server removing a file. Client which is using the file will get stale file handle.