| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 340.1 | only a small restriction | COOKIE::HOLSINGER | HSM Engineering, DTN 522-2843 | Wed May 21 1997 17:01 | 16 |
| Hello Rob,
I presume that the 'SHP_INVALID_CACHE' error message you refer to is an
SHP exception, in the SHP_ERROR.LOG file, as I could not find any references
to this string in our message files.
Your customer should not have a problem configuring these virtual disks, as
as each shows up as a disk-class device in lib$getdvi.
The only reason I can see that the code will fail a set cache... would be when
the node is in a cluster but the cache device under configuration is local.
Is this the case?
Regards,
/Paul
|
| 340.2 | | UTRTSC::BOOR | | Thu May 22 1997 07:04 | 7 |
| Paul,
yes I think the VDdriver creates local disks.
Will ask customer to use the LDdriver, which can MSCP serve the virtual disk.
Rob.
|
| 340.3 | Variants exist | EVMS::EVERHART | | Thu May 22 1997 10:51 | 13 |
| Either driver (vddriver or lddriver) can create mscp serveable
disks. With vddriver you need to create the contiguous container
files yourself separately. (copy/contig/alloc followed by
set file /end and set file /nomove, or use sysgen/crea).
I have a differently named free driver that will create virtual
disks on files that don't need to be contiguous. It can optionally
have these files accessed via decnet, or encrypted, or
compressed, or in process virtual memory (with various flavors
of logging/journalling) or a few more. There are also a few
other variant drivers that do stuff like shadowing or striping
or WORM handling...
|
| 340.4 | Init order? | EVMS::EVERHART | | Thu May 22 1997 10:58 | 13 |
| Could there be an initialization order problem somehow? If the vddriver
being used is of any recent vintage, there should be no way HSM
or anything else would know they are not just J Random local disks,
so long as the device units are connected with sysgen or sysman io
and are assigned to containers with asnvd before they are needed.
If however HSM is getting started before the VD units are set up,
its initialization may either fail to find the VD devices, or see
them as offline. I would imagine much the same could happen with
LDdriver.
<5000 block cache dir! Holy hannah!>
|
| 340.5 | Make server node to CATALOG SERVER | ATZIS3::KARTNER_M | HOUSTON, we have a problem | Fri May 23 1997 03:20 | 11 |
| Hi!
If the drives are only local on one node you could assign this one
to be the catalog server of you cluster. This should fix the problem
with the local cache disks. Are the devices connected to one
of your servers (reliable & fast)?
Remember that only this node will do catalog uptdates and cacheserving
after enabling this feature
bye
Michael
|
| 340.6 | Works now | UTRTSC::BOOR | | Fri May 30 1997 01:33 | 8 |
| Finally got it working.
The problem was with the virtual disk drives NOT being 'available to cluster'. Even if this node is catalog-server
these disk MUST be 'available to cluster'.
$ld connect/SHARE disk_file LDAnn did the trick.
Rob.
|