NFS share on MacOS TrueNAS-SCALE-22.02.1

[gertz]

Hi, I have issue with MacOS devices and showexports function. It's great truenas added "allow_nonroot" function to GUI in ticket NAS-115049, but there is probably still some issues, MacOS still can't see NFS shares with showexpeorts command due RPC error message. If anyone know way to fix this I will be glad.

Thank you for any help.

 

[Kris Moore]

Thanks for the heads up, probably worth filing a new ticket just to we can keep track of this and investigate if more fixes are needed.

 

[d187]

Unfortunately, the problem still exists with scale 22.12.

Code:

showmount: Cannot retrieve info from host: 192.168.30.11: RPC failed:: RPC: Program/version mismatch; low version = 3, high version = 3

is there a solution?

Kind regards

 

[anodos]

Unfortunately, the problem still exists with scale 22.12.

Code:

showmount: Cannot retrieve info from host: 192.168.30.11: RPC failed:: RPC: Program/version mismatch; low version = 3, high version = 3

is there a solution?

Kind regards

Maybe invoke showmount on the MacOS client with the -3 flag?

 

[d187]

Maybe invoke showmount on the MacOS client with the -3 flag?

That worked.
but how can i show all folders? under share the setting 'ALL DIR' is no longer available in 22.12.

 

[Daisuke]

That worked.

I'm just curious why you use NFS, when is recommended to use SMBv3 shares with recent macOS releases? You will have better performance on SMB shares and Mojave+, not to mention is easier to setup. Are you running a very old macOS release?

Protocol	Version​	Seq Read Speed​	Seq Write Speed​
NFS	v3 / v4	551 MB/sec	121 MB/sec
SMB	v1	161 MB/sec	169 MB/sec
SMB	v3	652 MB/sec	624 MB/sec

Take a look at Bluefin Upgrade Checklist, to setup properly your SMB shares and dataset permissions.

 

[d187]

if I create a smb share for datasheets that are also assigned in apps (e.g. jellyfin, nextcloud) as 'type of storage = host path', then these apps don't start. only when I deactivate the release do they start.
here the error message:

Code:

Error: Error response from daemon: invalid volume specification: '/mnt/daten-hdd-1/Filme:/media/Filme': Invalid mount path. /mnt/daten-hdd-1/Filme. Following service(s) uses this path: `SMB Share, NFS Share`.

since update on 22.12

 

[Daisuke]

Create an SMB share for the /mnt/pool, your apps will start without issues. Assign proper permissions to each dataset, is all explained into link I posted.

 

[anodos]

Create an SMB share for the /mnt/pool, your apps will start without issues. Assign proper permissions to each dataset, is all explained into link I posted.

Generally speaking sharing /mnt/pool when the ix-applications dataset is /mnt/pool/ix-applications is not a great idea and may raise a validation error (depending on configuration of child datasets).

 

[Daisuke]

Just to confirm, I experienced no issues with any Bluefin components, that’s why I shared all details of my upgrade setup. From my perspective, specific dataset permissions avoid any interaction with ix-applications dataset, which should never be exposed to end-user.

 

[anodos]

Just to confirm, I experienced no issues with any Bluefin components, that’s why I shared all details of my upgrade setup. From my perspective, specific dataset permissions avoid any interaction with ix-applications dataset, which should never be exposed to end-user.

Just glancing at your info, you have your apps dataset at
/mnt/software/ix-applications

And an SMB share of
/mnt/software

This is as I mentioned a bad idea. It grants all SMB users access to your ix-applications dataset and depending on permissions and mapping of uid/gids within that path may even grant write access. It probably worked for you because all of the datasets in that path had same ZFS properties, but I would be very hesitant to recommend such a setup to other users.

I have WIP patch for samba to prevent it from opening paths within ix-applications dataset or its children, but it's not in BlueFin yet.

 

[Daisuke]

This is as I mentioned a bad idea. It grants all SMB users access to your ix-applications dataset and depending on permissions and mapping of uid/gids within that path may even grant write access.

Good to know you are working on an improvement. Let's continue the discussion in this thread.