unable to add shadow set member

[James Viswasam]

I am unable to add a shadow set member to an existing shadow set.

dsa4324 is a single member shadow set with member $1$dga4324.
I am adding disk $1$dga3324 as a second member.
I have checked size, limit etc..

VMS 8.3 , multinode cluster. Shadowing has been done on this cluster previously.

Please see the attachement.
Thanks in advance for your help.
James

[Jan van den Ende]

James,

can you MOUNT DGA3324 ?
And THEN post the output of
$ SHO DEV DGA3324/FULL ?
If you cannot MOUNT, then the MOUNT cammand + reply.

Proost.

Have one on me.

jpe

[The Brit]

Hi James,

I would also try doing an

$ init/sys/limit $1$dga3324: temp

this should set the Expansion Limit and the Logical Volume Size (which should be greater than the Total Blocks on dga4234).

then give it another twirl.

Dave.

[James Viswasam]

Disk $1$DGA3324: (Node1), device type HSV210, is online, allocated, deallocate
on dismount, mounted, file-oriented device, shareable, available to cluster,
device has multiple I/O paths, error logging is enabled.

Error count 0 Operations completed 17675
Owner process "JAVISWAS 0" Owner UIC [SYSTEM]
Owner process ID 2068B8E2 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 2 Default buffer size 512
Current preferred CPU Id 1 Fastpath 1
WWID 01000010:6005-08B4-0010-5366-0001-2000-0141-0000
Total blocks 125829120 Sectors per track 128
Total cylinders 7680 Tracks per cylinder 128
Logical Volume Size 125829120 Expansion Size Limit 2147475456
Allocation class 1

Volume label "TEST1" Relative volume number 0
Cluster size 96 Transaction count 1
Free blocks 125191200 Maximum files allowed 11069461
Extend quantity 5 Mount count 1
Mount status Process Cache name "_$1$DGA4323:XQPCACHE"
Extent cache size 75 Maximum blocks in extent cache 12519120
File ID cache size 68 Blocks in extent cache 0
Quota cache size 0 Maximum buffers in FCP cache 6210
Volume owner UIC [JAVISWAS] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-2, subject to mount verification, file high-water marking,
write-back caching enabled.

I/O paths to device 8

[James Viswasam]

Dave,

Yes, I tried that multiple times, after initializeing with different cluster sizes.

[John Gillings]

James,
From HELP/MESSAGE INCSHAMEM, here is the list of reasons:

o The shadow set is already fully populated.
o The device being added is not an MSCP device.
o The geometry or other hardware properties of the physical unit do not match those of the other shadow set members.
o The proposed shadow set member is the quorum disk.
o The physical unit is a member of another shadow set.
o The shadow set system disk has the SHADOW_SYS_DISK parameter set to 0 instead of to 1.

Some of those are discounted from what you've posted already, but please recheck them all.

I'd also sanity check your shadowing license. Is it AVAILABILITY or ACTIVITY based?

[Scott Vieth]

Hi James:

I noticed that the DSA device and the disk you are trying to add don't have the same number of blocks. I know this used to be a problem in the past. Was this restriction ever removed from VOLSHAD (I've been away from the VMS world for a few years)? If not, this may be the cause of your issue.

Thanks,
-Scott

[James Viswasam]

Scott, that is not an issue with the newer versions of VMS.

I found the problem with help from another VMS expert. THe LUN was not presented to all the nodes of the cluster and hence VMS would not allow me since it automagically mounts on all the nodes. ( that is very smart of VMS ! )
thanks you all guys,

[Robert Brooks_1]

I'd like to see the output from $ SHOW SHADOW /FULL for the virtual unit in question.

-- Rob

[James Viswasam]

I found the problem with help from another VMS expert. THe LUN from EVA was not presented to all the nodes of the cluster and hence VMS could not mount it on all nodes. That is the reason it prevented the shadow set as the disk was not available on all nodes ( that is very smart of VMS ! )
thanks to you all guys,
James