All of
 help / color / mirror / Atom feed
From: Daire Byrne <>
To: Bruce Fields <>
Cc: Chuck Lever III <>,
	Linux NFS Mailing List <>
Subject: Re: [PATCH] nfs: reexport documentation
Date: Wed, 22 Sep 2021 10:47:35 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 21 Sept 2021 at 17:00, Bruce Fields <> wrote:
> > Any recommended workarounds? Or does this simply mean that
> > administrators need to notify client users to unmount (or
> > at least stop their workloads) before rebooting the proxy?
> I think so.
> If you don't use any file locking or delegations I suppose you're also
> OK.  Delegations might be useful, though.
> I'd expect reexport to be useful mainly for data that changes very
> rarely, if that helps.
> --b.

Firstly, it's great to see this documentation and the well maintained
wiki page for something we use in production (a lot) - thanks Bruce!

I can only draw on our experience to say:
* if the nfs re-export server doesn't crash, we rarely have cause to reboot it.
* we re-export read-only software repositories to WAN/cloud instances
(an ideal use case).
* we also re-export read/write production storage but every client
process is writing unique files - there are no writes to the same
file(s) from any clients of the re-export server.

We don't use or need crossmnt functionality, but I know from chatting
to others within our industry that the fsid/crossmnt limitation causes
them the most grief and confusion. I think in the case of Netapps,
there are similar problems with trying to re-export a namespace made
up of different volumes?

As noted on the wiki, the only way around that is probably to have a
"proxy" mode (similar to what ganesha does?).


  reply	other threads:[~2021-09-22  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 14:32 J. Bruce Fields
2021-09-21 14:39 ` Chuck Lever III
2021-09-21 16:00   ` Bruce Fields
2021-09-22  9:47     ` Daire Byrne [this message]
2021-09-22 14:26       ` Bruce Fields
2021-09-22 14:40         ` Frank Filz
2021-09-22 14:32       ` Frank Filz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [PATCH] nfs: reexport documentation' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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.