ESXi NFSv4 mount issue - stale file handle

Chavell3_84

Cadet
Joined
Dec 9, 2020
Messages
5
Hello Community,

I have my TrueNAS Scale installed on a phyical box and running with the 22.12.3.3 Release (I didn't upgraded to the most recent release because I found nothing that could help for my problem).
I already mounted 3x NFS datastore via NFSv4 without any problem.
Now I'm trying to mount another datastore from a new dataset from a different IP subnet but I get an error with "stale file handle"...

brave_10172023_110926.png


As said, but that is weird as I already have 3 datastores running on TrueNAS... and that is a complete new dataset, no where else mounted

That is the share that is not working,

brave_10172023_104132.png


And that is a existing working dataset:

brave_10172023_111933.png


(do not wonder about the "networks", I use different ip addresses to mount that shares)

That is the network ports which is already working fine(that the onboard Intel I219 NIC):

brave_10172023_104441.png



That's the network that is not working, well for NFS(USB Realtek 2,5G NIC):
Driver is fully and succesfully installed(it does not use the CDC_ethernet driver)
brave_10172023_112425.png


The ethernet port should not be the problem, I tried SMB access from a windows machine to that 10.100.100.15, and that works without a problem.
And I can ping that 10.100.100.15 interface from the ESXi without a problem.

ESXi Log files are also not really helpful.


putty_10172023_110134.png



putty_10172023_105941.png


Unfortuntaly I could not find any specific NFS log on TrueNAS or some like that to identify the problem more in depth...
Or also the general logs are also not really helpful(I mean I can't see messages that could relate to the issue) to identify that issue further...

Maybe some of you have an idea.

Thanks.
 

Attachments

  • putty_10172023_110111.png
    putty_10172023_110111.png
    93.5 KB · Views: 33
  • putty_10172023_110111.png
    putty_10172023_110111.png
    93.5 KB · Views: 33

Chavell3_84

Cadet
Joined
Dec 9, 2020
Messages
5
Maybe someone is more clever on analyzing TCP dumps than me, so I added some dump I did.

What is curious, one of the first lines(black):
1697537148450.png


Those black error only happen once, even if I try to mount the share multiple time within that TCP dump

besides that, I see that NFS stale also in those packets.
1697537327105.png


The filter I used is
(eth.src == 00:24:27:88:11:40) || (eth.src == 00:50:56:64:42:53) - 11:40 is the NAS, 42:53 is the ESXi host.

thanks
 

Attachments

  • tcp_dump.zip
    61.8 KB · Views: 34
Top