Scale 22.02.1 NFS problems

[unf0rg0tt3n]

Hey Guys, Hope y'all doing well!

I had the Truenas Beta and everything did work great until the update to 22.02.1
Now I have problems with NFS shares.

I can mount the share, and see certain folders and files. but like 99% is missing.

Client says:

Looks empty, permissions are the same on all folders because I used recursive perms.

On the server side:

On the client side I can create new files and folders but those aren't shown on the server side.
Whats wrong, more importantly.. how to fix this?

Tried updating permissions and mount options but no luck

Same post is on the LTT forums, but this forum was down when I posted it.

Cheers, thanks
Dennis

 

[anodos]

Are they child datasets? If so you need to mount through the NFS4 pseudo-root in order to traverse mountpoints. This is how NFS kernel server works in linux (as opposed to ganesha).

 

[unf0rg0tt3n]

Are they child datasets? If so you need to mount through the NFS4 pseudo-root in order to traverse mountpoints. This is how NFS kernel server works in linux (as opposed to ganesha).

They are child datasets indeed. So that's the reason my other mounts work fine.
How do I do the NFS4 psuedo-root mount of the child datasets? I'm using fstab to mount my share to the client

 

[anodos]

They are child datasets indeed. So that's the reason my other mounts work fine.
How do I do the NFS4 psuedo-root mount of the child datasets? I'm using fstab to mount my share to the client

NFS4 mount of <server>:/ will mount the pseudoroot filesystem.

 

[unf0rg0tt3n]

NFS4 mount of <server>:/ will mount the pseudoroot filesystem.

So I have tried what you suggested, unfortunately it does not work.
when I mount

Code:

192.168.1.3:/ /mnt/test nfs defaults,rw 0 0

it gives a folder structure
like: /mnt/test/mnt/<poolname>/ .....
and when navigating to plex, it's like the previous example I gave.

This are the datasets, <poolname> > data and plex > the rest in pic below

This are the shares:

 

[auqref]

me too

 

[unf0rg0tt3n]

me too

 

[bklyngaucho]

Me three. My NFS mount works perfectly fine until I upgrade 22.02-RC.2 to anything newer (22.02.1). The mount doesn't work after that.

• Server:
  • I have a fresh (did not upgrade from Core) install of TrueNAS-SCALE-22.02-RC.2
  • I have a dataset (data) and several child datasets (downloads, media, vms)
  • I have a single NFS share at the top level (data) with only defaults set
• Client:
  • OS: ubuntu 22.04
  • fstab: 192.168.1.xxx:/mnt/data /mnt/nfs nfs defaults 0 0

I'd love to move beyond this RC version of Scale, but need to sort this out. Help appreciated.

 

[dsumike]

So I have tried what you suggested, unfortunately it does not work.
when I mount

Code:

192.168.1.3:/ /mnt/test nfs defaults,rw 0 0

it gives a folder structure
like: /mnt/test/mnt/<poolname>/ .....
and when navigating to plex, it's like the previous example I gave.

This are the datasets, <poolname> > data and plex > the rest in pic below
View attachment 55377

This are the shares:
View attachment 55378

I was able to get a similar setup working by exposing both the main NFS mount point as well as the individual NFS mounts, while only needing to actually mount the top-level NFS mount from clients. In your example, that would be having NFS Shares (exports) for:

• /mnt/Hades/plex
• /mnt/Hades/plex/film
• /mnt/Hades/plex/serie

Enabling NFSv4 in System Settings -> Services -> NFS -> Enable NFSv4.

Then, mounting just /mnt/Hades/plex, I was able to access both the root dataset as well as the child datasets from the single mount point.

 

[unf0rg0tt3n]

I was able to get a similar setup working by exposing both the main NFS mount point as well as the individual NFS mounts, while only needing to actually mount the top-level NFS mount from clients. In your example, that would be having NFS Shares (exports) for:

• /mnt/Hades/plex
• /mnt/Hades/plex/film
• /mnt/Hades/plex/serie

Enabling NFSv4 in System Settings -> Services -> NFS -> Enable NFSv4.

Then, mounting just /mnt/Hades/plex, I was able to access both the root dataset as well as the child datasets from the single mount point.

This is some really useful information! Thanks for the update. Currently running those shares as SMB, I'll might try soon

 

[bklyngaucho]

I was able to get a similar setup working by exposing both the main NFS mount point as well as the individual NFS mounts, while only needing to actually mount the top-level NFS mount from clients. In your example, that would be having NFS Shares (exports) for:

• /mnt/Hades/plex
• /mnt/Hades/plex/film
• /mnt/Hades/plex/serie

Enabling NFSv4 in System Settings -> Services -> NFS -> Enable NFSv4.

Then, mounting just /mnt/Hades/plex, I was able to access both the root dataset as well as the child datasets from the single mount point.

This worked for me.