According to your email, the following my comment may not be valid,
but better to check it out.
Do you enable firewall service? CentOS7 uses the NFSv4 as default as
Torsten mentioned, that use only 2049 port . With the firewall
commands as systemd's definition, you can open that port. However, NFSv3
uses the more than one port, and all ports are allocated when the
service is started dynamically. So, you have to define unused ports
manually before the NFSv3 service is started and open these ports later
(via systemd with firewalld or others... )
I hope it may help you to resolve that issue.
220.127.116.11. NFS Firewall Configuration
On 01/19/2017 02:00 AM, Mark Rivers wrote:
We are mostly running VxWorks 6.9.4 now, and with that we have no
problem NFS mounting file systems on Centos 7.
However, we have a few IOCs that still need to run VxWorks 5.5. These
can mount file systems on Centos 5 servers fine. However, on Centos 7
we see the following:
- The NFS mount command from vxWorks succeeds with no error
- showmount on the Centos 7 system shows that the vxWorks
system has mounted the file system OK
- However, the vxWorks system cannot actually read or write any
files on the file system.
If I type the “ls” command in a valid directory I get
Cant’ open “null”.
The problem is not file permissions, it works fine if we are running the
identical IOC with vxWorks 6.9.4, and we have tried setting the files in
that directory to mode 755.
Is anyone running vxWorks 5.5 with a Centos 7/ RHEL 7, etc. modern NFS
server? If so, how does one get it to work?
- Problem NFS mounting Centos 7 file systems from vxWorks 5.5 Mark Rivers
- Navigate by Date:
Re: Problem NFS mounting Centos 7 file systems from vxWorks 5.5 Torsten Bögershausen
RE: Problem NFS mounting Centos 7 file systems from vxWorks 5.5 Mark Rivers
- Navigate by Thread:
Re: Problem NFS mounting Centos 7 file systems from vxWorks 5.5 Jörn Dreyer
Problem compiling StreamDevice on Visual Studio 2015 Mark Rivers