Comment 21 for bug 1037192

I can confirm this problem on Precise 12.04.3 with mountall=2.36.4 from precise-updates.

With clientaddr=0.0.0.0, nfsstat -s showed rapidly incrementing 'setcltid' and 'setcltidconf' operations on the server, and high IO utilization on the root volume due to writing v4recovery information.

Although I am not certain on this part, shortly after performing updates on three clients which bumped mountall to 2.36.4, our NFS server crashed after 300 days of uptime less than 24 hours later. ( Don't have much data here, but it was brought down due to an OOM condition, I'm assuming due to a memory leak somewhere in the NFS code. This server is used exclusively for NFS, and no user-land process was to blame. )

Reverting mountall to 2.36 and rebooting restored a properly configured clientaddr, and the excessive client ID operations stopped.

Changes in mountall 2.36.1 and 2.36.2 both seem highly suspicious, see LP #643289 and LP #1078926.