From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs: reexport documentation
Date: Tue, 21 Sep 2021 12:00:30 -0400 [thread overview]
Message-ID: <20210921160030.GC21704@fieldses.org> (raw)
In-Reply-To: <37851433-48C9-4585-9B68-834474AA6E06@oracle.com>
On Tue, Sep 21, 2021 at 02:39:39PM +0000, Chuck Lever III wrote:
> > On Sep 21, 2021, at 10:32 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > +It is possible to reexport an NFS filesystem over NFS. However, this
> > +feature comes with a number of limitations. Before trying it, we
> > +recommend some careful research to determine wether it will work for
> > +your purposes.
>
> ^wether^whether
Fixed.
> > +
> > +A discussion of current known limitations follows.
> > +
> > +"fsid=" required, crossmnt broken
> > +---------------------------------
> > +
> > +We require the "fsid=" export option on any reexport of an NFS
> > +filesystem.
>
> Recommended approach? I would just say use 'uuidgen -r'
Looking at the manual.... I'd somehow missed that fsid= would take a
uuid (and not just a small integer) now. So, sure, I'll add that as a
suggestion.
Longer term I wonder if it would work to do this automatically for new
nfs reexports. The annoying part is you'd have to keep the fsid=
argument on disk somehow, either by modifying the export configuration
in /etc or by keeping them on the side somewhere. That'd fix crossmnt
too.
> > +The "crossmnt" export option does not work in the reexport case.
>
> Can you expand on this a little? Consequences? Risks?
crossmnt doesn't propagate fsid= (for obvious reasons), so if you cross
into another nfs filesystem then it'll fail.
Actually if you just had disk filesystems mounted underneath it'd
probably work.
> > +Reboot recovery
> > +---------------
> > +
> > +The NFS protocol's normal reboot recovery mechanisms don't work for the
> > +case when the reexport server reboots. Clients will lose any locks
> > +they held before the reboot, and further IO will result in errors.
> > +Closing and reopening files should clear the errors.
>
> 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.
diff --git a/Documentation/filesystems/nfs/reexport.rst b/Documentation/filesystems/nfs/reexport.rst
index 892cb1e9c45c..ff9ae4a46530 100644
--- a/Documentation/filesystems/nfs/reexport.rst
+++ b/Documentation/filesystems/nfs/reexport.rst
@@ -6,7 +6,7 @@ Overview
It is possible to reexport an NFS filesystem over NFS. However, this
feature comes with a number of limitations. Before trying it, we
-recommend some careful research to determine wether it will work for
+recommend some careful research to determine whether it will work for
your purposes.
A discussion of current known limitations follows.
@@ -15,9 +15,12 @@ A discussion of current known limitations follows.
---------------------------------
We require the "fsid=" export option on any reexport of an NFS
-filesystem.
+filesystem. You can use "uuidgen -r" to generate a unique argument.
-The "crossmnt" export option does not work in the reexport case.
+The "crossmnt" export does not propagate "fsid=", so it will not allow
+traversing into further nfs filesystems; if you wish to export nfs
+filesystems mounted under the exported filesystem, you'll need to export
+them explicitly, assigning each its own unique "fsid= option.
Reboot recovery
---------------
next prev parent reply other threads:[~2021-09-21 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 14:32 [PATCH] nfs: reexport documentation J. Bruce Fields
2021-09-21 14:39 ` Chuck Lever III
2021-09-21 16:00 ` Bruce Fields [this message]
2021-09-22 9:47 ` Daire Byrne
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:
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=20210921160030.GC21704@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).