Skip to contentSkip to conversation

RPC request reserved 0 but used 96

DISCUSSION Jens Axboe 1 participant 4 messages May 15, 2004 – May 18, 2004 1 message not in the archive

lore
Share & tools
lore

Jens Axboe

author
#0 lore raw

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.

Signature · 1 line
Jens Axboe
author
#1 lore raw
Quoted 12 lines · Jens Axboe

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

Quoted 2 lines

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.

Signature · 1 line
Jens Axboe
author
#2 lore raw
Quoted 33 lines · Jens Axboe
Quoted 12 lines · Jens Axboe

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

Quoted 2 lines

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

Quoted 5 lines

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.

Signature · 1 line
Jens Axboe

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#4 lore raw
Quoted 20 lines · J. Bruce Fields
Quoted 5 lines · Jens Axboe

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

Does this end the messages?

--Bruce Fields

svc_recv may call svc_sock_release before rqstp->rq_res is initialized.

 net/sunrpc/svcsock.c |    1 +
 1 files changed, 1 insertion(+)

diff -puN net/sunrpc/svcsock.c~svc_reserve_debugging net/sunrpc/svcsock.c

net/sunrpc/svcsock.c svc_recv(struct svc_serv *serv, struct s · line 1261

Quoted 7 lines
net/sunrpc/svcsock.c renamed from net/sunrpc/svcsock.c~svc_reserve_debugging +1 -0
@@ -1255,6 +1255,7 @@ svc_recv(struct svc_serv *serv, struct s
 
 	/* No data, incomplete (TCP) read, or accept() */
 	if (len == 0 || len == -EAGAIN) {
+		rqstp->rq_res.len = 0;
 		svc_sock_release(rqstp);
 		return -EAGAIN;
 	}

Seems to have fixed it, at least I haven't seen any messages of this sort since applying the patch and switching back to nfs over tcp. Thanks!

Signature · 1 line
Jens Axboe