Thank you for the information.
"hard" seems a good option for me. I will do more test.
As to "echo" timeout, are you referring "echo_interval"? It seems this option was implemented pretty late, and only most recent Linux distributions include its support.
Besides that, I have already configured samba server to serve "echo" request in separated process("async smb echo handler = yes", so "echo" server will not be blocked by "open/read/write" operations), but I can still see warning below on client side:
[620422.570128] CIFS VFS: Server 10.57.33.134 has not responded in 120 seconds. Reconnecting...
Do you have any suggestion on this?
Thanks
Mike
发件人: Steve French <smfrench@xxxxxxxxx>
发送时间: 2016年12月14日 1:20
收件人: Wang, Zhiye
抄送: linux-cifs@xxxxxxxxxxxxxxx
主题: Re: Access samba share which underlying storage is very slow
there is a "hard" mount option and the "echo" timeout can be adjusted on mount
On Tue, Dec 13, 2016 at 7:35 AM, Wang, Zhiye <Zhiye.Wang@xxxxxxxxxxxx> wrote:
Dear all,
I use Samba to share FUSE based file system which underlying storage is very slow sometimes (not always). Read/Write/Open sometimes may take several minutes. And especially, "write" must be in sequential manner. And "write to file" cannot break in the middle of a file (much like tape).
All that are ok for Samba, but it seems to be a problem for CIFS on client side. It seems operations timeout are all hardcoded, and cannot be adjusted during mount. After timeout, CIFS client will reconnect and then resume "write" from where is broken (but this is not acceptable for my case).
Is there a way to make CIFS client block at slow operations without timeout?
Thanks
Mike
--
Thanks,
Steve ��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
