similar to: How to disable CTDB pulling up NICs

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

hi Michael： We want to implement the ‘persistent handle’ function under Windows 7(SMB 2.1), which has only local ‘durable handle’. For now my plan is just to synchronize the following files between cluster nodes: smbXsrv_open_global.tdb.0 smbXsrv_session_global.tdb.0 smbXsrv_tcon_global.tdb.0 locking.tdb.0 It probably won’t be completed, so I’m writing to ask for your advice. Any help would be

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

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

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

Hi, I have another question, when I do the blockcommit command and get the result " Top image as the active layer is currently unsupported ", is it being developed? root@cvk-31:/vms/images# virsh blockcommit Vmtest /vms/images/Vmtest1;echo $? error: internal error unable to execute QEMU command 'block-commit': Top image as the active layer is currently unsupported 1 But as I

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

Hi folks I face a problem when using the samba share, Here is the detail: 1) Phenomenon In windows 7, sometimes, I type the samba server ip address and can see the shared folder. (the samba version is 4.3.11) a、However when I try to open the shared folder, it fails with a windows error message like “please check the spelling of the name, or some problem may related to the network”, and

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

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,

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 Jeremy Sorry to disturb you. I notice that at several months ago, you offered a patch about the frontend SMB support for the CA feature at mailing list(as shown below). Thanks for your help and thanks for the generosity of Simplivity. It benefits me a lot. Then, up to now, 1) Are there any updated versions about this frontend patch? 2) Are there any patches about

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

I had test the command virsh blockcommit, but it failed, with the libvirt version 1.1.0, and qemu version 1.6.0. Is this feature being developing? Thanks root at cvk-31:/vms/images# virsh -v 1.1.0 root at cvk-31:/vms/images# qemu-img -V qemu-img version 1.6.0, Copyright (c) 2004-2008 Fabrice Bellard usage: qemu-img command [command options] root at cvk-31:/vms/images# virsh blockcommit Vmtest

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

Hi all: Thanks for your attention. I have a question about nss_wrapper library. I want to get user and group information from my own passwd and group files in samba 4.3.9. So I use the package 'nss_wrapper'.Firstly,I install the nss_wrapper library;Secondly, I use the function setenv() to set LD_PRELOAD=libnss_wrapper.so, NSS_WRAPPER_PASSWD = passwd and

Hi all: Thanks for your attention. I have a question about smb.conf. I want add ‘everyone’ to write list of a share, but ‘ALL’ and ‘everyone’ doesn’t work, I want to know how to add everyone to write list ? thanks ________________________________ fengwei 11322 (RD) -------------------------------------------------------------------------------------------------------------------------------------

Hi samba-team, I met a problem recently: Problem Description: The connection would be broken when read rate is too big. Environment: Samba 4.3.11 Ubuntu server 14.04 Configuration: usershare allow guests = yes max protocol = SMB3 large readwrite = yes use sendfile = yes aio read size = 1024 oplocks = yes deadtime = 10 aio write behind = true clustering = yes store dos