Flash619
Cadet
- Joined
- Jun 7, 2017
- Messages
- 1
Greetings, I am trying to get NFS working on a new FreeNAS 11 RC3 install. The client I will be using to test is running KDE Neon User Edition LTS.
After setting up NFS, once mounted (with nfs4 disabled), all datasets appear to be owned by root:root. If I enable nfs4, the correct permissions are shown, but ls is broken "input / output error" as well as when trying to create files of any kind.
/etc/exports
Client Mount
As you can see, the directory containing the datasets is properly set to nobody:nogroup. However none of these permissions are correct on the directories within this folder. Here is the same command from on the NAS itself.
Datasets On Nas
I'm not really sure what could be going wrong at this point. So any input could be helpful. I will try to give as much info as possible. As I've said, nfs4 has errors as well, so whichever would be the easiest to fix is likely what I will end up using.
EDIT
While I did not get nfs3 working, I did find my issue with nfs 4.
It seems you cannot mount the parent directory of datasets and still access the dataset. This is because a dataset is seen as a separate file system (which it is) and as such is technically not mounted within the parent. The fix was to export each dataset individually and mount with /ets/fstab to make my life easy.
After setting up NFS, once mounted (with nfs4 disabled), all datasets appear to be owned by root:root. If I enable nfs4, the correct permissions are shown, but ls is broken "input / output error" as well as when trying to create files of any kind.
/etc/exports
Code:
/mnt/tank/nas -alldirs -mapall="nobody":"nobody" 192.168.1.60
Client Mount
Code:
Flash619@office-pc:/mnt/nfs$ sudo mount -t nfs nas:/mnt/tank/nas /mnt/nfs/nas/ Flash619@office-pc:/mnt/nfs$ ls -la /mnt/nfs/nas/ total 15 drwxrwx--- 7 nobody nogroup 7 Jun 7 16:21 . drwxr-xr-x 3 root root 4096 Jun 7 16:45 .. drwxr-xr-x 2 root root 2 Jun 7 16:20 dataset1 drwxr-xr-x 2 root root 2 Jun 7 16:20 dataset2 drwxr-xr-x 2 root root 2 Jun 7 16:19 dataset3 drwxr-xr-x 2 root root 2 Jun 7 16:21 dataset4 drwxr-xr-x 2 root root 2 Jun 7 16:19 dataset5
As you can see, the directory containing the datasets is properly set to nobody:nogroup. However none of these permissions are correct on the directories within this folder. Here is the same command from on the NAS itself.
Datasets On Nas
Code:
[root@nas ~]# ls -la /mnt/tank/nas/ total 23 drwxrwx--- 7 nobody nobody 7 Jun 7 14:21 . drwxr-xr-x 4 root wheel 4 Jun 7 16:25 .. drwxrwx--- 2 nobody nobody 2 Jun 7 14:20 dataset1 drwxrwx--- 2 nobody nobody 2 Jun 7 14:20 dataset2 drwxrwx--- 6 nobody nobody 6 Jun 7 16:02 dataset3 drwxrwx--- 2 nobody nobody 2 Jun 7 14:21 dataset4 drwxrwx--- 2 nobody nobody 2 Jun 7 14:19 dataset4
I'm not really sure what could be going wrong at this point. So any input could be helpful. I will try to give as much info as possible. As I've said, nfs4 has errors as well, so whichever would be the easiest to fix is likely what I will end up using.
EDIT
While I did not get nfs3 working, I did find my issue with nfs 4.
It seems you cannot mount the parent directory of datasets and still access the dataset. This is because a dataset is seen as a separate file system (which it is) and as such is technically not mounted within the parent. The fix was to export each dataset individually and mount with /ets/fstab to make my life easy.
Last edited:
