[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference spezko::cluster

Title:+ OpenVMS Clusters - The best clusters in the world! +
Notice:This conference is COMPANY CONFIDENTIAL. See #1.3
Moderator:PROXY::MOORE
Created:Fri Aug 26 1988
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5320
Total number of notes:23384

5253.0. "Host shadow between 2 different SCSI adapters KZPSC" by COWBOY::MIRGHANE () Thu Mar 13 1997 11:13

    A customer is encountering problems try to " Host Based Shadow" 2
    RZ28D-VW on a AlphaServer1000A:
    - One RZ28D-VW is connected to the Integral FWD SCSI of the Server
    - The second is connected to a KZPSC controller in an external BA356
    
    The error message is : IMC-SHAMEM "incompatible shadow set member"
    
    Lookind at the SPD of Volume Shadowing I do not see any restriction 
    regarding the nature of the SCSI adapters.
    
    
    Is there any? 
    
    If not How can the customer solve this problem?
    
    
    Thanks for a quick help.
    
    Best regards.
    Soumetty.
T.RTitleUserPersonal
Name
DateLines
5253.1EEMELI::MOSEROrienteers do it in the bush...Thu Mar 13 1997 11:363
    you mean he is trying to shadow a DR device with a DK device?
    
    /cmos
5253.2EVMS::MORONEYThu Mar 13 1997 12:049
re .1:

If the disk geometry is the same it can be done.

re .0:

Do a $SHOW DEVICE/FULL of the two devices.

-Mike
5253.3The 2 disks do not appear with the same typeCOWBOY::MIRGHANEThu Mar 13 1997 13:0891
    
    
    
    re .1 et .2
    
    
    Here are the 2 device descriptions. I have the feeling that the
    custommer  cannot
    shadow them because the 2 disks are not of the same type and do not
    present the same Total blocks.
    So the question is: Is there a way to configure the KZPSC so as to
    have the RZ28D be considered as of type RZ28D whith the correct size?
    
    
    Soumetty
    
    
    
    
    
                                   
Disk $3$DRA2: (MDHS1), device type 1 Member JBOD, is online, mounted, file-
============================================
    oriented device, shareable, available to cluster, error logging is enabled.

    Error count                    0    Operations completed               6013
    Owner process                 ""    Owner UIC                      [SYSTEM]
    Owner process ID        00000000    Dev Prot            S:RWPL,O:RWPL,G:R,W
    Reference count               15    Default buffer size                 512
    Total blocks             4110336    Sectors per track                    64
    Total cylinders             4014    Tracks per cylinder                  16
    Allocation class               3

    Volume label       "MDHS1_DISK4"    Relative volume number                0
    Cluster size                   4    Transaction count                    15
    Free blocks               268052    Maximum files allowed            411033
    Extend quantity                5    Mount count                           1
    Mount status              System    Cache name          "_$3$DKA0:XQPCACHE"
    Extent cache size             64    Maximum blocks in extent cache    26805
    File ID cache size            64    Blocks currently in extent cache      0
    Quota cache size             157    Maximum buffers in FCP cache        774
    Min ret. period  180-00:00:00.00    Max ret. period         181-00:00:00.00
    Volume owner UIC        [SYSTEM]    Vol Prot    S:RWCD,O:RWCD,G:RWCD,W:RWCD

  Volume Status:  subject to mount verification, write-back caching enabled.

MDHS1>SYSTEM> sh dev /full $3$dka100
====================================
Disk $3$DKA100: (MDHS1), device type DEC RZ28D, is online, mounted, file-
    oriented device, shareable, available to cluster, error logging is enabled.

    Error count                    0    Operations completed              51003
    Owner process                 ""    Owner UIC                      [SYSTEM]
    Owner process ID        00000000    Dev Prot            S:RWPL,O:RWPL,G:R,W
    Reference count               59    Default buffer size                 512
    Total blocks             4110480    Sectors per track                    86
    Total cylinders             2988    Tracks per cylinder                  16
    Allocation class               3

    Volume label       "MDHS1_DISK1"    Relative volume number                0
    Cluster size                   9    Transaction count                    40
    Free blocks              2495016    Maximum files allowed            411033
    Extend quantity                5    Mount count                           1
    Mount status              System    Cache name          "_$3$DKA0:XQPCACHE"
    Extent cache size             64    Maximum blocks in extent cache   249501
    File ID cache size            64    Blocks currently in extent cache   1971
    Quota cache size             157    Maximum buffers in FCP cache        774
    Min ret. period  180-00:00:00.00    Max ret. period         181-00:00:00.00
    Volume owner UIC        [SYSTEM]    Vol Prot    S:RWCD,O:RWCD,G:RWCD,W:RWCD

  Volume Status:  subject to mount verification, write-back caching enabled.


RFC-822-headers:
Received: from mail.vbo.dec.com (mail.vbo.dec.com)
 by vbemdf.vbe.dec.com (PMDF V5.0-7 #16475)
 id <[email protected]> for
 [email protected]; Thu, 13 Mar 1997 18:47:13 +0100 (CET)
Received: from server21.digital.fr (server21.digital.fr [193.56.15.21])
 by mail.vbo.dec.com (8.7.3/8.7) with ESMTP id SAA22312 for
 <[email protected]>; Thu, 13 Mar 1997 18:48:55 +0100 (MET)
Received: from red.cegelec-red.fr (redgw.cegelec-red.fr [192.93.31.114])
 by server21.digital.fr (8.7.5/8.7) with ESMTP id SAA24051 for
 <[email protected]>; Thu, 13 Mar 1997 18:51:32 +0100 (MET)
Received: from eret.cegelec-red.fr ([159.217.74.2])
 by red.cegelec-red.fr (8.8.3/8.6.12) with SMTP id SAA26662 for
 <[email protected]>; Thu, 13 Mar 1997 18:39:34 +0100 (MET)
Received: from VAX01.DECnet MAIL11D_V3 by eret.cegelec-red.fr
 (5.57/Ultrix3.0-C) id AA00565; Thu, 13 Mar 1997 18:36:41 +0000 (GMT)
    
5253.4EVMS::MORONEYThu Mar 13 1997 14:188
You guess correctly that the disks cannot be shadowed due to different
characteristics (block count, sectors, tracks, cylinders).

I do not know the KZPSC but I've heard of something called "transparent mode"
which presents the disk exactly as it is, perhaps this is what you need to
find the correct configuration parameters in the documentation.
If you can convince the KZPSC to pass on the disk's characteristics exactly,
you can shadow it to the other one.
5253.5FWIW, HSZ40 transportable disks and shadowing60326::KAGEYAMATrust, but VerifyThu Mar 13 1997 23:5011
>I do not know the KZPSC but I've heard of something called "transparent mode"
>which presents the disk exactly as it is, perhaps this is what you need to
>find the correct configuration parameters in the documentation.

I'm not sure about KZPSC case, but transportable disks attached to HSZ40
are not recommended for shadow set members because they loose READ_LONG/
WRITE_LONG capabilities which are necessary for certain error corrections.
This is mentioned in OpenVMS V7.1 Release Notes p.4-39.

- Kazunori