public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bpm@sgi.com
To: Wilson Snyder <wsnyder-12vJDDTx9R9AfugRpC6u6w@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Problem with nfs server reboot causing exports to jumble
Date: Fri, 26 Feb 2010 10:38:42 -0600	[thread overview]
Message-ID: <20100226163842.GI20620@sgi.com> (raw)
In-Reply-To: <20100225203336.9F69118839E-12vJDDTx9R9AfugRpC6u6w@public.gmane.org>

Hey Wilson,

On Thu, Feb 25, 2010 at 03:33:36PM -0500, Wilson Snyder wrote:
> >Use the mp and fsid export options documented in the exports manpage.
> 
> Reading between the lines, are you suggesting the mounts
> weren't ready when the exports started

I'm suggesting that it's a good idea to use the mp export option so that
you don't export your root filesystem in the off chance that the
filesystems you want to export aren't mounted yet.

> I presume then that it's enough to just use mp - assuming
> each mountpoint has a unique UUID?  

Look into how the fsid that identifies each filesystem to the nfs client
is chosen by the nfs server.  Is it possible that it changed across the
reboot?  I don't know offhand.  If it did change across a reboot, using
the fsid export option to explicitly set the fsid for each export might 
prevent this happening again.

> Wouldn't adding fsid now (with the server and clients all up) require
> me to remount every client?

Yep, I think so.  Maybe you want to schedule some downtime.

> Finally, is there a way to examine the present
> (automatically assigned) fsid's so I can confirm this was
> the problem?

Maybe you can try ethereal or something like that.

-Ben

  parent reply	other threads:[~2010-02-26 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 19:29 Problem with nfs server reboot causing exports to jumble Wilson Snyder
     [not found] ` <20100225192911.09CC318839E-12vJDDTx9R9AfugRpC6u6w@public.gmane.org>
2010-02-25 20:06   ` bpm
2010-02-25 20:33     ` Wilson Snyder
     [not found]       ` <20100225203336.9F69118839E-12vJDDTx9R9AfugRpC6u6w@public.gmane.org>
2010-02-26 16:38         ` bpm [this message]
2010-02-27 21:10   ` Neil Brown

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=20100226163842.GI20620@sgi.com \
    --to=bpm@sgi.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=wsnyder-12vJDDTx9R9AfugRpC6u6w@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox