Re: nfs locking problem?

[Bill Hawes]

Gerd Knorr wrote:
> While reading & writing mail using pine, the kernel (2.1.70) prints these
> messages:
> 
> nfs_safe_remove: //kraxel.lock.881160387.3674.bogomips inode busy?? i_count=2
> nfs_safe_remove: Mail/sent-mail.lock.881161174.3674.bogomips inode busy?? i_count=2
> nfs_safe_remove: //kraxel.lock.881161175.3674.bogomips inode busy?? i_count=2
> 
> Both /home and /var/spool/mail are mounted via NFS. Server is linux
> 2.0.31pre10 with the userland NFS server (2.2beta29).

Hi Gerd,
I haven't yet tracked down all of the conditions leading to busy inodes,
so I'm not sure whether the above is a problem or not.

If the removed file has a hard link, all is safe, but if the inode is
somehow busy even though the dentry count is 1, then there could be a
problem. I'll take a look at the locking code and see if that provides a
clue.

Regards,
Bill