NFS becomes unresponsive after nfsd errors related to TCP shutting down socket

Solution Verified - Updated -

Issue

  • After a few minutes of seeing errors about NFS scrolling on the console, the system becomes unresponsive
  • Following error messages are observed on NFS client
kernel: nfs: server server.hostname not responding, still trying
kernel: nfs: server server.hostname OK
  • And following error messages are observed on NFS server.
kernel: rpc-srv/tcp: nfsd: got error -104 when sending 140 bytes - shutting down socket

Environment

  • Red Hat Enterprise Linux 5 with RPM nfs-utils older than 1.0.9-47.
  • Red Hat Enterprise Linux 6 and higher

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content