Callback slot table overflowed
Subsystems (2)
Is this bad?
Jan 19 21:53:27 pdsi7 kernel: Callback slot table overflowed
All I can tell from the code is that xprt_alloc_bc_request() failed, and the slots are "preallocated during the backchannel setup". Is there a hard limit on these slots? Where is it set?
This shouldn't happen as the slot table size is negotiated on session establishment. Currently, the client support NFS41_BC_MIN_CALLBACKS (1) request(s)
Benny
-----Original Message-----
From: [email protected] on behalf of Jim Rees
Sent: Thu 2011-01-20 05:07
To: [email protected]
Cc: peter honeyman
Subject: Callback slot table overflowed
Is this bad?
Jan 19 21:53:27 pdsi7 kernel: Callback slot table overflowed
All I can tell from the code is that xprt_alloc_bc_request() failed, and the slots are "preallocated during the backchannel setup". Is there a hard limit on these slots? Where is it set?
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Examine the CREATE_SESSION that created the fore channel, the back channel limits are set there. Also note that since this is the back channel server setting the CREATE_SESSION backchannel attributes that the back channel client (e.g. the server) can not increase any of the limits.
-->Andy
Quoted 10 lines · Jim Rees
Is this bad?
Jan 19 21:53:27 pdsi7 kernel: Callback slot table overflowedAll I can tell from the code is that
xprt_alloc_bc_request()failed, and the slots are "preallocated during the backchannel setup". Is there a hard limit on these slots? Where is it set?
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html