Description of problem:

rpc.statd doesn't work when a host does not have rdns when mounting by ip address.

Version-Release number of selected component (if applicable):

nfs-utils-1.2.2-7

How reproducible:

Very.

Steps to Reproduce:
1. mount nfs server by ip address, eg, mount 172.16.255.14:/export /nfs/export
  
Actual results:

Locking does not work:

May 25 21:12:15 a rpc.statd[5850]: No canonical hostname found for 172.16.255.14
May 25 21:12:15 a rpc.statd[5850]: STAT_FAIL to a for SM_MON of 172.16.255.14
May 25 21:12:15 a kernel: lockd: cannot monitor 172.16.255.14

Expected results:

That locking would work.  Just like it is has in previous releases when just mounting by IP address where there are no reverse dns records.

Additional info:

It can easily be worked around by adding entries in /etc/hosts but this isn't expected behavior and could lead to confusion and issues including potential data corruption if the statd errors go unobservered when migrating from earlier releases.

This Debian bug report appears to be for the same issue.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579397