From: poma <pomidorabelisima@gmail.com>
To: Community support for Fedora users <users@lists.fedoraproject.org>
Cc: Greg Scott <GregScott@infrasupport.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: What does "mapping=identity" mean in /etc/exports?
Date: Fri, 22 Feb 2013 19:25:23 +0100 [thread overview]
Message-ID: <5127B813.5040601@gmail.com> (raw)
In-Reply-To: <1470031369de4d60a0d5965ec6bede10@mail2013.infrasupport.local>
On 02/16/13 22:09, Greg Scott wrote:
> Hello -
>
> I'm migrating an old NFS server to newer hardware. /etc/exports in the old environment looks like this:
>
> /shares/IMSHCS01 *(rw,insecure,sync,no_root_squash,all_squash,mapping=identity,anonuid=0,anongid=0
>
> So the old system is exporting the directory, /shares/IMSHCS01 to anyone and everyone who wants to connect, with a bunch of switches essentially making it wide open.
>
> Wonderful.
>
> But on the new system, when I set up /etc/exports the same way, I get this error:
>
> [root@nfs2013 etc]# exportfs -av
> exportfs: /etc/exports:1: unknown keyword "mapping=identity"
>
> [root@nfs2013 etc]#
>
> Getting rid of "mapping=identity", my shared directory exports just fine.
>
> I can find no mention of "mapping=identity" in any man pages, but several google references show this option in pasted-in copies of /etc/exports files. My hunch is, this is an obsolete option and no longer supported - but what did it do in case my new server needs to behave the same way the old server behaved?
>
Probably related to the unfsd[1].
iSeries? ;)
[1]
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=74a8f33de5f26d6bab11d5299318035d65bd60d0;hp=afc841a1f2a62645ec2dfaa333baf07e44a03c08
Cheers,
poma
next parent reply other threads:[~2013-02-22 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1470031369de4d60a0d5965ec6bede10@mail2013.infrasupport.local>
2013-02-22 18:25 ` poma [this message]
2013-03-01 19:18 ` What does "mapping=identity" mean in /etc/exports? Greg Scott
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=5127B813.5040601@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=GregScott@infrasupport.com \
--cc=linux-nfs@vger.kernel.org \
--cc=users@lists.fedoraproject.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).