0

On NFS Server (CentOS):

[root@localhost ~]# cat /etc/exports

/IT_Projects 192.168.56.0/25(ro,root_squash)

eth1      Link encap:Ethernet  HWaddr 08:00:27:C4:A8:B6  
          inet addr:192.168.56.101  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fec4:a8b6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1790 errors:0 dropped:0 overruns:0 frame:0
          TX packets:230 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:252381 (246.4 KiB)  TX bytes:27381 (26.7 KiB)

On NFS Client (CentOS):

 eth1      Link encap:Ethernet  HWaddr 08:00:27:C4:A8:B6  
              inet addr:192.168.56.102  Bcast:192.168.56.255  Mask:255.255.255.0
              inet6 addr: fe80::a00:27ff:fec4:a8b6/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:1609 errors:0 dropped:0 overruns:0 frame:0
              TX packets:145 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:231539 (226.1 KiB)  TX bytes:11555 (11.2 KiB)


[root@localhost ~]# mount -t nfs4 192.168.56.101:/IT_Projects /mnt/proj

results in connection timeout.

[root@localhost ~]# dmesg | tail
sf_read_super_aux err=-71
sf_read_super_aux err=-71
sf_read_super_aux err=-71
fuse init (API version 7.16)
FS-Cache: Loaded
FS-Cache: Netfs 'nfs' registered for caching
EXT3-fs (sdc2): error: no journal found. mounting ext3 over ext2?
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period

[root@localhost ~]# ping 192.168.56.102
PING 192.168.56.102 (192.168.56.102) 56(84) bytes of data.
64 bytes from 192.168.56.102: icmp_seq=1 ttl=64 time=0.422 ms

Can ping the client from the server.

I have turned SELinux off, and started the rpcbind, nfs, daemons on both NFS client and server. I also changed Defvers=3 in /etc/nfsmount.conf on the Server to no effect. What other avenues can I explore to fix the problem?

    [root@localhost ~]# rpcinfo -p 192.168.56.101
rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host

[root@localhost IT_Projects]# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTABLISHED 
ACCEPT     icmp --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp dpt:ssh 
REJECT     all  --  anywhere             anywhere            reject-with icmp-host-prohibited 

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
REJECT     all  --  anywhere             anywhere            reject-with icmp-host-prohibited 

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination 
  • Can the server itself mount the filesystem via NFS? – Mark Plotnick Oct 5 '14 at 16:54
  • 1
    What does rpcinfo -p server_ip_address on the client show? – Mark Plotnick Oct 5 '14 at 16:57
  • @MarkPlotnick do you mean can the server act as both client and server? If so yes, mount -t nfs4 192.168.56.101:/IT_Projects /mnt/IT_Projects works. Received this error on client: rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host – user Oct 5 '14 at 19:46
  • 1
    iptables -L unfortunately doesn't show the interfaces that the rule applies to. iptables -L -v will. The second ACCEPT all -- anywhere anywhere rule you have may actually be ACCEPT all -- lo any anywhere anywhere, meaning it only applies to input from the loopback interface. – Mark Plotnick Oct 6 '14 at 22:55
  • 1
    Working on it... need to research how to set up NFSv4. – Mark Plotnick Oct 15 '14 at 14:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.