[Samba] IO report error when use samba in HA
stefan at kania-online.de
Thu Nov 3 11:09:19 UTC 2022
Did you configure the right parameters for your GlusterFS to fully
support Samba? Did you change the network.ping.timeout from Gluster? The
default value is 42 seconds and it's much to long for Windows-Clients
you should have no more then 20 seconds set if you use Gluster with Windows.
Am 03.11.22 um 02:17 schrieb jie wang via samba:
> Hi all,
> I use two samba server1 + glusterfs + ctdb to build a high availability
> environment, and use windows client to visit the samba server. First,
> windows client connect to samba server1, and I execute a copy command
> in client which cost a long time. Then I kill samba server1, and
> windows client reconnect to samba server2, but the copy command break
> and report error. But the strange thing is, if I use linux client, the
> copy command will not break, in the period of reconnect.
> So how can I make the windows client not break the copy command, in
> the period of reconnect ? Thanks a lot.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 203 bytes
Desc: OpenPGP digital signature
More information about the samba