samba.git/ctdb/doc, branch master

ctdb-doc: add section to manpage for -j/--json option

2026-02-20T01:50:20+00:00

Signed-off-by: John Mulligan 
Reviewed-by: Martin Schwenke 
Reviewed-by: Anoop C S 

Autobuild-User(master): Martin Schwenke 
Autobuild-Date(master): Fri Feb 20 01:50:20 UTC 2026 on atb-devel-224

ctdb-doc: Improve private and public network documentation

2026-02-09T11:17:41+00:00

Signed-off-by: Martin Schwenke 
Reviewed-by: Volker Lendecke

ctdb-server: Load optional tunables.d/ directory

2025-07-23T00:02:47+00:00

Change the variable name to "path" so it makes sense to reuse it for
the directory.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs 

Autobuild-User(master): Martin Schwenke 
Autobuild-Date(master): Wed Jul 23 00:02:47 UTC 2025 on atb-devel-224

ctdb-daemon: Add configuration option shutdown extra timeout

2025-05-29T09:56:31+00:00

See documentation change for details.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15858

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-daemon: Add configuration option shutdown failover timeout

2025-05-29T09:56:31+00:00

Allows the timeout for failover during shutdown to be modified.
Defaults to 10s.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15858

Signed-off-by: Martin Schwenke 

SQ

Reviewed-by: Amitay Isaacs

ctdb/doc: document the newly added option to not register the helper

2025-03-14T09:42:02+00:00

Add the newly established -R (no-register) option to allow skipping the
registration of the helper as a ceph service.

Signed-off-by: John Mulligan 
Reviewed-by: Guenther Deschner 
Reviewed-by: Anoop C S 

Autobuild-User(master): Anoop C S 
Autobuild-Date(master): Fri Mar 14 09:42:02 UTC 2025 on atb-devel-224

ctdb-scripts: Change default persistent DB for statd_callout_helper

2024-12-13T15:01:10+00:00

This database isn't use throughout CTDB, so name the it more
specifically.

Note that this might cause locks to be lost during upgrade to the
first version containing this change.

For testing, a different name is chosen to exercise related
functionality.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs 

Autobuild-User(master): Amitay Isaacs 
Autobuild-Date(master): Fri Dec 13 15:01:10 UTC 2024 on atb-devel-224

ctdb-scripts: Support CTDB_STATD_CALLOUT_SHARED_STORAGE=none

2024-12-13T13:57:32+00:00

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-scripts: Support storing statd-callout state in cluster filesystem

2024-12-13T13:57:32+00:00

CTDB_STATD_CALLOUT_SHARED_STORAGE is a new configuration variable
indicating where statd-callout should store its NFS client locking
data.  See the update to ctdb-script.options(5) for details.

This adds back functionality that was removed in commit
12cc82623150ca4a83482f1b7165401cbdecd3de.  The commit message doesn't
say why this was changed but it was most likely due to a cluster
filesystem hanging at inopportune times.  Hence, this is re-added as a
non-default option.  There are 2 justifications for re-adding it:

* The existing method (persistent_db) relies on dequeuing data during
  the monitor event, which loses any queued data on node crash.

* NFS-Ganesha writes NFSv4 client locking data to a cluster
  filesystem, by default.  Something similar might as well exist for
  NFSv3.

Note that this could create the files for sm-notify in add-client.
However, this would require an alternate implementation of
send_notifies() (or a change to the implementation for persistent_db
too).  It seems better to leave add-client lightweight and do the work
in notify, since add-client is a more frequent operation.

Unconditionally create the state directory on startup.  This is
currently implicitly created for persistent_db when the queue
directory is created.  However, it isn't created anywhere else for
shared_dir, so do it in a common place.

In test mode, the shared storage location has a prefix added so files
are created within the test environment.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-scripts: Use CTDB_NFS_SHARED_STATE_DIR in nfs-ganesha-callout

2024-12-13T13:57:32+00:00

Rename CTDB_NFS_STATE_MNT to CTDB_NFS_SHARED_STATE_DIR.  It doesn't
have to be a mount but can be any directory in a cluster filesystem.
CTDB_NFS_SHARED_STATE_DIR will soon be used in statd_callout_helper,
so the variable name might as well be better.

With this change, it will still only be used by nfs-ganesha-callout,
which isn't yet supported (i.e. it still lives in doc/examples).  The
rest of the comments below refer to behaviour changes in that script.

CTDB_NFS_SHARED_STATE_DIR is now mandatory when GPFS is used.  This is
much saner that choosing the first GPFS filesystem - if the state
directory changes then connection metadata can be lost.

Drop CTDB_NFS_STATE_FS_TYPE.  The filesystem type is now determined
from CTDB_NFS_SHARED_STATE_DIR and it is now checked against supported
filesystems.  This will catch the case when the filesystem for the
specified directory has not been mounted and the filesystem for the
mountpoint (e.g. ext4) is not a supported filesystem for shared state.

A side-effect is that the filesystem containing
CTDB_NFS_SHARED_STATE_DIR must be mounted when nfs-ganesha-callout is
first run.

While touching this file, my shfmt pre-commit hook wants to insert a
trailing ;; into a case statement.  Let's sneak that in here too.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs