Messages in this thread | | | Date | Sat, 15 May 2004 12:36:51 +0200 | From | Jens Axboe <> | Subject | Re: RPC request reserved 0 but used 96 |
| |
On Sat, May 15 2004, Jens Axboe wrote: > On Sat, May 15 2004, Jens Axboe wrote: > > Hi, > > > > Seeing lots of these on a small server that hosts nfs shares (root and > > "normal"). > > > > router:~ # dmesg | tail -n5 > > RPC request reserved 0 but used 96 > > RPC request reserved 0 but used 96 > > RPC request reserved 0 but used 140 > > RPC request reserved 0 but used 140 > > RPC request reserved 0 but used 96 > > > > I see nfs stalls on the client, doesn't seem to be directly related to > > when the above messages happen. > > This went out a little early, lots of pieces missing. > > The server is running 2.6.6-mm2, NFS options are as follows: > > CONFIG_NFS_FS=y > CONFIG_NFS_V3=y > # CONFIG_NFS_V4 is not set > CONFIG_NFS_DIRECTIO=y > CONFIG_NFSD=y > CONFIG_NFSD_V3=y > # CONFIG_NFSD_V4 is not set > CONFIG_NFSD_TCP=y > CONFIG_LOCKD=y > CONFIG_LOCKD_V4=y > CONFIG_EXPORTFS=y > CONFIG_SUNRPC=y > > The shares are exported async. > > Client is running 2.4.26, mount options are nfsvers=3,tcp. > > I'll be trying 2.6.6-BK on the server now.
2.6.6-BK with shares exported sync show the same behaviour. I get:
RPC request reserved 0 but used 32900 RPC request reserved 0 but used 32900 RPC request reserved 0 but used 96
and client stalls with a:
nfs: server router not responding, still trying nfs: server router OK
at that time.
-- Jens Axboe
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |