From: David Teigland <teigland@redhat.com>
To: gfs2@lists.linux.dev
Subject: New: use GFS2/DLM without a cluster
Date: Wed, 1 May 2024 12:26:01 -0500 [thread overview]
Message-ID: <ZjJ7KfWIVpn6kT5i@redhat.com> (raw)
A new daemon "dlm_sand" allows GFS2/DLM to be used without a cluster.
dlm_sand is an alternative to dlm_controld. Where dlm_controld uses
corosync to coordinate GFS2/DLM usage and recovery, dlm_sand does the
same coordination using the SAN storage that GFS2 is already using.
This makes GFS2/DLM usage simpler, more self contained, and suited to use
cases that are more data-oriented, rather than clustering/HA oriented.
The behavior and requirements of a traditional cluster can be intrusive
and limiting when the sole interest is just using the GFS2 file system.
At the link below you'll find an initial version of dlm_sand that should
work well enough for basic usage. The README includes how to use it, how
it works, and current limitations. I'd like to hear if you'd find it
useful, how it works for you, or any suggestions. Thanks!
https://pagure.io/dlm/blob/main/f/dlm_sand
reply other threads:[~2024-05-01 17:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZjJ7KfWIVpn6kT5i@redhat.com \
--to=teigland@redhat.com \
--cc=gfs2@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox