search for: zhiye

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

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...

I know "hard" means command will hang if network is broken. But it seems that's not actuate. It's CPU that will hang. Affected scope: I tested it against CentOS 5/6/7, it can be reproduced on all the systems. the debug logs below are captured from CentOS 7 (cifs.ko v2.05) How to reproduce this problem? 1. mount a cifs share with option "hard" 2. stop samba

> This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3294209241_521622 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have been unable to find any discussion regarding this issue, but I have been able to reproduce it on two different machines. Both computer are Macs running