From: bfields@fieldses.org (J. Bruce Fields)
To: "Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]" <jeffrey.c.becker@nasa.gov>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: FW: [EXTERNAL] Re: NFS server question
Date: Wed, 7 Jul 2021 10:13:59 -0400 [thread overview]
Message-ID: <20210707141359.GB9446@fieldses.org> (raw)
In-Reply-To: <C88E1CD2-4156-4E45-AC27-F19D4E4C9FC7@ndc.nasa.gov>
On Fri, Jul 02, 2021 at 03:11:11PM +0000, Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC] wrote:
> Is there a limit on the number of exports for an NFS server? Thanks.
I don't have a better answer than Chuck's.
I can't think of any hard-coded limits, it's just a matter of resources.
You could try giving more specifics about your plan and see if anyone
has experience with a similar setup.
--b.
>
> Jeff Becker
>
> On 7/2/21, 7:21 AM, "Chuck Lever III" <chuck.lever@oracle.com> wrote:
>
> Hi Jeff-
>
> > On Jul 1, 2021, at 7:54 PM, Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC] <jeffrey.c.becker@nasa.gov> wrote:
> >
> > Hi Chuck,
> >
> > I have an NFS server that currently has about 20 directories it’s exporting over NFSv4. I was wondering what the maximum number of exports is. Thanks.
>
> I'm not aware of any intrinsic limit on the number of exports.
> There is probably a per-export resource cost that acts as a
> practical limit.
>
> Might be a good idea to ask on linux-nfs@vger.kernel.org.
>
>
> --
> Chuck Lever
>
>
>
>
prev parent reply other threads:[~2021-07-07 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0C9D9022-8E61-4B03-8225-D829E22B4137@ndc.nasa.gov>
[not found] ` <E168219A-8120-4154-80E7-DC03F70D69D1@oracle.com>
2021-07-02 15:11 ` FW: [EXTERNAL] Re: NFS server question Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]
2021-07-07 14:13 ` J. Bruce Fields [this message]
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=20210707141359.GB9446@fieldses.org \
--to=bfields@fieldses.org \
--cc=jeffrey.c.becker@nasa.gov \
--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