Sharing Mac Snow Leopard directory via NFS

file-sharingnfsosx

I am running a Mac Pro using Snow Leopard (not server). I would like to share a directory with a linux machine. I have edited /etc/exports on the Mac to:

/Volumes/mstore/home/sdavis -maproot=root -rw

When I try to mount this from a linux machine, I get:

 sudo mount gale.nci.nih.gov:/Volumes/mstore/home/sdavis /tmp/abc
mount.nfs: access denied by server while mounting gale.nci.nih.gov:/Volumes/mstore/home/sdavis

Also, this is what I get for showmount -e on the Mac:

% showmount -e
Exports list on localhost:
%

In other words, the mount is not seen, apparently. Any suggestions? I have not found much good documentation on sharing via NFS on the Mac, particularly for later OS versions.

Best Answer

Bad form, I know, to answer my own question, but.... I needed a couple more steps, outlined here. In short, I needed to execute:

sudo nfsd update

As another detail, I added the client name to the export and removed the "-rw" flag.

Related Solutions

NFS Share – Creating from a CIFS Mounted Directory

You can pass from cifs mount to nfs export via a fuse filesystem, though I don't think I would recommend it for something as essential as backup.

When I tried this once I looked for a fuse filesystem that would be as transparent as possible, and ending up with fuse-convmvfs. This software is intended to convert filenames from one encoding to another, but if you configure it to the same encoding at both sides, it seems to work as you need.

Quite simply, if you have your cifs mount at /mnt/samba, you can mount your fuse at /mnt/fuse and export this directory by nfs using an /etc/exports entry like

/mnt/fuse backupmachine(ro,fsid=55)

and the commands

$ sudo sh -c 'echo user_allow_other >>/etc/fuse.conf'
$ sudo convmvfs /mnt/fuse -o srcdir=/mnt/samba,icharset=iso-8859-1,ocharset=iso-8859-1,user_allow_other
$ sudo exportfs -a

The user_allow_other part is probably not needed for nfs export. While this is ok as an experiment, note that nfs is dangerous with filesystems that do not use the same inode in a repeatable way, and that is probably why nfs on top of cifs is not implemented. Adding the fuse layer is not necessarily going to fix this. Perhaps if you can independently produce a list of md5 sums of each file locally on the cifs server, and locally on the backup machine, and compare the two, you might have some confidence in a backup.

Nfs mount failed: reason given by server: No such file or directory

Does not apply to NFSv4:

Why did you not include the folder before /backup/?

It should be :
server:/export/backup/system/pc1 /backup/system nfs4 auto,noatime        0 0
You need to mount it according to your export file.

Edit :

Could it be that you are exporting the file pc1 only to the IP address 192.168.1.8 and your client does not have that IP.

Try changing the IP address :

/export/backup/system/pc1 192.168.1.0/24(rw,sync,no_root_squash,no_subtree_check)

Best Answer

Related Solutions

NFS Share – Creating from a CIFS Mounted Directory

Nfs mount failed: reason given by server: No such file or directory

Related Question