[prev in list] [next in list] [prev in thread] [next in thread] 

List:       samba
Subject:    Re: [Samba] How to avoid CIFS timeout?
From:       "Wang, Zhiye via samba" <samba () lists ! samba ! org>
Date:       2016-12-25 12:23:07
Message-ID: CY4PR10MB159138DAAE006362137671E0E4970 () CY4PR10MB1591 ! namprd10 ! prod ! outlook ! com
[Download RAW message or body]

This is not about CIFS performance. It's actually the underlying storage cannot \
response in time sometimes. Improving underlying storage performance is out of my \
control.

On the other hand, I wonder if this option "async smb echo handler" really work at \
all. It seems the echo handler process has no network connection with client, instead \
of, it gets request from a pipe linked to the FS service process. So, if FS service \
process gets hang on open/read/write/close, the echo handler process has no chance to \
serve echo request from client. Is that true?

Another point, it seems smbd is a single thread application (as of 4.x). Is there a \
multithread version?


Thanks
Mike


________________________________
发件人: Xiaoli Feng <xifeng@redhat.com>
发送时间: 2016年12月23日 14:02
收件人: Wang, Zhiye
抄送: samba@lists.samba.org
主题: Re: [Samba] How to avoid CIFS timeout?

Hello Zhiye,

 On my opinion, you can improve the CIFS performance instead of avoiding CIFS
timeout. Such as extend read/write size and change the cache type. I don't think
enable "async smb echo handler" is a good choice for your situation. This option
will depress performance.


----- Original Message -----
> From: "Zhiye via samba Wang" <samba@lists.samba.org>
> To: samba@lists.samba.org
> Sent: Wednesday, December 21, 2016 5:55:11 PM
> Subject: [Samba] How to avoid CIFS timeout?
> 
> Dear all,
> 
> My storage could be very slow for open/read/write sometimes (not always). To
> avoid CIFS timeout (Linux), I configure samba server "async smb echo handler
> = yes".
> 
> On server side, I can see two smbd processes are generated for every CIFS
> client, and one of them is for echo server.
> 
> On client side, I confirm CIFS 1.0 is used (and "hard" option is also used).
> 
> But I can still observed the following logs on client side:
> 
> CIFS VFS: Server 10.57.33.134 has not responded in 120 seconds.
> Reconnecting...
> 
> 
> My samba server version 4.2.10.
> 
> Can anyone suggest me how to avoid CIFS client timeout? (echo_interval is not
> good as most of existing Linux distributions today do not support it)
> 
> 
> Thanks
> Mike
> 
> 
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
samba list: member options login page<https://lists.samba.org/mailman/options/samba>
lists.samba.org
Unsubscribe: By clicking on the Unsubscribe button, a confirmation message will be \
emailed to you. This message will have a link that you should click on to ...



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[prev in list] [next in list] [prev in thread] [next in thread]