public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: wsnyder-12vJDDTx9R9AfugRpC6u6w@public.gmane.org (Wilson Snyder)
To: linux-nfs@vger.kernel.org
Subject: Problem with nfs server reboot causing exports to jumble
Date: Thu, 25 Feb 2010 14:29:10 -0500 (EST)	[thread overview]
Message-ID: <20100225192911.09CC318839E@wsnyder.org> (raw)


We're using the 2.6.18 x86_64 kernel (RH SL 5.1) with a NFS
v3 server and NFS v3 clients using the automounter with options
(rw,noatime,hard,intr,rsize=32768,wsize=32768,proto=tcp).

Our NFS server had several exports

    /export/a/{files-a}
    /export/b/{files-b}

these were mounted on various clients.

We then added a new mount and export without rebooting:

    /export/a/{files-a}
    /export/b/{files-b}
    /export/c/{files-c}

All were visible on the clients, and everything was fine:

    /nfs/a/{files-a}
    /nfs/b/{files-b}
    /nfs/c/{files-c}

Our NFS server then crashed, and rebooted.  After reboot the
clients then had:

    /nfs/a/{files-c}
    /nfs/b/{files-a}
    /nfs/c/{files-b}

Note the files correspond to the wrong exports.  Remounting
on every client fixed the problem - once we realized what
was going on!  (files-a/b/c were all similar so it wasn't
immediately aparent)

My speculation is the reboot changed some enumeration
causing a mismatch between the clients and servers.

This is a new one by me - is this a known issue, and if so
is a patch available?

Other than patching, are there any precautions we can take
to avoid this in the future?  (Other than not crashing the
server, which we'd be happy to not to do. :)

Thanks

             reply	other threads:[~2010-02-25 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 19:29 Wilson Snyder [this message]
     [not found] ` <20100225192911.09CC318839E-12vJDDTx9R9AfugRpC6u6w@public.gmane.org>
2010-02-25 20:06   ` Problem with nfs server reboot causing exports to jumble bpm
2010-02-25 20:33     ` Wilson Snyder
     [not found]       ` <20100225203336.9F69118839E-12vJDDTx9R9AfugRpC6u6w@public.gmane.org>
2010-02-26 16:38         ` bpm
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=20100225192911.09CC318839E@wsnyder.org \
    --to=wsnyder-12vjddtx9r9afugrpc6u6w@public.gmane.org \
    --cc=linux-nfs@vger.kernel.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