NFS between a RedPitaya board and an Ubuntu PC

Just about everything about Red Pitaya
Post Reply
lago113
Posts: 1
Joined: Tue Jun 20, 2017 7:50 pm

NFS between a RedPitaya board and an Ubuntu PC

Post by lago113 » Tue Jul 04, 2017 9:49 pm

I tried to configure a NFS server with my Red Pitaya board, exactly as this page tells me to https://www.digitalocean.com/community/ ... untu-16-04. However when I try to mount my directories on my Client I got this error:

# sudo mount 10.30.xx.xxx:/var/nfs/general /nfs/general
mount.nfs: Protocol not supported

Where 10.30.xx.xxx is my Host's IP. I googled this error and found that executing this command in my Host should tell me the allowed Protocols of my NFS service, but I got his:

# rpcinfo 10.30.xx.xxx |egrep "service|nfs"
program version netid address service owner
100003 2 tcp 0.0.0.0.8.1 nfs superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
100003 4 tcp 0.0.0.0.8.1 nfs superuser
100003 2 udp 0.0.0.0.8.1 nfs superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
100003 4 udp 0.0.0.0.8.1 nfs superuser
100003 2 tcp6 ::.8.1 nfs superuser
100003 3 tcp6 ::.8.1 nfs superuser
100003 4 tcp6 ::.8.1 nfs superuser
100003 2 udp6 ::.8.1 nfs superuser
100003 3 udp6 ::.8.1 nfs superuser
100003 4 udp6 ::.8.1 nfs superuser

So I used the next command to use NFS 2, and got the next problems

# mount -o rw,vers=2 10.30.xx.xxx:/var/nfs/general /nfs/general
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: mounting 10.30.44.197:/var/nfs/general failed, reason given by server: No such file or directory

I don't know how to proceed, anyone can help?

Thanks a lot in advance

njoshi
Posts: 1
Joined: Thu Jun 07, 2018 10:12 am

Re: NFS between a RedPitaya board and an Ubuntu PC

Post by njoshi » Fri Jun 08, 2018 3:55 pm

Hi,
I am facing the same problem.
# mount 1**.***.***.***:/path_to_source_dir/ /media/target_dir/
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: mounting 148.79.232.43:/home/njoshi/data/work/Shared_Daresbury/ failed, reason given by server: No such file or directory

# mount -o nolock 1**.***.***.***:/path_to_source_dir/ /media/target_dir/
mount.nfs: Protocol not supported

# service rpcbind status
● rpcbind.service - RPC bind portmap service
Loaded: loaded (/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
Drop-In: /run/systemd/generator/rpcbind.service.d
└─50-rpcbind-$portmap.conf
Active: active (running) since Fri 2018-06-08 14:05:50 UTC; 41min ago
Main PID: 1932 (rpcbind)
CGroup: /system.slice/rpcbind.service
└─1932 /sbin/rpcbind -f -w

rp-f0526f systemd[1]: Starting RPC bind portmap service...
rp-f0526f rpcbind[1932]: cannot get local address for udp: Servname not supported for ai_socktype
rp-f0526f rpcbind[1932]: cannot get local address for tcp: Servname not supported for ai_socktype
rp-f0526f rpcbind[1932]: cannot get local address for udp6: Servname not supported for ai_socktype
rp-f0526f rpcbind[1932]: cannot get local address for tcp6: Servname not supported for ai_socktype
rp-f0526f systemd[1]: Started RPC bind portmap service.
rp-f0526f systemd[1]: Started RPC bind portmap service.
rp-f0526f systemd[1]: Started RPC bind portmap service.

Post Reply
jadalnie klasyczne ekskluzywne meble wypoczynkowe do salonu ekskluzywne meble tapicerowane ekskluzywne meble do sypialni ekskluzywne meble włoskie

Who is online

Users browsing this forum: No registered users and 2 guests