All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS not mountable until all nodes are up
Date: Tue, 5 Jun 2007 08:42:31 -0500	[thread overview]
Message-ID: <20070605134231.GA9298@redhat.com> (raw)
In-Reply-To: <466522AA.1010304@forschungsgruppe.de>

On Tue, Jun 05, 2007 at 10:45:30AM +0200, Christian Brandes wrote:
> One week ago I opened a bug report about this topic:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241663
> 
> And I would like to know, why all cluster nodes need to be started 
> first, before GFS can be mounted, and what alternatives I have, when one 
> node cannot start.
> 
> Please give me some advice, since I do not know how to solve this problem.

I've updated the bz with some debugging steps to see why your mount is
failing.  Mounting should work if the cluster has quorum.

Dave



      reply	other threads:[~2007-06-05 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05  8:45 [Cluster-devel] GFS not mountable until all nodes are up Christian Brandes
2007-06-05 13:42 ` David Teigland [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=20070605134231.GA9298@redhat.com \
    --to=teigland@redhat.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.