Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU.UUCP
Newsgroups: comp.os.vms
Subject: Re: cluster disk mounts
Message-ID: <870617193955.01n@CitHex.Caltech.Edu>
Date: Wed, 17-Jun-87 23:27:01 EDT
Article-I.D.: CitHex.870617193955.01n
Posted: Wed Jun 17 23:27:01 1987
Date-Received: Sat, 20-Jun-87 06:51:16 EDT
References: <8706121732.AA04967@ncsc.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 35


 > I have two VAXes, and one HSC50 in a homogeneous cluster.  Connected to the
 > HSC50  I  have  RA81's  and  RA60's.   I would like to be able to mount the
 > RA60's as /SYSTEM/CLUSTER, but I would also link  to  be  able  to  inquire
 > about   the   the   volume   name   before   doing   it.   I  know  how  to
 > mount/override=id,  check   the   volume   name   with   f$getdvi,   do   a
 > dismount/nounload, and then do a MOUNT/SYSTEM/CLUSTER.  However If the disk
 > is already mounted with /cluster on one vax, when the second vax  tries  to
 > mount/override,  it can't reach the disk.  It there a way around this?  Any
 > help will be greatly appreciated.

I'll assume that MOUNT/FOREIGN has the same problem as  MOUNT/OVERRIDE=ID;  if
not,  use  that  instead, since it still reads the volume name.  Since you say
"Any help will be appreciated", I'll assume you're willing to accept inelegant
solutions.   If  this  is the case, one way you can get the volume information
you want (assuming you have DECnet) is to ask the machine you suspect has  the
volume  mounted,  by  running  a  network  job.  The following is a very crude
example:
    First create a file containing something like:
        $ DEFINE SYS$OUTPUT SYS$NET:
        $ SHOW DEVICES D/MOUNTED
        $ DEASSIGN SYS$OUTPUT
    and assign it a logical name short enough that its length and  the  length
    of  your  node's name add up to less than 10 (since you're allowed only 12
    characters in a DECnet object name; in my example, I use the logical  name
    "X").  Then initiate the network job with a command something like:
        $ TYPE target::"0=mynode::X:"
    where target is the node with the disk already mounted, and mynode is  the
    current node.
Yes, I know it's clumsy, but it does get you the information you need.

							-Carl J Lydick
BITnet:							CARL@CITHEX
ARPAnet:						CARL@CITHEX.CALTECH.EDU
HEPnet/EUROHEPnet/SPAN:					CITHEX::CARL