From: Lars Marowsky-Bree <lmb@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [Linux-ha-dev] Re: [PATCH 00/11] ocfs2: implement userspace clustering interface
Date: Wed, 1 Feb 2006 16:29:31 +0100 [thread overview]
Message-ID: <20060201152931.GI28936@marowsky-bree.de> (raw)
In-Reply-To: <43E0D25D.9080105@unix.sh>
On 2006-02-01T08:23:09, Alan Robertson <alanr@unix.sh> wrote:
> Except that you CANNOT mount, umount, or mkfs before the CRM starts.
> This means you can't put it in fstab like people conventionally do.
> (Unless of course, the CRM somehow gets started really early - this
> would likely be messy)
Well of course. That is quite true. You can't access a cluster
filesystem before the cluster stack is up.
And just like other Filesystem instances or any other resource on our
control, we require that it not be started before us; ie, not mounted
auotmatically on boot.
But, if the admin wishes, this could be implemented similar to ocfs2
already does it - namely, it already has to delay mounting until after
the network is up (like NFS), and would thus delay until hb is up.
Thanks for the clarification.
This is not much of an issue unless we aim for "shared root" on a
cluster filesystem, in which case we'd need to get fancy with
initrd/initramfs and initialize (maybe in a low-cost read/only mode)
access to the root fs. This is something I'm right now not that
interested in because of the pain this implies at various places and
would require changes to the whole distribution.
And sorry for running off on this tangent ;-) Just important to keep at
the back of the mind, even if not relevant yet.
> Lars already knows this - but for the rest of you: This would be
> relatively easily implemented in our current architecture. We already
> have a special class of resource agent which does this (STONITH).
> Adding a "general" one would be relatively easy. Just need to make sure
> we design the API in an extensible way so we don't have a bunch of churn
> later on.
Right, there's even an open bugzilla to track this feature already.
Sincerely,
Lars Marowsky-Br?e
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
prev parent reply other threads:[~2006-02-01 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 22:39 [Ocfs2-devel] [PATCH 00/11] ocfs2: implement userspace clustering interface Jeff Mahoney
2006-01-10 4:29 ` Mark Fasheh
2006-01-10 4:51 ` Jeffrey Mahoney
2006-01-10 10:43 ` Lars Marowsky-Bree
2006-01-10 19:08 ` Mark Fasheh
2006-02-01 12:27 ` Lars Marowsky-Bree
[not found] ` <43E0D25D.9080105@unix.sh>
2006-02-01 15:29 ` Lars Marowsky-Bree [this message]
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=20060201152931.GI28936@marowsky-bree.de \
--to=lmb@suse.de \
--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.