[Info-vax] Problem with Multinet NFSMOUNT.

[Richard Whalen]

On Thursday, July 23, 2020 at 6:10:44 AM UTC-4, F.Zwarts wrote:
> We are still running an small cluster with VAX (VMS 7.3) and Alpha (VMS 
> 7.3-1) systems. 
> These systems run Multinet 5.0. 
> These systems mount an NFS file system on a Linux server. For more than 
> three years we did not reboot these system. 
> This week there was a power outage and all systems were restarted. Now 
> they fail to mount the NFS file system on the Linux server. 
> I hope that someone has seen this problem before and knows a work-around. 
> 
> Here is the command and the error message: 
> 
> $ NFSMOUNT /soft /timeout=100 /transport=(UDP,TCP) - 
> "unix-file.kvi.nl::/usr/local/kvi" UNIX_KVI /volume=UNIX_KVI - 
> /SEMANTICS=(NOVMS_ACCESS) 
> %NFSMOUNT-F-NONFSRESPONSE, NFS server on "unix-file.kvi.nl" not 
> responding: RPC: 
> Program/version mismatch; low version = 3, high version = 3 
> 
> (The error is immediate. There is no time-out of 10 seconds.) 
> 
> Other Linux systems have no problem to mount this NFS file system. 
> 
> The VMS systems have not been changed on the system level, so I suspect 
> that the Linux server has been upgraded several time in these years and 
> that now there is an incompatibility between the VMS Multinet client and 
> the Linux server. 
> The NFS server supports NFS version 3. Support for NFS version 4 is 
> disabled. 


MultiNet 5.0 only implemented NFS version 2.  MultiNet 5.5 has NFS 3 (client and server)
and there are a number of patches available to correct problems that were discovered as
more customers started using it.  NFS 3 is NOT available on VAX as VAX lacks the ability to
do a lot of the 64 bit arithmetic that is necessary for figuring out file offsets.