NFS problems in 2.1.63

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sat, 15 Nov 97 22:19 GMT


[The first chunk of this is the result of the page colouring stuff on
any box without hundreds of megs of RAM - that I know about - what
it triggered however is more interesting]

nfs_revalidate_inode: getattr failed, error=-5
nfs_revalidate_inode: getattr failed, error=-5
IP: queue_glue: no memory for gluing queue c1ec9120
nfs_revalidate_inode: getattr failed, error=-5
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 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
NFS: page unused while waiting
NFS: inode 876862182 had 1 failed requests
NFS: page unused while waiting
NFS: page unused while waiting

Turning off the page colouring makes 2.1.63 CVS tree usable for NFS, for
larger MTU networking and for various other stuff that the page colouring
fragments memory so badly over. I'd strongly suggest we leave page colouring
OFF until after 2.2 when we can reasonably address and design to work with
the issues it raises. Right now its not terribly good news.

Alan