Hi everyone, I'm implementing the nfsroot for my devices but it seems that when extracting my rootfs.tar.xz lava keep the parent folder rootfs and didn't extract all the files in extract-nfsrootfs-XXXXX so that the lava test overlay is putting outside of rootfs folder and raises an error during execution.
Is there a way in job definition to ask lava to put the test overlay in the rootfs folder ?
Thanks
Benjamin AUCLAIR
On 16 August 2017 at 09:50, Benjamin Auclair benjamin.auclair@devialet.com wrote:
Hi everyone, I'm implementing the nfsroot for my devices but it seems that when extracting my rootfs.tar.xz lava keep the parent folder rootfs
Do you mean that if you do:
tar -taf rootfs.tar.xz on the file before submission, that you get:
./bin/ ./usr/ ./lib/ ....
or do you get:
./target/bin/ ./target/usr/ ./target/lib/ ....
If you have a single folder inside the tarball which contains the rest of the rootfs then this is actually a broken NFS tarball - V1 used to work around it but the kernel will not be able to use it directly.
There is support for skipping a single top level directory in the NFS (to cover older test jobs which relied on the V1 workaround) using the prefix value.
nfsrootfs: url: http://images.validation.linaro.org/overdrive/linaro-jessie-developer-201601... compression: gz prefix: binary/
and didn't extract all the files in extract-nfsrootfs-XXXXX so that the lava test overlay is putting outside of rootfs folder and raises an error during execution.
Is there a way in job definition to ask lava to put the test overlay in the rootfs folder ?
The overlay will be unpacked into the top level directory of the rootfs - unless "prefix" is set.
All files for the NFS *MUST* be in the specified prefix directory - multiple nested directories are not supported, fix the NFS tarball.
Thanks
Benjamin AUCLAIR
- Confidential -
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users