RHEL6: NFS client rebooting due to hung_task timeouts due to one NFSv3 operation which is not completing

Solution Unverified - Updated -

Issue

  • NFS client hung_task panic / reboots due to process waiting on a mutex or other operation, which is held up by a second process which is waiting on a NFSv3 operation (such as a SETATTR, or a LOOKUP) to complete.
  • NFS client slowness or hanging, and we see nfs: server XYZ not responding messages in the log

Environment

  • Red Hat Enterprise Linux 6 (NFS client)
    • seen on kernel 2.6.32-279.11.1.el6, 2.6.32-431.el6
  • NFS
    • seen on NFSv3
  • Seen with NetApp (NFS server)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.