I have two NFS clients mounted to an openfiler 2.99 NFS share at 192.0.2.3:192.0.2.1 mounts 192.0.2.3:/mnt/nfs01/volnfs01/share01 with rw,noatime,nodiratime,hard,rsize=32768,wsize=32768,noacl,nocto,tcp,nfsvers=3192.0.2.1 mounts 192.0.2.3:/mnt/nfs01/volnfs01/share02 with rw,noatime,nodiratime,hard,rsize=32768,wsize=32768,nfsvers=3,tcp,noacl,nocto192.0.2.2 mounts 192.0.2.3:/mnt/nfs01/volnfs01/share02 with rw,noatime,nodiratime,hard,rsize=32768,wsize=32768,nfsvers=3,tcp,noacl,noctotouch brokenMy problem is with 192.0.2.2's NFS mount.  When I touch a file in on that mount, the process hangs indefinitely... I used strace touch /mnt/share02/this and got this far...rt_sigaction(SIGRTMIN, {0x3b71c05ae0, [], SA_RESTORER|SA_SIGINFO, 0x3b71c0f500}, NULL, 8) = 0rt_sigaction(SIGRT_1, {0x3b71c05b70, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x3b71c0f500}, NULL, 8) = 0rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0getrlimit(RLIMIT_STACK, {rlim_cur=10240*1024, rlim_max=RLIM_INFINITY}) = 0brk(0)                                  = 0xafb000brk(0xb1c000)                           = 0xb1c000open(/usr/lib/locale/locale-archive, O_RDONLY) = 3fstat(3, {st_mode=S_IFREG|0644, st_size=99158576, ...}) = 0mmap(NULL, 99158576, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fce244c0000close(3)                                = 0open(/mnt/share02/this, O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK, 0666                                                                    ^^^ stops touching                                                                     |                                                                     |When I check ps -elf from another terminal, I see the process in D state...[mpenning@host192_0_2_2 ~]$ ps -elf | awk '$2==D'0 D mpenning  8157  8032  0  80   0 - 26293 rpc_wa 09:59 pts/2    00:00:00 touch /mnt/share02/this[mpenning@host192_0_2_2 ~]$showmount isn't finding a problem though....[mpenning@host192_0_2_2 ~]$ showmount -e 192.0.2.3Export list for 192.0.2.3:/mnt/nfs01/volnfs01/share01 192.0.2.2/255.255.255.255,192.0.2.1/255.255.255.255/mnt/nfs01/volnfs01/share02 192.0.2.2/255.255.255.255,192.0.2.1/255.255.255.255[mpenning@host192_0_2_2 ~]$Various status of NFS services...[mpenning@host192_0_2_2 ~]$ service nfs statusrpc.svcgssd is stoppedrpc.mountd (pid 9168) is running...nfsd (pid 9232 9231 9230 9229 9228 9227 9226 9225) is running...rpc.rquotad (pid 9164) is running...[mpenning@host192_0_2_2 ~]$ service rpcbind statusrpcbind (pid  9088) is running...[mpenning@host192_0_2_2 ~]$ service nfslock statusrpc.statd (pid  9256) is running...[mpenning@host192_0_2_2 ~]$Network configuration (default gw isn't required since this is a dedicated layer2 NFS vlan):[mpenning@host192_0_2_2 ~]$ sudo cat /etc/sysconfig/network-scripts/ifcfg-eth1DEVICE=eth1NM_CONTROLLED=noONBOOT=yesBOOTPROTO=noneIPADDR=192.0.2.2NETMASK=255.255.255.0DNS2=noneTYPE=EthernetGATEWAY=DNS1=noneIPV6INIT=noUSERCTL=noMTU=9000[mpenning@host192_0_2_2 ~]$This looks pretty nasty.  I have done the following on 192.0.2.2:Restarted all NFSinit 6 the machineping 192.0.2.3 to make sure it still has connectivity to the serverChecked dmesgChecked showmount -e 192.0.2.3This feels like a permissions problem, but I don't know where to go from here...How can I fix this problem so I can read / write to any file on 192.0.2.2's mount of 192.0.2.3:/mnt/nfs01/volnfs01/share02?touch worksIf I execute the same touch command from 192.0.2.1, everything is fine...rt_sigaction(SIGRTMIN, {0xb096e0, [], SA_SIGINFO}, NULL, 8) = 0rt_sigaction(SIGRT_1, {0xb09b80, [], SA_RESTART|SA_SIGINFO}, NULL, 8) = 0rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0getrlimit(RLIMIT_STACK, {rlim_cur=10240*1024, rlim_max=RLIM_INFINITY}) = 0uname({sys=Linux, node=host192_0_2_1.localdomain.local, ...}) = 0brk(0)                                  = 0x8d4d000brk(0x8d6e000)                          = 0x8d6e000open(/usr/lib/locale/locale-archive, O_RDONLY|O_LARGEFILE) = 3fstat64(3, {st_mode=S_IFREG|0644, st_size=99158544, ...}) = 0mmap2(NULL, 2097152, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7574000close(3)                                = 0open(/mnt/share02/this, O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK|O_LARGEFILE, 0666) = 3dup2(3, 0)                              = 0close(3)                                = 0utimensat(0, NULL, NULL, 0)             = 0close(0)                                = 0close(1)                                = 0close(2)                                = 0exit_group(0)                           = ?/etc/exports from 192.0.2.3[root@T1-Netfile01 backups]# head /etc/exports# PLEASE DO NOT MODIFY THIS CONFIGURATION FILE!#       This configuration file was autogenerated#       by Openfiler. Any manual changes will be overwritten#       Generated at: Fri Nov 8 9:35:39 CST 2013/mnt/nfs01/volnfs01/share02 192.0.2.1/255.255.255.255(rw,anonuid=96,anongid=96,secure,root_squash,wdelay,sync)  192.0.2.2/255.255.255.255(rw,anonuid=96,anongid=96,secure,root_squash,wdelay,sync)/mnt/nfs01/volnfs01/share01 192.0.2.1/255.255.255.255(rw,anonuid=96,anongid=96,secure,root_squash,wdelay,sync)  192.0.2.2/255.255.255.255(rw,anonuid=96,anongid=96,secure,root_squash,wdelay,sync)[root@T1-Netfile01 backups]#
Hang during 'touch' operation on NFS mount
filesystems;files;nfs
And if you change the order of the IPs in the /etc/exports file what happens then? Put the .2.2 IP 1st and the .2.1 2nd.Also I would confirm what the exports are presenting as using the command:$ showmount -e 192.0.2.3/etc/exports can be very particular about the formatting!Other things to tryI typically specify my hosts in the /etc/exports like this:/cobbler/isos   192.168.1.0/24(rw,no_root_squash)So for you with a single host IP:/mnt/nfs01/volnfs01/share02 192.0.2.1/32(rw,anonuid=96,anongid=96,secure,root_squash,wdelay,sync)  192.0.2.2/32(rw,anonuid=96,anongid=96,secure,root_squash,wdelay,sync)/mnt/nfs01/volnfs01/share01 192.0.2.1/32(rw,anonuid=96,anongid=96,secure,root_squash,wdelay,sync)  192.0.2.2/32(rw,anonuid=96,anongid=96,secure,root_squash,wdelay,sync)nfs related servciesMake sure that nfslock and other related services are both running on 192.0.2.2.If you're using jumbo frames, be sure that ping -s <jumbo_mtu> 192.0.2.3 works from 192.0.2.2