Disk compatibility with VMS

[owilliams]

I have 50GB Luns that is OPEN-V is this compatible with VMS?

[Hein van den Heuvel]

So you are using XP-storage? Or Hitachy?
Should work.

There is an active discussion in this forum which is probably of interest to you:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1139926


Also:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1137513

Finally there is the support statement in:

http://h71000.www7.hp.com/openvms/roadmap/openvms_roadmaps_files/openvms_roadmaps_notes.pdf


So why are you asking?
'Just' planning or is there something that does not work for you?

What seems to be the problem? Specific errors? Intermediate displays you can attach as a text file?

Cheers,
Hein.

[owilliams]

One of our disk is running low on space and we were planning on adding this as a solution. What do you think?

[Volker Halle]

Is the 'disk that is getting full' also a SAN disk ($1$DGAx) ? And part of a shadowset ? If so, are you ready for DDS and DVE ?

Do you have other 'OPEN-V' disks in use on that system ?

Volker.

[owilliams]

Yes it is a SAN disk.

[Volker Halle]

Your SAN controller may offer the functionality of increasing the size of a disk 'on-the-fly'. An EVA (HSV) can do this.

If you're running at least OpenVMS V7.3-2, you could use DVE (Dynamic Volume Expansion) to also increase the size of your OpenVMS disk in the running system. Check with SHOW DEV/FULL $1$DGAx: for the Expansion Size Limit of that disk. You can expand a disk up to that limit online with SET VOL/SIZE, once you've increased the size of the underlying disk.

If your disk has not been set up for DVE, you can do this with SET VOL/LIMIT, but this requires that you need to privately mount that disk, so you need to temporarily dismount it (cluster-wide) for this operation.

For a recent discussion about DVE, see this topic:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1139928

Volker.

[owilliams]

Our storage people have added the disk. How can I verify that it was added correctly?

[Volker Halle · Accepted solution]

Can you already see the new SAN disk as $1$DGAnnn: ? Has it been presented to your OpenVMS System ?

$ MCR SYSMAN IO AUTO/LOG

Does it discover the new disk ? If so, INIT the disk with a scratch label and try to mount it.

Volker.

[owilliams]

Here is the output:
%SYSMAN-I-OUTPUT, command execution on node NRCAVA
%IOGEN-I-PREFIX, searching for ICBM with prefix SYS$
%IOGEN-I-PREFIX, searching for ICBM with prefix DECW$
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKA0
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port PGA0
%IOGEN-I-CONFIGURED, configured device DGA1550
%IOGEN-E-LOADERR, error configuring device OHA0, driver SYS$OHCIDRIVER.EXE
-RMS-E-FNF, file not found
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port PGB0
%IOGEN-F-FTLIOERR, fatal I/O error while trying to access device
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port PGC0
%IOGEN-I-CONFIGURED, configured device DGA1550
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKB0

[Volker Halle]

So the new disk seems to be DGA1550.
Try MOUNT/FOR $1$DGA1550: first to see, if you can do IOs to that disk. It should mount with an empty label - that way you know, that this disk has never been initialized on OpenVMS.

Then

$ DISM $1$DGA1550:
$ INIT $1$DGA1550: scratch/LIMIT
$ MOUNT $1$DGA1550: scratch
$ SHOW DEVICE/FULL $1$DGA1550:

check the expected size

$ ANAL/DISK $1$DGA1550:

$ SHOW DEV/MULTI $1$DGA1550
and check for the correct number of pathes to the disk.

Feel free to post the commands and results in an attached .TXT file.

Volker.