Another NFS share already exports this dataset for some network

[bhavik]

Hi,

Please pardon me if I miss anything as this is my first post to the TruaNAS forum, my posts will improvise with time.

I am running into an error:
Another NFS share already exports this dataset for some network

While trying to export the "home" folder as an NFS export. I have verified in the sharing options there are no existing shares for both NFS and SMB and besides this error message, which is preventing me from creating the NFS share, I couldn't find any other information to troubleshoot and fix this issue. Can you please help/suggest what might be going wrong on my part? And how can I get this resolved?

Attaching the screen capture depicting the same error and related details from the wb GUI page.

Please let me know if there are any questions.


Thanks,
Bhavik

 

[sretalla]

I have verified in the sharing options there are no existing shares for both NFS and SMB

You haven't shown us a picture of that, but if it's right, then the error you're seeing is a bug.

If you are sharing *anything* else with NFS, it's possible that you have an overlap in the scope, which makes that error logical.

 

[bhavik]

Thank you for your notes on this Wizened.

You haven't shown us a picture of that, but if it's right, then the error you're seeing is a bug.

https://www.truenas.com/community/attachments/truenas_another_nfs_share_error-png.47284/ - Also I have attached the same in my initial post and hope the same is accessible to you. Please let me know if you would be asking for something else, I will surely share it here.

Also, as for the overlapping NFS sharing scope, this is some more info related to that per which I understand there's no overlapping sharing unless I am missing something.

Code:

bsukhadia@fpfs001:~ $ cat /etc/exports
/mnt/Pool1/jobs -alldirs
bsukhadia@fpfs001:~ $

So, what I am trying to share over the NFS are:

1. /mnt/Pool1/home - (giving an error - Another NFS share already exports this dataset for some network)
2. /mnt/Pool1/jobs - (already exported and working per the /etc/exports)

Code:

bsukhadia@fpfs001:~ $ ls -la /mnt/Pool1/
total 18
drwxr-xr-x   4 root       wheel    4 May 20 20:29 .
drwxr-xr-x   3 root       wheel  128 May 20 18:49 ..
drwxr-xr-x  13 root       wheel   13 May 20 20:01 home
drwxrwxrwx+ 11 bsukhadia  vfx     11 May 20 23:34 jobs
bsukhadia@fpfs001:~ $

Any further inputs to debug this issue will be greatly appreciated.

Thanks,
Bhavik

 

[sretalla]

/mnt/Pool1/jobs - (already exported and working per the /etc/exports)

So here's what I was asking about... a screenshot of the NFS shares screen would have shown it.

I am guessing that jobs and home are both subdirectories in Pool1 (not child datasets), so the error makes sense... you can do 2 things to improve the situation:

1. remove the current share of jobs and re-share at the Pool1 level, then controlling the shares at the mapping level on the clients.
2. remove the current share of jobs and remove both directories, replacing them with child datasets (with the same names if you want), then make your shares of each dataset.

 

[bhavik]

Many thanks for your notes once again, I believe you suggested something like the below when referring to #2

Code:

root@fpfs001[~]# cat /etc/exports 
/mnt/Pool1/home /mnt/Pool1/jobs
root@fpfs001[~]# 

While this works fine per truenas_another_nfs_share_error_fix01.png and truenas_another_nfs_share_error_fix02.png but when I am trying to export it with "All dirs" option it is resulting in truenas_another_nfs_share_error_fix03.png - any thoughts/suggestions would be very helpful.

Please let me know if I need to share any other config info.

Thanks,

 

[bhavik]

Additionally, at the client end, I do see these exports being available at the client end:

Code:

showmount -e 192.168.0.21
Export list for 192.168.0.21:                                                                                                                                           
/mnt/Pool1/home (everyone)                                                                                                                                               
/mnt/Pool1/jobs (everyone)

However, with the home export, my goal was to mount the respective user's home directory as opposed to the entire home (exported) folder.