strange disk states

I'll post another message about the ultimate cause of the problem.
Right now, I'm wondering how one member of DSA510: can be a copy target
and the other member in the "merging" status. Shouldn't either no or
both members be in the "merging" status? Or will first a copy happen
then a merge? (I'll have to wait about 10 hours to find out. We plan
to move next spring; maybe that will be a chance for me to get some
faster hardware.)

The disk appears to work fine from all nodes.

GLADIA is an ALPHA; DANEEL and ELIJAH are VAXes. DANEEL has been acting
strange lately, but this time ELIJAH was too. I tried a shutdown on
ELIJAH, which hung. Couldn't get a prompt on the DANEEL console, so did
a reset, as on ELIJAH. Both hung. Only after a power cycle did they
come back up. I didn't reboot GLADIA.

The strange status of DSA510: is the same on all nodes. Now, a few
minutes later, $22$DKA500: is showing 1% copied. The only difference is
that $22$DKA400: is in MntVerifyTimeout only on DANEEL; a MOUNT fixed
that. Otherwise all the disks look as expected.

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$22$DKA200: (DANEEL) ShadowCopying 0 (copy trgt DSA520: 0% copied)
$22$DKA300: (DANEEL) ShadowMergeMbr 0 (merging DSA122: 66% merged)
$22$DKA400: (DANEEL) MntVerifyTimeout 0 OVMSDOC071 61179 1 3
wrtlck
$22$DKA500: (DANEEL) ShadowCopying 0 (copy trgt DSA510: 0% copied)
$22$DKA700: (DANEEL) ShadowMergeMbr 0 (merging DSA122: 66% merged)
$33$DKA200: (GLADIA) Online 0
$33$DKA300: (GLADIA) ShadowSetMember 36 (member of DSA520:)
$33$DKA400: (GLADIA) Online wrtlck 0
$33$DKB100: (GLADIA) ShadowMergeMbr 0 (merging DSA133: 90% merged)
$33$DKB600: (GLADIA) ShadowMergeMbr 0 (merging DSA133: 90% merged)
$44$DKA100: (ELIJAH) ShadowMergeMbr 0 (merging DSA144: 76% merged)
$44$DKA200: (ELIJAH) Mounted 0 SCRATCH_4 168837 2 3
$44$DKA300: (ELIJAH) Mounted 0 DATA 1907185 1 3
$44$DKA400: (ELIJAH) ShadowMergeMbr 0 (merging DSA510: 0% merged)
$44$DKA600: (ELIJAH) ShadowMergeMbr 0 (merging DSA144: 76% merged)
$131$DKA300: (NADILA) HostUnavailable 0
$131$DKA500: (NADILA) HostUnavailable 0

For completeness:

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA122: Mounted 0 OVMSVAXSYS_2 2139480 347 3
DSA133: Mounted 0 ALPHASYS_3 1934613 1 3
DSA144: Mounted 0 OVMSVAXSYS_4 2060704 1 3
DSA510: Mounted 0 USER 5533721 219 3
DSA520: Mounted 0 SOFT 514653 9 3

.

Relevant Pages

  • Re: strange disk states
    ... I'm wondering how one member of DSA510: ... and the other member in the "merging" status. ... DANEEL and ELIJAH are VAXes. ...
    (comp.os.vms)
  • Re: strange disk state
    ... Gladia or Elijah? ... The strange disk is on DANEEL. ... DANEEL and GLADIA had the ... DISK$USER shadow set has 2 members, one with a direct connection to ...
    (comp.os.vms)