- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Correct use of NFS
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 06:47 AM
тАО09-20-2005 06:47 AM
Correct use of NFS
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 07:30 AM
тАО09-20-2005 07:30 AM
Re: Correct use of NFS
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 08:10 AM
тАО09-20-2005 08:10 AM
Re: Correct use of NFS
tcpip add export /disk/dir
On the client side: mount point is /disk/dir.
Unix fstab: node:/disk/dir:/mnt/vmsdir:rw:0:0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 09:16 AM
тАО09-20-2005 09:16 AM
Re: Correct use of NFS
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 01:21 PM
тАО09-20-2005 01:21 PM
Re: Correct use of NFS
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 05:59 PM
тАО09-20-2005 05:59 PM
Re: Correct use of NFS
Michael : not possible without a container ?
It's VMS to VMS.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 06:37 PM
тАО09-20-2005 06:37 PM
Re: Correct use of NFS
Create container wants to create the directory itself while it already exists.
I want to present an EXISTING directory !
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 07:12 PM
тАО09-20-2005 07:12 PM
Re: Correct use of NFS
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 .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2005 10:56 PM
тАО09-20-2005 10:56 PM
Re: Correct use of NFS
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 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-22-2005 01:52 AM
тАО09-22-2005 01:52 AM
Re: Correct use of NFS
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