OpenVMS 7.3-2 - Shadow Sets

[Kevin Raven (UK)]

I have a OpenVMS 7.3-2 server.
Very simple setup.
Single ES45 server
Single two member shadow set

DSA1 = DKB0 + DKB100

Added third disk into shadow set.
DSA1 = DKB0 + DKB100 + DKB300
Shadow set fully formed.
Shutdown OpenVMS to SRM prompt. With 3 members in shadow set DSA1:

Pull third disk (DKB300) from drive cage.
(Will be using this disk to boot and build another Standalone server ...not on network).

The observation is that when you boot ...
The boot hangs for a couple of mins and then you get an error message regarding DSA1: ...and boot continues with DSA1 as a single member shadow set.
DSA1 = DKB0
o.k. ....it cant find DKB300 ...but why kick out poor old DKB100 from the shadow set ?

On reboot logged in and added DKB100 back into shadow set.

Comments.

[Andy Bustamante]

What is the mount command for DSA1 ?

Is DSA1 the system disk? Is DSA1 dismounted during shutdown?

Andy Bustamante

[Volker Halle · Accepted solution]

Kevin,

assuming DSA1: is the system disk...

The system should have hung for about SHADO_SYS_TMO seconds before continuing with a reduced shadowset. Only DKB300 should have been thrown out of the shadowset.

Are you current of SHADOWING patches ? Please check ERRLOG.SYS entries from the boot. SYS$SHDRIVER should have written errlog-entries when removing disks from a shadowset.

Volker.

[Volker Halle]

sorry: SHADOW_SYS_TMO

[Kevin Raven (UK)]

The shadow set is the System disk.
Shadow set forms on boot
I.E. DSA1 = DKB0 + DKB100

Third member was added with following command:
$mount/sys/shadow=$1$dkb300: system

I get the following errors in the error log file (During boot process).
Remember I shutdown the server to the >>> SRM prompt. Pulled the third disk and then rebooted.
289 , 290 ,
291 and
292 Asynchronous Device Attention 28-JAN-2008 14:59:56.83

And

293 , 294 and
295 Device Timeout

Patch levels as below ....
$ product show hist
----------------------------------- ----------- ----------- --------------------
PRODUCT KIT TYPE OPERATION DATE AND TIME
----------------------------------- ----------- ----------- --------------------
DEC AXPVMS TCPIP_ECO V5.4-155 Patch Install 23-JUL-2007 11:50:22
DEC AXPVMS VMS732_UPDATE V8.0 Patch Install 23-JUL-2007 11:46:49
DEC AXPVMS VMS732_PCSI V3.0 Patch Install 23-JUL-2007 11:43:00
CPQ AXPVMS CDSA V2.0-109 Full LP Install 23-JUL-2007 11:30:52
DEC AXPVMS DECNET_PHASE_IV V7.3-2 Full LP Install 23-JUL-2007 11:30:52
DEC AXPVMS OPENVMS V7.3-2 Platform Install 23-JUL-2007 11:30:52
DEC AXPVMS TCPIP V5.4-15 Full LP Install 23-JUL-2007 11:30:52
DEC AXPVMS VMS V7.3-2 Oper System Install 23-JUL-2007 11:30:52
HP AXPVMS KERBEROS V2.0-6 Full LP Install 23-JUL-2007 11:30:52
----------------------------------- ----------- ----------- --------------------

9 items found

Of course the answer is apply the latest update patch and see if still does it :-)

[Volker Halle]

Kevin,

the shadowing driver should write specific errlog entries, if something 'unexpected' happens. I would need to have a look at the DECevent output of those errors.

You could also mail me the binary ERRLOG.SYS extract (please see my ITRC profile).

Volker.

[Dave Gudewicz]

Kevin,

Updates for VMS 7.3-2 are now up to v14 as of 5-DEC-2007 and therein lies a shadow patch (v6) dated 8-NOV-2007.

I would recommend installing the v6 shadow patch.