HP OpenVMS Systems

ask the wizard
Content starts here

CD-ROM MOUNT FILESTRUCT error on V7.2?

» close window

The Question is:

 
Hello,
 
I work for BEA Systems.   We support the MessageQ product for VMS.
 
The problem is VMS V7.2 will not read our MQ V4.0A CD.   This problem was
discovered several months ago during the field test (EFT2) of VMS V7.2.  I
reported the failure to Compaq at that time, however there was no response.
When we received the final v
ersion of V7.2 I tried the MQ CD again, and it still fails.   This has also
been reported by our customers; reference case 137880.
 
The CD reads fine on all version of VMS prior to V7.2.   Further, in our VMS
cluster here in Dallas, we can place the MQ CD in the system that is running
V7.2, serve the disk, and read it just fine from another VMS (V7.1 or V6.2)
system.   All to say it h
as nothing to do with the hardware or this specific CD.
 
This is the error message given when we try to mount the CD on VMS V7.2:
 
$ mou/ov=id $2$DKA400:
%MOUNT-F-FILESTRUCT, unsupported file structure level
 
---------------
 
This is the way the MQ CD normally mounts and looks:
 
$ mou/ov=id $2$DKA400:
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, MQVMS40A mounted on _$2$DKA400: (REDOAK)
$ sh dev/fu $2$DKA400:
 
Disk $2$DKA400: (REDOAK), device type DEC RRD45, is online, allocated,
    deallocate on dismount, mounted, software write-locked, file-oriented
    device, shareable, available to cluster, error logging is enabled.
 
    Error count                    0    Operations completed
10
    Owner process           "_RTA1:"    Owner UIC
[SYSTEM]
    Owner process ID        202000C8    Dev Prot
S:RWPL,O:RWPL,G:R,W
    Reference count                2    Default buffer size
512
    Total blocks              199116    Sectors per track
 
    Total cylinders             8297    Tracks per cylinder
 
    Host name               "REDOAK"    Host type, avail AlphaStation
255/233, y
es
    Allocation class               2
 
    Volume label          "MQVMS40A"    Relative volume number
 
    Cluster size                   3    Transaction count
 
    Free blocks                    0    Maximum files allowed
451
    Extend quantity                5    Mount count
 
    Mount status             Process    Cache name
"_$1$DIA0:XQPCACHE"
    Extent cache size             64    Maximum blocks in extent cache
 
    File ID cache size            64    Blocks currently in extent cache
 
    Quota cache size               0    Maximum buffers in FCP cache
4731
    Volume owner UIC        [SYSTEM]    Vol Prot
S:RWCD,O:RWCD,G:RWCD,W:RWCD
 
  Volume Status:  subject to mount verification, file high-water marking,
write-
      back caching enabled.
--------------
 
 


The Answer is :

 
  Please contact the Compaq Customer Support Center, or your Compaq
  support contact.
 
  The fix for the likely cause will likely be included in an OpenVMS
  Alpha V7.2 UPDATE kit after V1.0, and is also expected to be in V7.2-1.
  Specific images that may resolve this problem can be retrieved from
  the Compaq Customer Support Center.
 
  OpenVMS V7.2 provided a new check to determine if the disk that you are
  MOUNTing was initialized to a size that is larger than the number
  of blocks that are now available.
 
  This condition is a result of a disk that is moved from one controller
  type to another (for example, from a local SCSI connection to an HSJ)
  without the disk being initialized on the new controller.  Some data
  may be unaccessible through the new controller.
 
  It is recommended that the BACKUP utility be used to move data from
  a disk on one controller type to a disk on another controller type,
  especially if those controllers report a different number of blocks
  available for the same disk type.  Once the data has been moved,
  they physical disk can be moved and initialized on the new controller.
 
  If this condition was detected, then a fatal MOUNT-F-FILESTRUCT error
  was reported and the MOUNT was aborted.
 
  It has been determined that a number of customers are running with
  disks which are in this condition.  While there may be data that is
  inaccessible on the disk, the usefulness of the disk should be left
  to the discretion of the system manager.
 
 

answer written or last revised on ( 10-JUN-1999 )

» close window