NFS not work ?

Status
Not open for further replies.

5m1l3

Cadet
Joined
Sep 21, 2014
Messages
9
I have two FreeNAS boxes with 9.2.1.7. Boxes clear installed. (not upgraded)
And i cant mount this nfs from ubuntu (12.04 and 14.04), rpcbind and nfsd at server started.
When i try to mount it:

mount -t nfs 192.168.110.251:/mnt/safe1 /mnt/net
It's just hangup for long time, and after it show mount timeout.

When i do showmount -e 192.168.110.251 (my freenas box)
it hangup for long time, but give me exports list:

root@nfsclient:~# showmount -e 192.168.110.251
Export list for 192.168.110.251:
/mnt/safe1 192.168.110.0


If i from this client try mount another nfs share from test linux box, everything work fine and fast. All boxes in one subnet, all firewalls disabled. I tried to add host name to hosts file for server and client.

Help, help!!! :(

Some info from 192.168.110.251 serverside :

[root@nas2] ~# ps auxc|grep nfsd
root 7668 0.0 0.1 9900 1840 ?? Is 2:08PM 0:00.01 nfsd
root 7669 0.0 0.1 9900 1668 ?? I 2:08PM 0:00.00 nfsd

[root@nas2] ~# ps auxc | grep rpc
root 7629 0.0 0.1 14124 1996 ?? Ss 2:08PM 0:00.01 rpcbind
root 7693 0.0 0.1 274144 1896 ?? Ss 2:08PM 0:00.00 rpc.statd
root 7725 0.0 0.1 14120 1924 ?? Ss 2:08PM 0:00.00 rpc.lockd

[root@nas2] ~# cat /etc/exports
/mnt/safe1 -alldirs -network 192.168.110.0/24

[root@nas2] ~# showmount -e localhost
Exports list on localhost:
/mnt/safe1 192.168.110.0

[root@nas2] ~# rpcinfo -p localhost
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100000 4 local 111 rpcbind
100000 3 local 111 rpcbind
100000 2 local 111 rpcbind
100005 1 udp 795 mountd
100005 3 udp 795 mountd
100005 1 tcp 795 mountd
100005 3 tcp 795 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100024 1 udp 815 status
100024 1 tcp 815 status
100021 0 udp 958 nlockmgr
100021 0 tcp 959 nlockmgr
100021 1 udp 958 nlockmgr
100021 1 tcp 959 nlockmgr
100021 3 udp 958 nlockmgr
100021 3 tcp 959 nlockmgr
100021 4 udp 958 nlockmgr
100021 4 tcp 959 nlockmgr

Serverside TCPdums:

After run at client root@nfsclient:~# mount -t nfs 192.168.110.251:/mnt/safe1 /mnt/net/

[root@nas2] ~# tcpdump -vv host 192.168.110.248
tcpdump: listening on re0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:25:04.043141 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has nfsclient tell w8.lan, length 46
14:26:56.256932 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has nas2 tell nfsclient, length 46
14:26:56.256942 ARP, Ethernet (len 6), IPv4 (len 4), Reply nas2 is-at f4:ec:38:80:cb:82 (oui Unknown), length 28
14:27:07.420471 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has nfsclient tell w8.lan, length 46


After run at client root@nfsclient:~# showmount -e 192.168.110.251
Export list for 192.168.110.251:
/mnt/safe1 192.168.110.0

[root@nas2] ~# tcpdump -vv host 192.168.110.248
14:27:49.712755 IP (tos 0x0, ttl 64, id 43734, offset 0, flags [DF], proto UDP (17), length 84)
nfsclient.850 > nas2.sunrpc: [udp sum ok] UDP, length 56
14:27:49.712838 IP (tos 0x0, ttl 64, id 32526, offset 0, flags [none], proto UDP (17), length 56)
nas2.sunrpc > nfsclient.850: [udp sum ok] UDP, length 28
14:28:25.793118 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has nas2 tell nfsclient, length 46
14:28:25.793128 ARP, Ethernet (len 6), IPv4 (len 4), Reply nas2 is-at f4:ec:38:80:cb:82 (oui Unknown), length 28
14:28:57.856967 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has nas2 tell nfsclient, length 46
14:28:57.856976 ARP, Ethernet (len 6), IPv4 (len 4), Reply nas2 is-at f4:ec:38:80:cb:82 (oui Unknown), length 28
14:29:56.977477 IP (tos 0x0, ttl 64, id 43735, offset 0, flags [DF], proto UDP (17), length 84)
nfsclient.850 > nas2.sunrpc: [udp sum ok] UDP, length 56
14:29:56.977535 IP (tos 0x0, ttl 64, id 44841, offset 0, flags [none], proto UDP (17), length 56)
nas2.sunrpc > nfsclient.850: [udp sum ok] UDP, length 28
14:29:56.977835 IP (tos 0x0, ttl 64, id 43736, offset 0, flags [DF], proto UDP (17), length 104)
nfsclient.850 > nas2.951: [udp sum ok] UDP, length 76
14:29:56.978231 IP (tos 0x0, ttl 64, id 44842, offset 0, flags [none], proto UDP (17), length 104)
nas2.951 > nfsclient.850: [udp sum ok] UDP, length 76





 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
I know one thing that helped me on a direct link NFS connection was adding a host entry for my NFS client machine on freenas. not sure if that helps you
 

5m1l3

Cadet
Joined
Sep 21, 2014
Messages
9
It was a firmware trouble with Cisco SG200-08 switch. Solution downgrade firmware to 1.0.5.1. In any firmware greater than 1.0.5.1 NFS not work, cisco dont resolve trouble.
 

Havoc70

Dabbler
Joined
Mar 27, 2015
Messages
13
How did you downgrade the firmware? I'm having this exact same problem, exact same switches. Though I'm on this version of firmware and still having this problem. Guess I'll try a different switch.
 
Status
Not open for further replies.
Top