Locking, notify collisions using CTDB on non-clustered share?

Volker Lendecke Volker.Lendecke at SerNet.DE
Fri Apr 13 10:02:45 UTC 2018

Hi, Chris!

On Thu, Apr 12, 2018 at 11:53:30PM -0500, Christopher R. Hertel via samba-technical wrote:
> I did some digging in Bugzilla but came up empty.  I'm wondering if this is
> a known issue:
> - I have a clustered file system.
> - I have Samba running on <n> nodes of the cluster.
> - I have one share on each of the <n> nodes that points to an EXT4
>   filesystem.
> I'm running the same smbtorture tests against the various EXT4 shares, and
> getting errors like:
> - Others that represent different forms of access collisions.
> CTDB is handling locking and other aspects shared access, so the collisions
> are probably occurring at the database level rather than the filesystem
> level.  Further precautions taken:
> - The share names differ from node to node; no duplicates.
> - The underlying pathnames also differ.  They're in the form:
>   /path/to/nodename/share
> Of course, when clustering is disabled (clustering=no) the errors are no
> longer produced.  Again, indication that the collisions are occurring at the
> DB layer.

Hmm. I think your setup needs some explanation. Why do you have ctdb
on top of separate ext4's? ctdb was initially designed to take care of
smb level locking on top of a cluster file system.

What I could imagine is that you have collisions in the inode space on
the different "nodes", and this might lead to problems.

Do you come to SambaXP? There we could have a quick chat about that :-)


SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de

More information about the samba-technical mailing list