Re: patch for 2.1.71 nfs client

[Bill Hawes]

Michael Lausch wrote:
> I'm sorry to report this, but this patches don't seem to correct the
> errors in every case.
> 
> Log messages, home directory NFS mounted from usnfsd server on
> linux-2.0.29 (update planned, but this is our main NFS server).
> 
> Dec  6 23:01:54 loki kernel: nfs_safe_remove: mla/.Xauthority-n inode busy?? i_count=2, i_nlink=2
> Dec  6 23:01:54 loki kernel: nfs_safe_remove: mla/.Xauthority-c inode busy?? i_count=2, i_nlink=2
> 
> The previous two lines are displayed whenever i log in from xdm.

In this case there's probably no danger, as the link count shows there's
another hard link. It's OK if two different dentries have the inode in
use twice, because the server won't get rid of the inode when one of the
links is deleted. (I should probably make my warning message a little
smarter.)

> Dec  6 23:04:17 loki kernel: nfs_rename: target x/init busy, d_count=2
> 
> This one is triggered by the ddd 2.2 debugger when trying to save a
> session.

This case is still under discussion -- right now we refuse to rename if
the target or source is busy. It is causing a few compatibility
problems, though, so we'll need to make some changes at some point.

Regards,
Bill