Re: Help with rtems nfs mounting

["Knap, Giles \(DLSLtd,RAL,LSCI\) via Tech-talk" <tech-talk at aps.anl.gov>]

Hi Chris,

Re RTEMS 6 and libbsd - there are some issues with using this on the M7400 processor we are using. Some of the folk in accelerator controls at DLS have been looking into resolving that. We are using your patched epics-base with legacy networking in the interim.

Cheers,

giles

---

From: Chris Johns <chris@contemporary.software>
Sent: 08 September 2024 22:19
To: Knap, Giles (DLSLtd,RAL,LSCI) <giles.knap at diamond.ac.uk>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>; Miceli, Antonino <amiceli at anl.gov>
Cc: Malowany, Alex (DLSLtd,RAL,LSCI) <alex.malowany at diamond.ac.uk>
Subject: Re: Help with rtems nfs mounting

 

[You don't often get email from chris@contemporary.software. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

On 7/9/2024 7:15 am, Knap, Giles (DLSLtd,RAL,LSCI) via Tech-talk wrote:
> I can't help with the debugging but I have made RTEMS5 and 6 connect to NFSv2
> using a user space NFSv2 driver running on RHEL8.
>
> At DLS we are still running RHEL 7 to serve NFSv2 to our VxWorks and RTEMS IOCs.
> However we have been looking to retire those servers.

RTEMS 6 with libbsd supports NFSv4.

Chris

>
> I have had success with the user space NFSv2 running in a container in
> Kubernetes. However you could also try compiling the driver natively using the
> steps in the Dockerfile. See epics-containers/nfsv2-tftp-server: User space
> NFSv2 and TFTP server for experimenting with RTEMS booting (github.com)
> <https://eur03.safelinks.protection.outlook.com/?url="">>
>
> Copying Alex: as you were planning to test switching on NFSv2 on RHEL8 I thought
> you might be interested to hear that there may be issues.
>
> Cheers,
> giles
> --------------------------------------------------------------------------------
> *From:* Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Miceli, Antonino
> via Tech-talk <tech-talk at aps.anl.gov>
> *Sent:* 06 September 2024 21:27
> *To:* tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
> *Subject:* Help with rtems nfs mounting
>
> Hi,
>
> I have some legacy rtems IOCs. I can't get the NFS mount to work after our IT
> upgraded to RHEL9. So, they setup an RHEL8 VM with nfs v2 activated.  They say
> it is working:
>
> [root@dplab ~]# mount -o vers=2 rtems-dserv:/xorApps  /mnt
> [root@dplab ~]# mount | grep mnt
> rtems-dserv:/xorApps on /mnt type nfs (rw,vers=2,addr=10.54.100.9)
>
> But not of the IOC below....
>
> Any advices on debugging this?
>
> B$ printenv
> FACTORY=Arcturus Networks Inc.
> REVISION=uC5282-16E16C64
> SERIAL=X4CB88918-01660
> CONSOLE=ttyS0
> KERNEL=0:linux.bin
> KERNEL_ARGS=root=/dev/mtdblock0 quiet
> HWADDR0=00:06:3b:01:36:60
> FW_VERSION=010809000
> RAMIMAGE=yes
> CACHE=on
> _0=10000000:400000:RW
> BOOTFILE=/xorApps/epics/synApps_5_3/ioc/dth/bin/RTEMS-uC5282/dthApp.boot
> CMDLINE=/xorApps/epics/synApps_5_3/ioc/dth/iocBoot/iocdth3/st.rtems.cmd
> NETMASK=255.255.255.0
> AUTOBOOT=20
> HOSTNAME=iocdth3
> IPADDR0=10.54.112.70
> GATEWAY=10.54.112.1
> NAMESERVER=10.54.100.9
> SERVER=10.54.100.9
> NTPSERVER=10.54.100.9
> NFSMOUNT=10.54.100.9:/xorApps:/xorApps
> B$ go!
> go!: command not found
> B$ go
> Copy...done
> go! 0x40000
>
> ***** Initializing network *****
> Startup after Software reset.
> fs1: Ethernet address: 00:06:3b:01:36:60
> ***** Initializing NFS *****
> This is RTEMS-RPCIOD Release $Name: rtems-addon-packages-4-7-1 $
> ($Id: rpcio.c,v 1.4 2006/08/30 13:52:10 joel Exp $)
>
> Till Straumann, Stanford/SLAC/SSRL 2002
> See LICENSE file for licensing info
> This is RTEMS-NFS Release $Name: rtems-addon-packages-4-7-1 $
> ($Id: nfs.c,v 1.3 2006/06/20 00:36:25 ericn Exp $)
>
> Till Straumann, Stanford/SLAC/SSRL 2002
> See LICENSE file for licensing info
> Trying to mount 10.54.100.9:/xorApps on /xorApps
> RPCIO: server '10.54.100.9' not responding - still trying
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
> ***** Initializing NTP *****
>     *************** WARNING ***************
>     ***** NO RESPONSE FROM NTP SERVER *****
>     *****  TIME SET TO DEFAULT VALUE  *****
>     ***************************************
> ***** Starting EPICS application *****
> #------------------------------------------------------------------------------
> # RTEMS startup file for the uCDIMM
> #------------------------------------------------------------------------------
> #------------------------------------------------------------------------------
> # NFS mount external file systems
> < ../nfsCommands
> #nfsMount s100dserv.xray.aps.anl.gov /APSshare /APSshare
> nfsMount rtems-dserv.xray.aps.anl.gov /APSshare /APSshare
> nfsMount: host 'rtems-dserv.xray.aps.anl.gov' not found
> #------------------------------------------------------------------------------
>
>
> Thanks,
> Nino
>
>
>
>
> This e-mail and any attachments may contain confidential, copyright and or
> privileged material, and are for the use of the intended addressee only. If you
> are not the intended addressee or an authorised recipient of the addressee
> please notify us of receipt by returning the e-mail and do not use, copy,
> retain, distribute or disclose the information in or attached to the e-mail. Any
> opinions expressed within this e-mail are those of the individual and not
> necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments
> are free from viruses and we cannot accept liability for any damage which you
> may sustain as a result of software viruses which may be transmitted in or with
> the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England and
> Wales with its registered office at Diamond House, Harwell Science and
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom.

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom.