All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Langås" <tlan@stud.ntnu.no>
To: nfs@lists.sourceforge.net
Subject: NFS shares becoming disabled
Date: Wed, 9 Oct 2002 12:21:48 +0200	[thread overview]
Message-ID: <20021009102148.GD26096@stud.ntnu.no> (raw)

If you have a box with two (or more, maybe) shares exported, and one of theese
shares "dies", the other share will also become unavailable to the nfs clients
that tries to or has mounted any of theese shares.

We've seen this twice now, with our fileservers (each fileservers have two
disks mounted over fiberchannel). If one of those disks "die", ie. server
loose connectivity, both shares becomes unavailable to the nfs clients.

Why?  (It should only be the affected share that becomes unavailable, since
we locally can do whatever we want on the other disk that's still mounted).

-- 
Thomas


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2002-10-09 10:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021009102148.GD26096@stud.ntnu.no \
    --to=tlan@stud.ntnu.no \
    --cc=nfs@lists.sourceforge.net \
    /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.