[Samba] IO report error when use samba in HA

jie wang yjxxtd12 at gmail.com
Thu Nov 3 12:08:26 UTC 2022

Thanks the reply, I set network.ping.timeout to 10, but it does not
work. Following are my volume's parameters, did I need to change other
parameter ?

gluster> volume info
Volume Name: tank
Type: Distribute
Volume ID: 6ab518a2-08c1-4456-af1b-31a47926d246
Status: Started
Snapshot Count: 0
Number of Bricks: 3
Transport-type: tcp
Options Reconfigured:
network.ping-timeout: 10
performance.write-behind: off
transport.address-family: inet
performance.readdir-ahead: on
nfs.disable: on

On Thu, Nov 3, 2022 at 7:29 PM Stefan Kania via samba
<samba at lists.samba.org> wrote:
> 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.
> >
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

More information about the samba mailing list