Skip to main content
Unix & Linux

Return to Answer

Apology not required (new input on old problems that still persist is welcome), minor rephrasing, add formatting.
Source Link
AdminBee
AdminBee
  • 23.6k
  • 25
  • 55
  • 77

Apologies for the necropost, but thisThis issue just hit me on a Mac running Ventura 13.2 accessing a QNAP with NFS. Wound up with a stale NFS handle that would not go away despite reboots of both devices. 

To confirm, just logging into the server using sshssh and doing exportfs -ra

exportfs -ra

without anything else, no (no config changes, no playing with fsidfsid, no other actions, just exportfs -ra on the QNAP, and) made the problem wentgo away.

Apologies for the necropost, but this issue just hit me on a Mac running Ventura 13.2 accessing a QNAP with NFS. Wound up with a stale NFS handle that would not go away despite reboots of both devices. To confirm, just logging into the server using ssh and doing exportfs -ra without anything else, no config changes, no playing with fsid, no other actions, just exportfs -ra on the QNAP, and the problem went away.

This issue just hit me on a Mac running Ventura 13.2 accessing a QNAP with NFS. Wound up with a stale NFS handle that would not go away despite reboots of both devices. 

To confirm, just logging into the server using ssh and doing

exportfs -ra

without anything else (no config changes, no playing with fsid, no other actions) made the problem go away.

Source Link
Dennis Simpson
Dennis Simpson
  • 1

Apologies for the necropost, but this issue just hit me on a Mac running Ventura 13.2 accessing a QNAP with NFS. Wound up with a stale NFS handle that would not go away despite reboots of both devices. To confirm, just logging into the server using ssh and doing exportfs -ra without anything else, no config changes, no playing with fsid, no other actions, just exportfs -ra on the QNAP, and the problem went away.