NFS mount not working for ODS-5 disk using OpenVMS 8.2 Alpha

[Ken Englander]

I am not able to successfully export a directory on an ODS-5 disk on OpenVMS 8.2 Alpha. If I add the map to the permanent configuration, then restart NFS I get the following error in the SYS$SYSDEVICE:[TCPIP$NFS]TCPIP$MOUNTD_.LOG file.

ERROR: stat: no such file or directory, Cannot stat

I am not having any problem with exports for ODS-2 disks.

I have 3 ODS-5 disks and have the same problem on all of them.

The following patches are the only ones installed other than base 8.2.

TCPIP V5.5-11ECO1
VMS82A_UPDATE V5.0
VMS82A_PCSI V1.0

Is this a known issue? Is anyone able to do this successfully?

Thanks!

Ken

[Hoff]

NFS is supposed to work with ODS-5.

What's the particular mount point specification? Does the target exist? Might there be a local logical name not visible to the NFS server, possibly?

Here's some tips from a previous posting:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=984439

I'd start with all of the mandatory ECOs. There's a C ECO with some fixes to statvfs around filename parsing which might -- emphasis on might -- be related here. (There are a selection of OpenVMS system crashes fixed by various of the ECO kits, too.)

[Brian Reiter · Accepted solution]

Have your tried specifying name_conversion in the /OPTIONS field when specifying the export?

[Ken Englander]

I reviewed the current patch list posted on the ITRC site. There are only a few mandatory patches missing and none of them seem like they would be related. Nevertheless, I will install them so everything is up to date.

I have not tried using the NAME_CONVERSION option. I did using CASE_SENSITIVE, but that does not make any difference.

[Hoff]

The reasons for the application of ECOs is as much to speed the process through a formal HP Services report as to find and resolve the known bugs -- that, and some of the lower-level bugs that get ECO'd can show up in some really weird ways.

[Ken Englander]

The NAME_CONVERSION option was required to fix this problem.