How to avoid client timeout.(SMB2 ECHO Request)
sandeepnagamalli at gmail.com
Fri Feb 7 00:13:00 MST 2014
@Richard: Thank you, for the reply.
Yes, sometimes in cases where box is in space-out situation, back-end
write/truncate does take more that 60 sec in our back-end.
Now in such scenarios where back-end is taking long time > 60 sec, can we
keep the samba connection alive by responding to Echo SMB2/CIFS client
Can we do this in VFS plugin reply function such as
On Thu, Feb 6, 2014 at 10:41 PM, Richard Sharpe <realrichardsharpe at gmail.com
> On Thu, Feb 6, 2014 at 10:00 PM, sandeep nag <sandeepnagamalli at gmail.com>
> > http://msdn.microsoft.com/en-us/library/cc246540.aspx
> > There is write/truncate request from the client and processing in samba
> > plugin is taking longer time(which is expected as per our VFS plugin
> > processing time).
> > The client meanwhile sends many SMB ECHO requests
> > (every 30 seconds (not sure)). However, they sit in the socket because
> > smbd
> > is now stuck and will only process the ECHOs after the truncate. Because
> > of this, I am seeing client time outs.
> > If the ECHO could be responded promptly, then the client would not time.
> > How can this be done, please guide me in implementing/coding/undertanding
> > this.
> Only you know the details of your back-end ... and I thought that it
> did write-behind.
> In any event, if your back end is taking more than sixty seconds for a
> write that is a problem, isn't it.
> Maybe you should ask Tarun.
> Richard Sharpe
More information about the samba-technical