From: tridge@samba.org <tridge@samba.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Clustered Samba/CTDB on ocfs2 ?
Date: Wed May 2 14:11:24 2007 [thread overview]
Message-ID: <17976.65193.79079.299940@samba.org> (raw)
In-Reply-To: <20070502204508.GM21982@ca-server1.us.oracle.com>
Mark,
> Definitely - working well with Samba is one of the things that Ocfs2 is
> interested in.
great!
> Does it require the file system to support cluster-aware fcntl locking?
> That's the one thing that Ocfs2 doesn't do yet.
no, it doesn't need fcntl locking in the filesystem.
Basically CTDB is a clustered version of the tdb database in Samba. It
has its own DLM, and its own communications system (can be either TCP
or infiniband).
Not all of the Samba internal databases can use CTDB yet, so for those
that aren't yet using CTDB they should be stored on a filesystem that
supports fcntl locking. Eventually all the Samba databases will be
able to use CTDB, at which time Samba should be making no fcntl lock
requests to the cluster filesystem at all. In the meantime, you can
still test Samba on ocfs2, but if you (for example) change passwords
on two nodes at the same time then there is a slight risk of data
corruption in the passsword database. That's because the tdbsam
database is not yet using CTDB. You could avoid that particular
problem by using a ldap server for your password database.
I assume ocfs2 is data coherent? That is the main requirement from the
cluster filesystem. If you are not data coherent then clustered Samba
will still work, but a user who writes a file to one node may get old
data if they fetch it on another node.
Cheers, Tridge
next prev parent reply other threads:[~2007-05-02 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 13:29 [Ocfs2-devel] Clustered Samba/CTDB on ocfs2 ? tridge
2007-05-02 13:45 ` Mark Fasheh
2007-05-02 14:11 ` tridge [this message]
2007-05-02 14:29 ` Mark Fasheh
2007-05-02 14:46 ` tridge
2007-06-04 0:01 ` tridge
2007-06-04 8:48 ` Robert Wipfel
2007-06-06 3:32 ` tridge
2007-06-08 9:06 ` Robert Wipfel
2007-06-04 15:00 ` Mark Fasheh
2007-06-05 4:11 ` tridge
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=17976.65193.79079.299940@samba.org \
--to=tridge@samba.org \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.