All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] shutdown of filesystems and quorum
Date: Wed Sep 28 18:46:08 2005	[thread overview]
Message-ID: <433B2B3E.805@oracle.com> (raw)
In-Reply-To: <20050928233249.GB17462@ca-server1.us.oracle.com>

umount script should look at /etc/mtab and not /etc/fstab.

netfs looks at /etc/mtab or /proc/mounts depending on the version.

Joel Becker wrote:

>	I just realized.  Even with _netdev, we have a problem on Red
>Hat.  Normally, we assume that netfs will start up our _netdev
>filesystems and umount them on shutdown.  But what about filesystems
>that aren't in /etc/fstab?  What about filesystems that are noauto?  I'm
>not sure what netfs does with noauto on shutdown, but I'm certain it has
>no idea about OCFS2 filesystems that aren't in /etc/fstab.  It knows
>about nfs/gfs/etc, because it hardcodes those fs types.  But it only
>tracks OCFS2 filesystems via the /etc/fstab entries.
>	What does this mean?  Even with /etc/init.d/netfs, any
>filesystem that isn't in /etc/fstab will not be umounted before the
>network is stopped.  So every other node mounting that filesystem will
>see:
>
>	o network connection went away
>	o heartbeat is still alive
>	=> Ergo, make a quorum decision, perhaps killing myself.
>
>Yuk.
>	What should we do?  Try to persuade Red Hat to add OCFS2 as an
>explicit type in netfs (means we don't even need to tell our customers
>_netdev anymore)?  That doesn't help sles/debian.  We have a script for
>sles.  Maybe use that everywhere?
>	What are your thoughts?
>
>Joel
>  
>

  reply	other threads:[~2005-09-28 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 18:32 [Ocfs2-devel] shutdown of filesystems and quorum Joel Becker
2005-09-28 18:46 ` Sunil Mushran [this message]
2005-09-28 18:54   ` Joel Becker
2005-09-28 19:08     ` Sunil Mushran

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=433B2B3E.805@oracle.com \
    --to=sunil.mushran@oracle.com \
    --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.