Hello,
We currently have a dataset structure similar to the below:
As each dataset is its own filesystem, we must export each of them individually similar to the below:
The issue is when we mount these child datasets, we constantly receive
Only when a non-root user accesses the share do we see the stale file handle. Reads and writes still proceed as normal (confirmed in FreeNAS) but it is not longer possible to view the contents of the share using
When we move these childsets to the same level of the parent (i.e.
What is the proper process to ensure we do not receive a
Thanks!
We currently have a dataset structure similar to the below:
vol1/parent/child1
vol1/parent/child2
As each dataset is its own filesystem, we must export each of them individually similar to the below:
/mnt/vol1/parent/child1 -maproot="root":"wheel" -sec=sys
/mnt/vol1/parent/child2 -maproot="root":"wheel" -sec=sys
The issue is when we mount these child datasets, we constantly receive
ls: cannot open directory '.': Stale file handle
when inspecting the directory. Strangely, we do not have any issues if the root user accesses the share or any non-root user when --mapall="root":"wheel"
is specified.Only when a non-root user accesses the share do we see the stale file handle. Reads and writes still proceed as normal (confirmed in FreeNAS) but it is not longer possible to view the contents of the share using
ls
on the client. This persists across all linux clients in our network.When we move these childsets to the same level of the parent (i.e.
vol1/child1
) the issue disappears but we are seeking to have a better structure for our datasets.What is the proper process to ensure we do not receive a
Stale file handle
when mounting child datasets over NFS? Please note that remounting the shares has had no effect.Thanks!
Last edited: