HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Correct use of NFS

 
Wim Van den Wyngaert
Honored Contributor

Correct use of NFS

TCP 5.3. On system A I have a disk DISK with directory DIR. I want to NFS mount it on system B as "/export". System B may not know of DISK and DIR, only of /export.

What do I need to map/export/mount ?

(tried it for an hour and went crazy of the error messages, also crazy because operator.log is deferred write)

Wim
Wim
12 REPLIES
Uwe Zessin
Honored Contributor

Re: Correct use of NFS

No immediate idea on NFS, sorry, but an idea how to work around OPCOM's buffering:

if you send the '$REPLY/LOG' command, it looks like all buffers are flushed to the current OPERATOR.LOG before a new file is opened. You can then access the contents, e.g. with:

$ type/tail sys$manager:operator.log;-1
.
Joseph Huber_1
Honored Contributor

Re: Correct use of NFS

tcpip map /disk DISK:
tcpip add export /disk/dir

On the client side: mount point is /disk/dir.
Unix fstab: node:/disk/dir:/mnt/vmsdir:rw:0:0
http://www.mpp.mpg.de/~huber
Joseph Huber_1
Honored Contributor

Re: Correct use of NFS

Sorry, in my previous answer, the Unix style pathes /disk, /disk/dir must be enclosed in string quotes ("").

And: for root to access the VMS export, there must be a NFS proxy for /gid=/uid=0.
At least I don't know off hand how to specify non-root mounts.
http://www.mpp.mpg.de/~huber
Michael Yu_3
Valued Contributor

Re: Correct use of NFS

Hi Wim,

If system B is not to know about DISK and DIR, you may have to use the container file.

On system A:-

TCPIP> add proxy local_user /host=systemB /GID=gid /UID=uid/NFS=incoming
TCPIP> create container DISK:[DIR]/user=local_user/host=systemB
TCPIP> map "/disk" DISK:
TCPIP> map "/export" DISK:[DIR]
TCPIP> add export "/export"/host=systemB


On system B:-

TCPIP> add proxy local_user /host=systemA /GID=gid /UID=uid/NFS=outgoing
TCPIP> mount dnfs0: /host=systemA /path="/export"

Thanks and regards.

Michael
Wim Van den Wyngaert
Honored Contributor

Re: Correct use of NFS

Joseph : System B may not know of DISK and DIR, only of /export

Michael : not possible without a container ?

It's VMS to VMS.

Wim

Wim
Wim Van den Wyngaert
Honored Contributor

Re: Correct use of NFS

Michael,

Create container wants to create the directory itself while it already exists.
I want to present an EXISTING directory !

Wim
Wim
Joseph Huber_1
Honored Contributor

Re: Correct use of NFS

Wim, You are completely free to name the map as You like. But You can't map a subdirectory unless it is a container, that's what You don't want, You want to share the directory between systems A and B.
So, if You don't want to export the whole disk, there is no way around exporting the path to the particular directory.
Why can't the client system mount /export/dir ?
It is just the path in the mount command (or in the /etc/fstab entry).
If the other system is Unix, then You can choose any local mount point (the Unix directory to mount the export TO).
So the mount would be
A:/export/dir:/mnt/export
and the access on Unix to VMSs disk:[dir] would be /mnt/export .
http://www.mpp.mpg.de/~huber
Joseph Huber_1
Honored Contributor

Re: Correct use of NFS

Wim, now I see You have both sides VMS, so my Unix examples are irrelavant.

Would You explain, what "B knows only of /export, not DISK and DIR" really means ?

The NFS client MOUNT command has to know the exported path, wether it is /export or /export/dir. The tcpip mount command still can choose which local directory it mounts it on:
TCPIP MOUNT DNFSn: results in DNFSn:[000000] being the exported directory. The users never see what is behind /export/dir. If You want to hide [000000] then You can choose any "mount point" like
TCPIP MOUNT DNFSn:[systemA]

Or is Your problem with existing system-management (or whoever does the TCPIP MOUNT on B), which now mounts /export, and can't be asked to change ?
http://www.mpp.mpg.de/~huber
Wim Van den Wyngaert
Honored Contributor

Re: Correct use of NFS

Joseph,

I wanted clients to use a logical when mounting. This way I can move the files to other disks / directories without having to modify all 100 clients.

Wim
Wim
Joseph Huber_1
Honored Contributor

Re: Correct use of NFS

But then the solution is easy:

the clients mount command needs once and for all fix the mount path (or the logical name resulting in) to say "/export/dir".
There is to my knowledge no way around specifying a subdirectory: in Unix speech "/export" is a device path only, and TCPIP mount "speaks" Unix in this regard.

Then only the server side need to change when the disk/directory becomes different:

Map /export to the new disk.
Create a directory alias (or hardlink on ODS5 disks) [DIR] pointing to the new directory,
then "/export/dir" need not be changed at all, and all the clients can mount without changing a single character in the pathname.
http://www.mpp.mpg.de/~huber
Wim Van den Wyngaert
Honored Contributor

Re: Correct use of NFS

Ok J but I avoid hardlinks. I was searching for a pure tcpip thing (e.g. via mapping).

Wim
Wim
Jan van den Ende
Honored Contributor

Re: Correct use of NFS

Wim,

if I understand correctly, you want to be able to just use:

SOMEDIR:

as a directory spec?

In that case you CAN
$ DEFINE/SYSTEM/EXEC SOMEDIR DNFS:[topdir.subdir]
Then you just
We have been using it for some time (although it has been quite some time ago).

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.