Hi all,
For the boards I am using in my LAVA lab, if I try an NFS job on my jetson-tk1, it fails to mount the filesystem from the debian installed NFS server. http://lava.streamtester.net/scheduler/job/120050
my nfs-kernel-server version is 1:1.3.4-2.1, which was installed with LAVA from Debian Stretch.
If I add 'vers=3' to the kernel NFS command line, it mounts the filesystem successfully. http://lava.streamtester.net/scheduler/job/120049
This is being discussed here to make it a default option https://review.linaro.org/#/c/25666/
But really this does seem like there's an issue with the NFS kernel server in Debian Stretch. Has anyone else had this issue?
Matt
On 6 June 2018 at 16:19, Matt Hart matthew.hart@linaro.org wrote:
Hi all,
For the boards I am using in my LAVA lab, if I try an NFS job on my jetson-tk1, it fails to mount the filesystem from the debian installed NFS server. http://lava.streamtester.net/scheduler/job/120050
my nfs-kernel-server version is 1:1.3.4-2.1, which was installed with LAVA from Debian Stretch.
If I add 'vers=3' to the kernel NFS command line, it mounts the filesystem successfully. http://lava.streamtester.net/scheduler/job/120049
This is being discussed here to make it a default option https://review.linaro.org/#/c/25666/
There are devices which now appear to not support vers=3, using the same infrastructure.
Adding the review causes cubietrucks to fail with a jessie NFS: https://staging.validation.linaro.org/scheduler/job/221515#L261 and a stretch NFS (with stretch kernel, initramfs, modules and dtb) https://staging.validation.linaro.org/scheduler/job/221753#L265
Disabling vers=3 allows the stretch NFS to complete: https://staging.validation.linaro.org/scheduler/job/221754
This change was made in the device-type template by adding: {% set extra_nfsroot_args = extra_nfsroot_args|default('') %}
This option can also be specified in the job context.
I've also seen problems with QEMU NFS not working if vers=3 is set.
Please test your own instances by setting extra_nfsroot_args to ",vers=3" and checking that vers=3 occurs in the parsed boot commands. Due to how these commands need to be structured for the kernel to accept them, make sure the syntax is correct:
* first character MUST be a comma * no spaces, anywhere, in the value * If other options are also needed, vers=3 can appear anywhere as long as each value is comma separated with no spaces.
But really this does seem like there's an issue with the NFS kernel server in Debian Stretch. Has anyone else had this issue?
We'd really like to know what is going on here. Why would only certain device-types be affected if this is a host side issue? (Problem first appeared with Juno devices.)
Matt _______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users