mount.nfs4 gives invalid argument

This forum is for topics dealing with problems with software specifically in the AArch64 repo.

mount.nfs4 gives invalid argument

Postby risto3 » Thu Jan 05, 2017 5:03 am

NFS server: Linux sarchx64 4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016 x86_64 GNU/Linux
(+ another one running linux-lts)
NFS client: Linux odroid-001e06337421 3.14.79-14-ARCH #1 SMP PREEMPT Sat Dec 10 11:42:30 MST 2016 aarch64 GNU/Linux

On the server every thing seems fine:
$this->bbcode_second_pass_quote('', '
')richard@sarchx64:/home/richard$ sudo mount.nfs4 -vv sarchx64.local:/export/pub /mnt
mount.nfs4: timeout set for Thu Jan 5 05:57:57 2017
mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.0.2,clientaddr=192.168.0.2'
richard@sarchx64:/home/richard$ mount |grep mnt
sarchx64.local:/export/pub on /mnt type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.2,local_lock=none,addr=192.168.0.2)
richard@sarchx64:/home/richard$ sudo umount /mnt
richard@sarchx64:/home/richard$ sudo mount.nfs4 -vv -o vers=4.2 sarchx64.local:/export/pub /mnt
mount.nfs4: timeout set for Wed Jan 4 19:37:39 2017
mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.0.2,clientaddr=192.168.0.2'
richard@sarchx64:/home/richard$ mount |grep mnt
sarchx64.local:/export/pub on /mnt type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.2,local_lock=none,addr=192.168.0.2)
richard@sarchx64:/home/richard$ sudo umount /mnt
richard@sarchx64:/home/richard$ sudo mount.nfs4 -vv -o vers=4 sarchx64.local:/export/pub /mnt
mount.nfs4: timeout set for Wed Jan 4 19:37:53 2017
mount.nfs4: trying text-based options 'vers=4,addr=192.168.0.2,clientaddr=192.168.0.2'
richard@sarchx64:/home/richard$ mount |grep mnt
sarchx64.local:/export/pub on /mnt type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.2,local_lock=none,addr=192.168.0.2)
richard@sarchx64:/home/richard$ sudo umount /mnt


but on the odroid-c2 client:
$this->bbcode_second_pass_quote('', '
')[root@odroid-001e06337421 ~]# mount.nfs4 -vv -o vers=4.2 sarchx64.local:/export/pub /mnt
mount.nfs4: timeout set for Wed Jan 4 19:42:25 2017
mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.0.2,clientaddr=192.168.0.35'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: an incorrect mount option was specified
[root@odroid-001e06337421 ~]# mount.nfs4 -vv -o vers=4 sarchx64.local:/export/pub /mnt
mount.nfs4: timeout set for Wed Jan 4 19:42:33 2017
mount.nfs4: trying text-based options 'vers=4,addr=192.168.0.2,clientaddr=192.168.0.35'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: an incorrect mount option was specified
[root@odroid-001e06337421 ~]# mount.nfs4 -vv sarchx64.local:/export/pub /mntmount.nfs4: timeout set for Wed Jan 4 19:42:38 2017
mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.0.2,clientaddr=192.168.0.35'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.0.2,clientaddr=192.168.0.35'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: trying text-based options 'vers=4.0,addr=192.168.0.2,clientaddr=192.168.0.35'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: trying text-based options 'addr=192.168.0.2'
mount.nfs4: prog 100003, trying vers=3, prot=6
mount.nfs4: trying 192.168.0.2 prog 100003 vers 3 prot TCP port 2049
mount.nfs4: prog 100005, trying vers=3, prot=17
mount.nfs4: trying 192.168.0.2 prog 100005 vers 3 prot UDP port 20048
[root@odroid-001e06337421 ~]# mount |grep mnt
sarchx64.local:/export/pub on /mnt type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.2,mountvers=3,mountport=20048,mountproto=udp,local_lock=none,addr=192.168.0.2)


it appears nothing but nfs3 mounts correctly...

noticed something similar here: http://forums.funtoo.org/topic/885-nfs- ... g-on-boot/
where the conclusion seemed to be that the kernel wasn't configured for nfs4+...

If that's the case here, can this be remedied
risto3
 
Posts: 44
Joined: Wed Aug 31, 2016 2:32 pm

Re: mount.nfs4 gives invalid argument

Postby moonman » Sun Jan 08, 2017 9:30 am

Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3387
Joined: Sat Jan 15, 2011 3:36 am

Re: mount.nfs4 gives invalid argument

Postby risto3 » Wed Jan 18, 2017 8:11 am

okay, then I guess I'll see if I can glean more info this weekend...
in the meanwhile I have another issue seemingly involving nfs and pcmanfm, but I'll create a new thread for that.
cheers
risto3
 
Posts: 44
Joined: Wed Aug 31, 2016 2:32 pm

Re: mount.nfs4 gives invalid argument(server sidezfs/nfs4 is

Postby risto3 » Wed Jan 18, 2017 10:51 am

Argg, seems this is more or less a server-side zfsonlinux issue where the translation to the linux syntax only does a half-arsed job (in terms of v4), necessitating redoing everything and declaring the nfs shares instead in /etc/exports. :evil:
I was able to jerry rig an nfs4 mount finally on the odroid-c2 to confirm that indeed v4 is correctly there.
cheers
risto3
 
Posts: 44
Joined: Wed Aug 31, 2016 2:32 pm


Return to ARMv8

Who is online

Users browsing this forum: Google [Bot] and 16 guests