kernel: nfs_safe_remove: log/aferror.log busy, d_count=2

[skt_skt]

#uname -a
Linux hostname 2.4.9-e.72enterprise #1 SMP Tue Jul 3 21:57:23 EDT 2007 i686 unknown
cat /etc/redhat-release
Red Hat Linux Advanced Server release 2.1AS (Pensacola)

"When the 2.4 NFS client does a REMOVE and gets an ENOENT back from the
server it does not remove the dentry from the d_cache. This can make it
inappropriately keep writing to an inode that has been renamed" --here is what i found after goolging.

Can any one explain better?and a fix possible.

[Ivan Ferreira]

This would mean that if a NFS clients tries to delete a file and the file does not exists, the entry in the VFS cache (dcache) which normally contains a pointer to an inode may not be cleared. This means that would be possible to keep writing information to that inode when should not.

[skt_skt]

That is similar to what i understood.

Does that impact the nfs clients?( i have the similar messages reported from three servers) or is that can be ignored?