similar to: Any news about the patch for the CA feature?

Where is the patch?I can help to get this integrated -----邮件原件----- 发件人: Jeremy Allison [mailto:jra at samba.org] 发送时间: 2016年9月1日 7:57 收件人: Michael Adam 抄送: zhengbin 08747 (RD); weidong 12656 (RD); 'samba at lists.samba.org' 主题: Re: [Samba] status of Continuous availability in SMB3 On Wed, Aug 31, 2016 at 10:29:51AM +0200, Michael Adam via samba wrote: > On 2016-08-31 at 08:13 +0000,

Well, I have changed the line "map to guest = bad password" to "map to guest = bad user" However the problem still exists: 1) I can pass the authentication and see the shared folder, but when I try to open the folder , it fails with a windows error message like "cannot find the route to the network". It may recover to normal later (means I can open that folder) 2) I

Thank you very much for reply. Our test team insists on simulating network failure by using ifdown instead of just unpluging the cable. I have to modify the event script 10.interface. When noticing a NIC failure, CTDB just marks the NIC down and do not try to pull it up. It seems to work fine. -----邮件原件----- 发件人: Martin Schwenke [mailto:martin at meltin.net] 发送时间: 2016年9月18日 18:49 收件人: Weidong

On Wed, Aug 31, 2016 at 10:29:51AM +0200, Michael Adam via samba wrote: > On 2016-08-31 at 08:13 +0000, zhengbin.08747 at h3c.com wrote: > > When carring out the test, I have a wireshark process run. It is confirmed that protocol smb3 is used. In the tree connection phase, server's response to client claims that it does not support DFS/Continuous Availability. > > I'm

Thanks very much, Volker. I want to synchronize three tdb files(listed as below) which is relevant to the opened file: 1) brlock.tdb 2) locking.tdb 3) smbXsrv_open_global.tdb These three tdb files are used to realize the durable file handle feature. As what you have said, the performance will be affected if storing these three files in the shared storage. So can I realize the synchronization

Thanks for your response, Rowland. Sorry for the late reply. Here is my smb.conf: [global] workgroup = grouptest1 server string = %h server (Samba NAS) dns proxy = no log file = /var/log/samba/log.%m max log size = 10000 syslog = 0 panic action = /usr/share/samba/panic-action %d server role = standalone server obey pam restrictions = yes unix password sync =

hi Michael, Sorry for taking so long to reply, I just get back on vacation. Your advice is very helpful. Our purpose is no IO interrupted with Window 7 cifs client accessing the shared folder when virtual IP taken over by another node. SMB3.0 or newer protocol do meet that demand, but Window 7 cifs client only supports SMB2.1 protocol and previous versions. So we need implement a

hi Michael Adam: Thanks for you work on samba. Here I am looking for some advice and your help. I have been stuck in continuous availability of samba 4.3.9 for two weeks. Continuous availability in SMB3 is an attractive feature and I am strugling to enable it. smb.conf, ctdb.conf are attached. Cluster file system is cephfs and mount to /CephStorage client: Windows 8 Pro root at node0:~# samba

Thanks for your attention. First, use local users at samba server, and client login success. [global] workgroup = H3C ONESTOR server string = %h server (Samba NAS) dns proxy = no log file = /var/log/samba/log.%m max log size = 100000 log level = 10 syslog = 0 panic action = /usr/share/samba/panic-action %d server role = standalone server obey pam restrictions = yes

Hi folks I want to print the log in socket_wrapper.c to have a better view of the read or write socket behavior. I find that there are four debug levels: SWRAP_LOG_ERROR SWRAP_LOG_WARN SWRAP_LOG_DEBUG SWRAP_LOG_TRACE So: Where and How to set those debug levels? Where can I find the log? Or: Are there any other ways to print the log?(I

Hi folks Recently, I find that the number of the smbd connections may increase if the network is abnormal. And the repeated connections will exist for a long time (which is not accepted for me) So, I modify the following params and shorten the existing time of those repeated connections: TCP_KEEPCNT 3 TCP_KEEPIDLE 60 TCP_KEEPINTVL 15 My concern is that: Are there any

Hi folks I face a problem about the data synchronization when using the ctdb. When one ctdb node fails, other ctdb nodes may not recover the data of the failed node. I think it may be due to the fact that ctdb stores its tdb files in the local storage. So, is it fine to store the tdb files in the shared directory of the backend storage? When one node fails, other nodes may recover the data from

If eth0 holds virtual IP as its secondary IP and I bring down eth0 by command "ifdown eth0", CTDB will automatically pull eth0 up. Sometime it goes wrong. The virtual IP becomes primary IP, and origin primary IP turns into a secondary IP or just missing. If the origin primary IP is missing, I have to run "ifup eth0" though CTDB has pulled eth0 up. CTDB uses “ip link set eth0

Is the samba server a domain controller? Is this a classic domain or an Active Directory domain. If you are using a classic domain you probably want a WINS server configured. I find it works better if the primary domain controller is also the WINS server. In a classic domain, keep the "smb ports" as the default ( "smb ports = 445 139.") What is the

Hi, Thanks a lot. Use the valgrind, we found the stack of the malloc as below, so, maybe it is not memory leak. ==2796353== 36,334,440 bytes in 100,929 blocks are still reachable in loss record 774 of 774 ==2796353== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2796353== by 0x953B88F: ??? (in

HI I have a linux samba server and lists users at this server. and access the folder from the windows7 client. Now i configure a LDAP sever and let samba to use it . But I don’t want clients keeping the connection because I have changed the authentication,clinets need to re-login. So I restart smbd. and it works. Then,let clients reconnect to samba, but it report errors: Windows cannot access

On 2016-08-31 at 08:13 +0000, zhengbin.08747 at h3c.com wrote: > hi Michael Adam: > Thanks for you work on samba. Here I am looking for some advice and your help. > I have been stuck in continuous availability of samba 4.3.9 for two weeks. Continuous availability in SMB3 is an attractive feature and I am strugling to enable it. > > smb.conf, ctdb.conf are attached. Cluster file

Hi all http://linux.die.net/man/1/ctdbd. In this page, it says “This directory is local for each node and should not be stored on the shared cluster filesystem”. But why? Thanks for reply. --dbdir=<directory> This is the directory on local storage where ctdbd keeps the local copy of the TDB databases. This directory is local for each node and should not be stored on the shared cluster

Hello to everyone Durable file handles allow a connection to an SMB server to survive a short network outage. An ongoing IO will continue after the client reconnects to the same server (maybe a difference smbd process if the CTDB status is always health during the outage). When crossing nodes caused by virtual IP’s relocating, durable handles will not work apparently. CA feature in SMB3 works

Hi all: Thanks for your attention. I have a question about smbcontrol. A user has read and write access to a share and already connected to the share, then I delete the user from the write list in smb.conf and reload the config (use the command line "smbcontrol ALL reload-config" ), but it doesn't work, the user still has read and write access to the share. Doesr the command line