RE: Problem NFS mounting Centos 7 file systems from vxWorks 5.5

[Mark Rivers <rivers@cars.uchicago.edu>]

Folks,

This is a follow-up with the resolution to this problem.

The problem was resolved by fixing the Analogic DVX-2503 driver (drvDvx.c) so that it no longer generates interrupt errors on the MVME2100 with vxWorks 6.9.4.  Andrew fixed the problem, which was the need for a final read operation at the end of the Interrupt Service Routine.  So we no longer have a need for VxWorks 5.5, and hence no need to support NFSv2 on Centos 7.

Thanks Andrew!

Mark


-----Original Message-----
From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Mark Rivers
Sent: Thursday, January 19, 2017 12:01 PM
To: 'Andrew Johnson'; tech-talk@aps.anl.gov
Subject: RE: Problem NFS mounting Centos 7 file systems from vxWorks 5.5

Hi Andrew,

Good news and bad news.

The good news is that by booting vx55 with -asd8 I can mount NFS on our Centos7 server without changing its NFS configuration.

The bad news is that by changing from -asd7 to -asd8 we introduce the uninitialized interrupt messages from our Analogic DVX-2503 cards.

These messages do not happen on:

MVME5100 with VxWorks 5.5 or 6.9.4
MVME2100 with VxWorks 5.5 -asd7

They do occur with:
MVME2100 with VxWorks 6.9.4 or 5.5 -asd8.

Is anyone else using Analogic DVX-2503 cards with VxWorks?  If so, what version of VxWorks?

Thanks,
Mark



-----Original Message-----
From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Andrew Johnson
Sent: Thursday, January 19, 2017 11:36 AM
To: tech-talk@aps.anl.gov
Subject: Re: Problem NFS mounting Centos 7 file systems from vxWorks 5.5

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