| Title: | VAX and Alpha VMS |
| Notice: | This is a new VMSnotes, please read note 2.1 |
| Moderator: | VAXAXP::BERNARDO |
| Created: | Wed Jan 22 1997 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 703 |
| Total number of notes: | 3722 |
I installed today VAXCLUSIO01_062 patch onto OpenVMS V6.2 system. Remounting device on to a shadow set behaves a bit stranglely. $ sho dev dk Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt $1$DKA100: (HSKRTR) ShadowSetMember 0 (member of DSA0:) $1$DKA200: (HSKRTR) Online 0 $1$DKA300: (HSKRTR) ShadowMergeMbr 0 (merging DSA1: 10% merged) $1$DKA400: (HSKRTR) ShadowMergeMbr 0 (merging DSA1: 10% merged) $1$DKA500: (HSKRTR) Online wrtlck 0 $ mount/sys dsa0/shadow=$1$Dka200 sts_hskrtr %MOUNT-I-MOUNTED, STS_HSKRTR mounted on _DSA0: %MOUNT-I-SHDWMEMCOPY, _$1$DKA200: (HSKRTR) added to the shadow set with a copy o peration %MOUNT-I-ISAMBR, _$1$DKA100: (HSKRTR) is a member of the shadow set $ sho dev dsa0 Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DSA0: Mounted 0 SYS_HSKRTR 364959 606 1 $1$DKA100: (HSKRTR) ShadowSetMember 0 (member of DSA0:) $1$DKA200: (HSKRTR) ShadowCopying 0 (copy trgt DSA0: 0% copied) The problem is that I accidentally typed $ mount/system dsa0/shadow=$1$dka200 STS_HSKRTR i.e. specifying WRONG volume label. I would have expected some kind "WRONG volume mounted" behaviour like in other system not yet having ALPCLUSIO patch: $ sho dev dsa100 Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DSA100: Mounted 0 AXPSYS 1322032 894 1 $2$DKA0: (AKSELI) ShadowSetMember 0 (member of DSA100:) $ mount/Sys dsa100/shadow=$2$DKB0: jfhgd %%%%%%%%%%% OPCOM 13-APR-1997 15:31:35.94 %%%%%%%%%%% Message from user KORKKO on AKSELI device contains the wrong volume %MOUNT-I-OPRQST, device contains the wrong volume %%%%%%%%%%% OPCOM 13-APR-1997 15:31:35.95 %%%%%%%%%%% Request 1, from user KORKKO on AKSELI Please mount volume JFHGD in device
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 456.1 | After ALPCLUSIO patch similar wrong behaviour | VELI::KORKKO | Veli K�rkk� @FNO, 879-5512 | Sun Apr 13 1997 15:00 | 8 |
Just verified that xxxCLUSIO01_062 patch really changes MOUN/SYS
../SHADow behaviour. The very same system in .0 giving WRONGVOL
opcom request now nicely mounts the $2$DKB0 to shadow set DSA100
wven if I specify wrong volume label in the command.
IPMT time?
_veli
| |||||
| 456.2 | known problem | VMSSG::FRIEDRICHS | Ask me about Young Eagles | Mon Apr 14 1997 10:51 | 18 |
This is a known problem in MOUNT96. There are actually 2 variations
of this.... One on the local system as you saw, and one where the
member will fail on the local node, but still be added on another
node in the cluster that has the shadow set mounted...
They are QARs EVMS-RAVEN 874 and 875.
While the behavior is different from previous versions of MOUNT, and
while yes, the data on that disk is gone, it would have been copied
over anyways had it been added to the correct shadow set. There are
also lots of other ways with shadowing that typos can cause a disk
to be added to the wrong set.
I hope to restore these checks in RAVEN and a future TIMA kit.
Cheers,
jeff
| |||||