NFS Client - Timed Out on Freenas 9.X

[Giuseppe Padilha]

Hi,

When used the FreeNAS server version 8.0.x, I could mount an NFS directory from an external HD normally.

After updating to version 9.x, I can't mount the external HD using NFS.

The error appears:
RPCPROG_MNT: RPC: Timed Out

Code:

[root@freenas] ~# showmount -e 172.16.0.2
Exports list on 172.16.0.2:
/DataVolume/BACKUP                *

Code:

[root@freenas] ~# mount -t nfs 172.16.0.2:/DataVolume/BACKUP /mnt/exthd
[tcp] 172.16.0.2:/DataVolume/BACKUP: RPCPROG_MNT: RPC: Timed out
[tcp] 172.16.0.2:/DataVolume/BACKUP: RPCPROG_MNT: RPC: Timed out

Code:

[root@freenas] ~# mount -t nfs -o user=admin,username=admin 172.16.0.2:/DataVolume/BACKUP /mnt/exthd
[tcp] 172.16.0.2:/DataVolume/BACKUP: RPCPROG_MNT: RPC: Timed out

Does anyone know how to solve?

Thank you!
Giuseppe Padilha

 

[Giuseppe Padilha]

Sorry, the third code is:

Code:

[root@freenas] ~# mount -t nfs -o user=admin,password=admin 172.16.0.2:/DataVolume/BACKUP /mnt/exthd
[tcp] 172.16.0.2:/DataVolume/BACKUP: RPCPROG_MNT: RPC: Timed out
[tcp] 172.16.0.2:/DataVolume/BACKUP: RPCPROG_MNT: RPC: Timed out

 

[dlavigne]

Code:

[root@freenas] ~# mount -t nfs -o user=admin,password=admin 172.16.0.2:/DataVolume/BACKUP /mnt/exthd

Just to be clear, is that -o or -o tcp ?

 

[Giuseppe Padilha]

Just to be clear, is that -o or -o tcp ?

I added the -o option just to inform that I tried to make the connection informing username and password.

But the NFS connection is via TCP.

Giuseppe

 

[dlavigne]

Does specifying -o tcp fix it?

 

[Giuseppe Padilha]

Does specifying -o tcp fix it?

I had already tested in other times, but tested again. But not resolved.

Also tested with UDP.

Code:

[root@freenas] ~# mount -o tcp 172.16.0.2:/DataVolume/BACKUP /mnt/exthd
[tcp] 172.16.0.2:/DataVolume/BACKUP: RPCPROG_MNT: RPC: Timed out
^C
[root@freenas] ~# mount -o udp 172.16.0.2:/DataVolume/BACKUP /mnt/exthd
[udp] 172.16.0.2:/DataVolume/BACKUP: RPCPROG_MNT: RPC: Timed out

Giuseppe

 

[Giuseppe Padilha]

Follow RPCINFO command of device (BlackArmor NAS 110):

Code:

[root@freenas] ~# rpcinfo -p 172.16.0.2
  program vers proto  port  service
    100000    2  tcp    111  rpcbind
    100000    2  udp    111  rpcbind
    100021    1  udp  32768  nlockmgr
    100021    3  udp  32768  nlockmgr
    100021    4  udp  32768  nlockmgr
    100003    2  udp  2049  nfs
    100003    3  udp  2049  nfs
    100021    1  tcp  36085  nlockmgr
    100021    3  tcp  36085  nlockmgr
    100021    4  tcp  36085  nlockmgr
    100003    2  tcp  2049  nfs
    100003    3  tcp  2049  nfs
    100005    1  udp    801  mountd
    100005    1  tcp    804  mountd
    100005    2  udp    801  mountd
    100005    2  tcp    804  mountd
    100005    3  udp    801  mountd
    100005    3  tcp    804  mountd

Giuseppe

 

[Giuseppe Padilha]

Dlavigne,


I tried with all the options available here and none of the options solved.

I'm thinking it's a NFS bug in this version of kernel used on this Freenas 9.2.
Giuseppe

 

[dlavigne]

In that case, please create a report at bugs.freenas.org and post the issue number here.

 

[Giuseppe Padilha]

Hi Dlavigne,

I created the ticket as you requested:
https://bugs.freenas.org/issues/3807

Thank you!
Giuseppe Paolo Fontana Padilha