EPICS Re: Problem NFS mounting Centos 7 file systems from vxWorks 5.5

1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024	Index	1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024
<== Date ==>		<== Thread ==>

Found this in RTEMS-Maillist:

Message: 1
Date: Mon, 13 Jun 2016 14:33:23 +0200
From: Sebastian Huber <[email protected]>
To: Till Straumann <[email protected]>, RTEMS
<[email protected]>
Subject: Re: Standard RTEMS NFSv3 client now available via libbsd
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed

On 10/06/16 16:47, Till Straumann wrote:
> The client is V2, not V3.

Thanks for clarification, this explains why its necessary to enable a
legacy mode on one NFS server to be able to work with RTEMS clients.

>
> We have a low-priority project to add V3 but having a low priority I'm
> not sure if or when it's going to happen...

Another option would be to port the FreeBSD NFS client to RTEMS. For
this we need a FreeBSD kernel file system layer to RTEMS file system
layer adaptor.

>
> - Till
> On 06/10/2016 05:20 AM, Sebastian Huber wrote:
>> Hello,
>>
>> I imported a snapshot of the standard RTEMS NFSv3 client from Till
>> Straumann to the libbsd (the new network stack). The RPC deamon uses
>> a kqueue() instead of RTEMS events for synchronization. The zero-copy
>> optimization by means of direct usage of mbufs is currently not
>> available due to a lack of time and budget.
>>

--
Sebastian Huber, embedded brains GmbH

Heinz

On 19 January 2017 at 18:37:37, Andrew Johnson ([email protected]) wrote:

Calling all RTEMS developers (Till, Eric, Michael, Heinz): Given the
statement below from Red Hat, are there any plans in the works to
support NFSv3 or later on RTEMS, or some other modern network filesystem
protocol?

On 01/19/2017 10:42 AM, Torsten Bögershausen wrote:
> But I am afraid that NFS 2 is no longer supported:
> <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Storage_Administration_Guide/index.html#ch-nfs>

The RTEMS NFSv2 client does talk to our RHEL-7.3 server with the
configuration change I posted for Mark, but the VxWorks 5.4.2 NFS client
broke somewhere between the RHEL-7.2 and 7.3 servers. VxWorks 5.5 has an
NFSv3 client (which is buggy, make sure you get all the available
patches) that works OK against a RHEL-7.3 server.

The APS now only has *2* production IOCs left running on EPICS 3.13.10,
having upgraded the others to Base-3.14.12 and VxWorks 5.5 or 6.9. This
solved the NFSv2 issue for VxWorks, but our RTEMS-4.9.2 and 4.10.2
systems are still stuck with NFSv2...

- Andrew

--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

Subject:	Re: Problem NFS mounting Centos 7 file systems from vxWorks 5.5
From:	Heinz Junkes <[email protected]>
To:	Andrew Johnson <[email protected]>, [email protected]
Date:	Fri, 20 Jan 2017 11:30:51 +0100

Experimental Physics and Industrial Control System