Re: NFS problems in 2.1.63

Bill Hawes (whawes@star.net)
Sat, 15 Nov 1997 18:08:03 -0500

Alan Cox wrote:
> IP: queue_glue: no memory for gluing queue c0895560
> nfs_revalidate_inode: getattr failed, error=-5
> nfs_revalidate_inode: getattr failed, error=-5
> IP: queue_glue: no memory for gluing queue c0342800
> nfs_revalidate_inode: getattr failed, error=-5
> IP: queue_glue: no memory for gluing queue c1795360
> nfs_revalidate_inode: getattr failed, error=-5
> nfs_revalidate_inode: getattr failed, error=-5
> nfs: server lightning OK

Revalidation failures are bad news, as generally the inode becomes
unusable. It's possible that we might be able to work out a way to
ignore some failures if they were likely to be transient. (I.e., we
can't update our inode now, but maybe it's still OK to use.)

> NFS: page unused while waiting
> NFS: inode 876862182 had 1 failed requests
> NFS: page unused while waiting
> NFS: page unused while waiting

The "page unused" and "failed requests" messages are actually good news,
as it means that former memory leaks have been detected and avoided :-)

Regards,
Bill