[Info-vax] Cluster node fails to boot from shadow-set member

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Wed Apr 17 14:02:24 EDT 2019


On 2019-04-17 16:54:07 +0000, Richard B said:

> I think I'm going to go along with Volker's suggestion: one which I had 
> contemplated anyway.
> On Node 1 I'm going to have an HBVS two-disk system disk - 
> DSA0:/shadow=($1$dka1:,$1$dka2:)
> On Node 2 I'm going to have an HBVS two-disk system disk - 
> DSA1:/shadow=)$2$dka1:,$2$dka2:)

Parenthetical typo aside, I'd avoid using allocation classes 1 and 2 
here and in general, as those two allocation classes are (also) used 
(and are required) by FC disk and tape storage, and there's no way to 
change that allocation class usage.  That's not a problem now. But 
that's a problem if (when?) FC storage arrives here. Best to avoid that 
usage.

> I think this should work.  However it will require more maintenance on 
> my part as far as the UAFs and RIGHTSLIST are concerned.

Once you get the files shared, there's no difference.

Get one OpenVMS system installed, with nothing else configured or 
added.  Use the files from that installation as your start for the 
common area.

Getting the logical names configured to reference the shared file is an 
utter and unmitigated and hilarious disaster of a user interface and 
the printed documentation here has been problematic for decades, 
but—following SYLOGICALS.TEMPLATE—it does work.

> What do you think?

No sé.  No quiero saber.  No necesito saber.

> PS:  Yes, the P410i controllers in each of the rx2800 i2's are in RAID 
> mode but I think I'm going to go with the HBVS for the system disks in 
> lieu of, say, RAID 1.  Just a personal preference I suppose.

I'd usually use the hardware RAID.  Just personal preference.  One less 
thing to mess with "upstairs" in OpenVMS, and I don't need to contend 
with host-based RAID-1 and a system disk.


-- 
Pure Personal Opinion | HoffmanLabs LLC 




More information about the Info-vax mailing list