Article 145337 of comp.os.vms:

In article <01I3RLV2BJHU00075M@meadow.meto.govt.uk>, "Mike Glover (Head of Computing, MRF)" <mjglover@meto.govt.uk> writes:
|>>Does any one know how to persuade VMS that a disk which it has timed out
|>>verifing is actually back online and ready for operation. For example if
|>>a node in a cluster drops and the other nodes timeout the disk's that the node
|>>was serving. How do you inform the other nodes that the disks are available
|>>again.
|>>
|>>
|>>Jason Simmons
|>>-------------------------------------------------------------------------------
|>>
|>>Jsimmons@hns.com
|>
|>There are two ways that I know of. The manual and the automatic.
|>
|>The manual way is:-
|>
|>$ mcr sysman
|>SYSMAN> set e/c
|>SYSMAN> do dismount disk
|>
|>$ mount/sys/cluster disk lab log
|>
<snip>

You do need to dismount the disk on each of the machines, but you
need to do it with the options /override=checks/abort --

   dismount/override=check/abort $5$dka0: 

You need to do this on each machine that has the disk mounted
as MountVerifyTimeout. You can do this through SYSMAN..

Then you can do a mount/cluster on one machine, and it will become
available to the entire cluster again.

Robin E. Shahan
resh@chevron.com
My opinions, not Chevron's.
The brain is a wonderful organ. It starts working the moment you get up
and does not stop until you get into the office. --Robert Frost