NFS Share To OS X
Subsystems (2)
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
Le Thu, 25 Sep 2014 09:15:24 -0400
MJ Jenkins <[email protected]> écrivait:
Quoted 5 lines
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.
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=0,anongid=5" in your export parameter, maybe it's something else entirely.
Signature · 6 lines
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <[email protected]>
| +33 1 78 94 84 02
------------------------------------------------------------------------Quoted 9 lines · Emmanuel Florac
Le Thu, 25 Sep 2014 09:15:24 -0400
MJ Jenkins <[email protected]> écrivait:Quoted 5 lines
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.
Quoted 5 lines
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=0,anongid=5" in your export parameter, maybe it's 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.
Quoted 11 lines
--
------------------------------------------------------------------------Emmanuel Florac | Direction technique | Intellique | <[email protected]> | +33 1 78 94 84 02------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
This is the /etc/exports file. 129.169 is the Mac I'm exporting to. 129.183 is the other RHEL machine.
##### Mount point for Britney Schmidt's Mac Pro #####
/nfs/bsmac 192.168.129.169(rw,all_squash,no_subtree_check,insecure,anonuid=0) 192.168.129.183(rw,no_root_squash,no_subtree_chck)
This is /etc/fstab from the Mac.
#storage:/nfs/bsmac /data1 nfs resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276 storage:/nfs/bsmac /data1 nfs vers=3,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 trying to solve this one.
Thanks for any assistance that can be provided.
Mack
Quoted 13 lines · Emmanuel Florac
Le Thu, 25 Sep 2014 09:15:24 -0400
MJ Jenkins <[email protected]> écrivait:Quoted 5 lines
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.
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=0,anongid=5" in your export parameter, maybe it's something else entirely.
Le Thu, 25 Sep 2014 13:52:33 -0400 vous écriviez:
Quoted 1 line
192.168.129.169(rw,all_squash,no_subtree_check,insecure,anonuid=0)
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 OS
X) clients.
Signature · 6 lines
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <[email protected]>
| +33 1 78 94 84 02
------------------------------------------------------------------------