similar to: CTDB and glusterfs

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To show what we did here the entry in /etc/fstab: knoten-01:/gv0 /glusterfs glusterfs defaults,_netdev,acl,selinux 0 0 Am 17.11.2015 um 18:22 schrieb Michael Adam: > We just analyzed the situation together, and the solution is that > in order to access security.FOOBAR xattrs on the gluster fuse > mount, you have to specify the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 13.02.2015 um 12:21 schrieb Ralph B?hme: > Hi Stefan, > > On Fri, Feb 13, 2015 at 12:02:20PM +0100, Stefan Kania wrote: >> [daten] comment = Daten im Cluster path = /glusterfs/daten/ read >> only = No kernel share modes = No >> >> >> [daten2] comment = Daten im Cluster ?ber gluster-vfs path = / > >

We just analyzed the situation together, and the solution is that in order to access security.FOOBAR xattrs on the gluster fuse mount, you have to specify the 'selinux' mount option to the glusterfs fuse mount... ...THis is necassary even if selinux is disabled. This sounds strange, but it currently is the solution. Note that the recommended way is to use the glusterfs vfs module instead

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, i try to use a glusterfs with "vfs objects = glusterfs" settings in smb.conf. But if I try to access the volume I allways getting "tree connect failed: NT_STATUS_BAD_NETWORK_NAME" If I add another Share directly inside the mountet glusterfs I can access the share und read and wirte alle the data. Here is my smb.conf: -

Hello, we are trying to configure a CTDB-Cluster with Glusterfs. We are using Samba 4.5 together with gluster 3.9. We set up a lvm2 thin-provisioned volume to use gluster-snapshots. Then we configured the first share without using shadow_copy2 and everything was working fine. Then we added the shadow_copy2 parameters, when we did a "smbclient" we got the following message: root at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I did a little change in my howto for Gluster and CTDB. Because of a bug in all debian based distributions a glusterfs filesystem will not mount during systemstart. What I did? I removed the mountpoint from /etc/fstab and created a systemd target.mount file /etc/systemd/system/glusterfs.mount. Important is, that the name of the file MUST be the same

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, here is a nother howto to set up a CTDB-Cluster together with GlusterFS. https://www.kania-online.de/wp-content/uploads/2016/10/ubuntu-cluster.tx t Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlf7ttYACgkQ2JOGcNAHDTYdWQCgsjoQa0W1G/SMYM0PeoAC6Ly0 I7gAnAzSHI+PtTEMmcdVdfV6CkFDNqCi =jsDs -----END PGP

On Fri, Feb 13, 2015 at 02:46:24PM +0100, Stefan Kania wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Am 13.02.2015 um 12:21 schrieb Ralph B?hme: > > Hi Stefan, > > > > On Fri, Feb 13, 2015 at 12:02:20PM +0100, Stefan Kania wrote: > >> [daten] comment = Daten im Cluster path = /glusterfs/daten/ read > >> only = No kernel share modes =

Hi, I have an old Fileserver which is working correct: This is the smb.conf: [global] security = ads realm = EXAMPLE.COM workgroup = example winbind refresh tickets = Yes winbind use default domain = yes template shell = /bin/bash idmap config * : range = 1000000 - 1999999 idmap config ZFD : backend = rid idmap config ZFD : range = 0 - 200000 hide dotfiles = yes server string =

Hi to all, I'm having a CTDB-Cluster with two nodes (both Ubuntu wit Sernet-packages 4.17.4). Now I want to replace one of the nodes. The first step was to bring a new node to the CTDB-Cluster. This time a Debian 11 but with the same sernet-packages (4.17.4). Adding the new node to /etc/ctdb/nodes at the end of the list. And the virtual IP to /etc/ctdb/public_addresses, also at the end

Hai, Great to hear i could help one with a gluster problem :-) And ofcourse your allowed to keep us up2date. So yes, plese, by doing that and sharing the configs it might help other people. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Benedikt Kale? via samba > Verzonden: woensdag 28 augustus 2019 17:37

yes i have, this is my share-config: [share] path = /mnt/gluster/daten/share/ public = yes writeable = yes browseable = yes inherit permissions = Yes inherit acls = Yes map acl inherit = Yes nt acl support = yes vfs objects = acl_xattr F?bio Leandro Rodrigues Cordeiro schrieb: > Hi, > > Have you tried adding the share writeable? > [share] > writeable = yes > > att, >

Hi Martin, Am 26.01.23 um 22:57 schrieb Martin Schwenke: > winbindd and smbd are only started during the CTDB startup event, so > you have to enable the event scripts before you start CTDB. > That's what I did and that's where the problem starts ;-) As soon as I enable one of the two events the cluster chrashes :-( Stefan > That hasn't changed... ? > > peace

Hi guys, I try to set up two identical installed up to date CentOS6 machines with Glusterfs/CTDB/Samba . I have set up Glusterfs and it works. I have set up CTDB from CentOS and it seems to work too. Samba is AD integrated and works mainly. The main problem is that file locking seem to not work between the machines at all. If two Win7 clients try to open an document from the same Samba server

Hi, We have a couple of RHEL7 gluster storage servers with samba/ctdb. Both have joined the domain successfully (the ctdb service was started and net ads join issued on both). A container was created by the AD admin and I specified this using createcomputer=OU when I issued the net ads command on both machines. As far as I can tell on the RHGS servers everything looks OK. However the AD admin

Hi all We did some failover/failback tests on 2 nodes��A and B�� with architecture 'glusterfs + ctdb(public address) + nfs-ganesha'�� 1st: During write, unplug the network cable of serving node A ->NFS Client took a few seconds to recover to conitinue writing. After some minutes, plug the network cable of serving node A ->NFS Client also took a few seconds to recover

Hi Martin, Thanks for reading and taking the time to reply >> ctdbd[89]: Unable to get RECORD lock on database locking.tdb for 20 seconds >> /usr/local/samba/etc/ctdb/debug_locks.sh: 142: >> /usr/local/samba/etc/ctdb/debug_locks.sh: cannot create : Directory >> nonexistent >> sh: echo: I/O error >> sh: echo: I/O error > > That's weird. The only

On 09/11/16 23:28, Martin Schwenke via samba wrote: > On Wed, 9 Nov 2016 16:05:32 +0000, lejeczek via samba > <samba at lists.samba.org> wrote: > >> an attempt to set up a cluster, I'm reading around and see >> some howto writers would say to put "private dir on the FS >> cluster" - one question I have: is this correct? necessary? > No, this is not

Hi folks, I know this topic was already discussed but unfortunately non of the suggestion's helped. My current setup, Glusterfs on ZFS, CTDB installed but running into "Permission denied" error in regards to the lock file. What did I tried/tested: - Mounting the gluster volume with option --direct-io-mode=enable - ping_pong -rw /gluster/lock/lock 3

Hi List, I set up a ctdb cluster a couple months back. Things seemed pretty solid for the first 2-3 weeks, but then I started getting reports of people not being able to access files, or some times directories. It has taken me a while to figure some stuff out, but it seems the common denominator to this happening is vacuuming timeouts for locking.tdb in the ctdb log, which might go on