Discussion:
NFS Share To OS X
MJ Jenkins
2014-09-25 13:15:24 UTC
Permalink
I have a user who is on a Mac, and has some data on our RedHat
Enterprise Linux(RHEL) server that needs to be shared to another RHEL
box and to her Mac. All seems to be fine on the RHEL box, and somewhat
on the Mac.

The problem comes in when the user on the Mac writes files to the NFS
share. On the RHEL side the files are owned by user root and group
nfsnobody. Has anyone else run into this issue? I'm not sure if the
issue is how I am exporting the share to the Mac, or how I have the
share mounted on the Mac.

Any assistance is greatly appreciated.

Mack

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Emmanuel Florac
2014-09-25 16:30:34 UTC
Permalink
Le Thu, 25 Sep 2014 09:15:24 -0400
The problem comes in when the user on the Mac writes files to the NFS=
=20
share. On the RHEL side the files are owned by user root and group=20
nfsnobody. Has anyone else run into this issue? I'm not sure if the=
=20
issue is how I am exporting the share to the Mac, or how I have the=20
share mounted on the Mac.
Without the content of your /etc/exports, it's impossible to know
what's happening. Mac behave like regular NFS clients. Maybe you have
"all_squash,anonuid=3D0,anongid=3D5" in your export parameter, maybe it=
's
something else entirely.

--=20
-----------------------------------------------------------------------=
-
Emmanuel Florac | Direction technique
| Intellique
| <eflorac-***@public.gmane.org>
| +33 1 78 94 84 02
-----------------------------------------------------------------------=
-
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Mauricio Tavares
2014-09-25 17:14:42 UTC
Permalink
On Thu, Sep 25, 2014 at 12:30 PM, Emmanuel Florac
Post by Emmanuel Florac
Le Thu, 25 Sep 2014 09:15:24 -0400
The problem comes in when the user on the Mac writes files to the NF=
S
Post by Emmanuel Florac
share. On the RHEL side the files are owned by user root and group
nfsnobody. Has anyone else run into this issue? I'm not sure if th=
e
Post by Emmanuel Florac
issue is how I am exporting the share to the Mac, or how I have the
share mounted on the Mac.
Without the content of your /etc/exports, it's impossible to know
what's happening. Mac behave like regular NFS clients. Maybe you have
"all_squash,anonuid=3D0,anongid=3D5" in your export parameter, maybe =
it's
Post by Emmanuel Florac
something else entirely.
I really want to say you need to export the fileshare with the
"insecure" option to make the Mac happy. Unfortunately I cannot check
that right now.
Post by Emmanuel Florac
--
---------------------------------------------------------------------=
---
Post by Emmanuel Florac
Emmanuel Florac | Direction technique
| Intellique
| +33 1 78 94 84 02
---------------------------------------------------------------------=
---
Post by Emmanuel Florac
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
Post by Emmanuel Florac
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
MJ Jenkins
2014-09-25 17:52:33 UTC
Permalink
This is the /etc/exports file. 129.169 is the Mac I'm exporting to. =20
129.183 is the other RHEL machine.

##### Mount point for Britney Schmidt's Mac Pro #####
/nfs/bsmac=20
192.168.129.169(rw,all_squash,no_subtree_check,insecure,anonuid=3D0)=20
192.168.129.183(rw,no_root_squash,no_subtree_chck)


This is /etc/fstab from the Mac.
#storage:/nfs/bsmac /data1 nfs=20
resvport,nolocks,locallocks,intr,soft,wsize=3D32768,rsize=3D3276
storage:/nfs/bsmac /data1 nfs=20
vers=3D3,noowners,nolocks,nolockd,nolock,nonlm,automounted,nosuid,hard,=
bg,noresvport,intr,rw,tcp,nfc

That 1st line in /etc/fstab is another way I was mounting the share=20
trying to solve this one.

Thanks for any assistance that can be provided.

Mack
Post by Emmanuel Florac
Le Thu, 25 Sep 2014 09:15:24 -0400
The problem comes in when the user on the Mac writes files to the NF=
S
Post by Emmanuel Florac
share. On the RHEL side the files are owned by user root and group
nfsnobody. Has anyone else run into this issue? I'm not sure if th=
e
Post by Emmanuel Florac
issue is how I am exporting the share to the Mac, or how I have the
share mounted on the Mac.
Without the content of your /etc/exports, it's impossible to know
what's happening. Mac behave like regular NFS clients. Maybe you have
"all_squash,anonuid=3D0,anongid=3D5" in your export parameter, maybe =
it's
Post by Emmanuel Florac
something else entirely.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Emmanuel Florac
2014-09-26 07:52:20 UTC
Permalink
Post by MJ Jenkins
192.168.129.169(rw,all_squash,no_subtree_check,insecure,anonuid=3D0)=20
Well you're squashing every user (all_squash) to the anonymous uid 0
(which is root). So you obtain the expected behaviour. Why did you put
these options in the first place?

The only special option you need is "insecure" for BSD (including Mac O=
S
X) clients.

--=20
-----------------------------------------------------------------------=
-
Emmanuel Florac | Direction technique
| Intellique
| <eflorac-***@public.gmane.org>
| +33 1 78 94 84 02
-----------------------------------------------------------------------=
-
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Continue reading on narkive:
Loading...