All of lore.kernel.org
 help / color / mirror / Atom feed
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:46:14 2007	[thread overview]
Message-ID: <17977.1747.673366.638199@samba.org> (raw)
In-Reply-To: <20070502212930.GN21982@ca-server1.us.oracle.com>

Mark,

 > Ok - understood. Out of curiousity, where is this stuff in its lifetime
 > (i.e., alpha, aeta, post release, etc). Once we verify that things are
 > working with Ocfs2 as expected, we could start pointing people asking about
 > Samba to the CTDB stuff.

It ran for the first time on a real cluster (running GPFS) at SambaXP
in Germany last week. It is progressing very rapidly though, and we
hope there will be real deployments soon.

So I guess you'd call it alpha. It doesn't yet do auto-recovery after
a node crash. We're working on that now. We want it to the point that
you can pull the power on a node in the cluster and the other nodes
continue with no data loss (that takes some fancy footwork, as we
deliberately do not replicate all the meta data between nodes in the
cluster, so we need a smart recovery system).

 > Yeah - we handle data coherency between nodes. O_DIRECT gets you around some
 > of those guarantees, so mixing it with buffered I/O is generally discouraged.
 > 	--Mark

we never use O_DIRECT, so that sounds good.

Cheers, Tridge

  reply	other threads:[~2007-05-02 14:46 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
2007-05-02 14:29     ` Mark Fasheh
2007-05-02 14:46       ` tridge [this message]
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=17977.1747.673366.638199@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.