On the client (as root):
| Practice | Why It Helps | |----------|---------------| | | Most mature, fewer unsupported ops. | | Keep kernel & nfs-utils in sync on client/server | Error 45 often appears after partial updates. | | Test new mount options with -o noac,vers=4.2 first | Exposes unsupported features early. | | Use nfsstat regularly | nfsstat -c -v shows per-operation error counts. | | When upgrading servers, enable debugging | echo 32767 > /proc/sys/sunrpc/rpc_debug (temporary). | Conclusion: Your "NFS VLTED 45" Checklist The phrase "nfs vlted 45 work" may be awkward and misspelled, but it points to a real, solvable issue: NFSv4.1+ returning ENOTSUP (Error 45) for unsupported operations.
apt-get install --install-recommends linux-generic-hwe-16.04 A specific bug that caused error 45 on READDIR with pNFS was fixed in . Check your version:
Look for: NFS: v4 server returned error -45 on operation X . If error 45 appears with vers=4.2 or vers=4 , downgrade to a lower version:
, your server lacks NFSv4.1/4.2 support. Permanently fix by updating /etc/fstab :
The fix? VMware ESXi’s NFS client defaults to NFSv4.1. The NetApp filer was still on NFSv4.0. Error 45 appeared due to unsupported RECLAIM_COMPLETE operation.
uname -r If < 4.15, upgrade or disable pNFS with -o nopnfs . When the basic steps fail, get surgical. Use tcpdump to see the actual NFS call that returns error 45 .
Leading oil companies have used our pipe systems for more than 40 years to transport oil, gas (LPG, LNG) and fuels. As a result, our pipes are used and prove their reliability every day at over 25,000 filling stations and tank facilities.