nfsclient rtems6 rtems-libbsd
Heinz Junkes
junkes at fhi-berlin.mpg.de
Wed Mar 16 15:00:32 UTC 2022
Hello,
I am trying the nfs-client with rtems6 and rtems-libbsd.
(on BSP “beatnik”)
I have not analyzed everything yet.
I just wanted to ask if, and how, someone has already managed it?
When I call mount_and_make_target_path().
rval = mount_and_make_target_path(dev, mntpoint,
RTEMS_FILESYSTEM_TYPE_NFS, RTEMS_FILESYSTEM_READ_WRITE,
mount_options);
and take as mount_options "nfsv2" comes this:
Mount 141.14.131.192:/Volume on /Volume
nfs: mount: nfs -> 141.14.131.192:/Volume (nfsv2)
nfs: mount: [tcp] 141.14.131.192:/Volume: RPCPROG_NFS: RPC: Port mapper failure - RPC: Server can't decode arguments
as mount_options "nfs3" comes that:
Mount 141.14.131.192:/Volume on /Volume
nfs: mount: nfs -> 141.14.131.192:/Volume (nfsv3)
nfs: mount: [tcp] 141.14.131.192:/Volume: RPCPROG_NFS: RPC: Port mapper failure - RPC: Server can't decode arguments
mount: 5: I/O error
as mount_options "nfsv4,minorversion=1" comes that:
Mount 141.14.131.192:/Volume on /Volume
nfs: mount: nfs -> 141.14.131.192:/Volume (nfsv4,minorversion=1)
nfs: mount args: 8
16 addr=10 02 08 01 8d 0e 83 c0 00 00 00 00 00 00 00 00
0 nfsv4
8 dirpath=/Volume
4 fstype=nfs
7 fspath=Volume
23 hostname=141.14.131.192:/Volume
0 rw
2 minorversion=1
nfs: mount: (2) No such file or directory
mount: 2: No such file or directory
Is it generally the case that the nfs cannot mount a subdir with the rtems-libbsd?
i.e.
Mount 141.14.131.192:/Volumes/Epics on /Volumes/Epics
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
More information about the devel
mailing list