[Info-vax] WRONGVU

[Stephen Hoffman]

On 2019-07-04 21:19:11 +0000, Phillip Helbig (undress to reply said:

> %MOUNT-F-WRONGVU, device is already a member of another virtual unit
> ...
> Why haven't I seen this before?

You have seen this exact error before.  On at least two occasions.

https://groups.google.com/d/msg/comp.os.vms/QWA1zkBVLXc/ZI6ZwWUeDAAJ
https://groups.google.com/d/msg/comp.os.vms/sGIlWnxA8Pc/KNIYwMToA4EJ

Canonical description of the underlying OpenVMS bug from a yet-earlier 
discussion:
https://groups.google.com/d/msg/comp.os.vms/CNb44Zcx3Fg/2JB1HTcEGTcJ

Once you're into this path, you're left to experiment and let us know 
what happens.  Either to wait for the copy to complete and can then 
attempt to mount the volume elsewhere, or to wait for the copy to 
complete, dismount everywhere, and then re-mount.  I'd expect the 
latter to be required, once things are stuck.  I would not expect a 
reboot to be necessary.

I've gotten burned by MOUNT /CLUSTER often enough that I don't use that 
qualifier anymore. A locally-tweaked fork of the provided MSCPMOUNT.COM 
example is a hack-ish option and a variant of what I do use with 
OpenVMS, and which also addresses other issues that MOUNT /CLUSTER does 
not and cannot.

Alas, OpenVMS lacks any sort of a storage logical volume manager.  The 
Linux LVM-related bits are rather capable, too.   
https://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)


-- 
Pure Personal Opinion | HoffmanLabs LLC