Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## Media Data Store Messages

##### OVS-05300: no voltab specified

Cause: This program requires that a voltab file be specified.

Action: Rerun the program and specify the voltab file using the appropriate command line option.

##### OVS-05301: cannot read 'voltab info' from disk num

Cause: An internal error occurred while trying to verify the volume information on the disk.

Action: Contact Oracle customer support.

##### OVS-05304: cannot open voltab file 'str': str

Cause: Cannot open or access the voltab file.

Action: Verify that the voltab file exists and its access permissions allow the program to read it.

##### OVS-05305: smdsdOpen failed on disk str: str

Cause: The process failed to open and initialize the indicated disk for the reasons above.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05306: no volumes mounted from voltab 'str'

Cause: MDS failed to mount all volumes.

Action: See the log for related error messages.

##### OVS-05307: error in volume 'str': # disks (num) is not multiple of raidsize num

Cause: The number of disks in the volume must be a multiple of the raid width, which is indicated in the "width" parameter in the voltab file.

Action: Fix the voltab file by modifying the raid width or the number of disks that comprise the volume.

##### OVS-05308: seeking to invalid address in 'str': str

Cause: An internal error occurred while seeking within the indicated file.

Action: Contact Oracle customer support.

##### OVS-05309: all disks in volume 'str' do not have the same size

Cause: All disks in a volume must have the same size.

Action: Check that all disks within the volume have the same size. Replace the odd-sized disk(s).

##### OVS-05310: raw disk 'str' has str bytes but raw disk 'str' has str bytes

Cause: All disks in a volume must have the same size.

Action: Check that all disks within the volume have the same size. Replace the odd-sized disk(s).

##### OVS-05311: invalid disk name: str

Cause: The indicated disk name does not have the proper format.

Action: Fix the syntax error which occurred, most likely in the voltab file or on the command line.

##### OVS-05312: volume 'str' is incompatible with server (version str)

Cause: This server cannot access the indicated volume because the version of the server is incompatible with the version of the volume. This volume was probably created by a newer version of MDS whose format is not recognized by older versions of MDS.

Action: Use a more current version of MDS.

##### OVS-05313: received signal num

Cause: The process received the signal indicated.

Action: No action required. The log may contain errors from failures related to receipt of this signal.

##### OVS-05314: reading from invalid address in 'str': str

Cause: An internal error occurred while reading within the indicated file.

Action: Contact Oracle customer support.

##### OVS-05315: writing to invalid address in 'str': str

Cause: An internal error occurred while writing within the indicated file.

Action: Contact Oracle customer support.

##### OVS-05316: failed to read TOC for volume 'str'

Cause: The MDS server failed to read the table of contents for the indicated volume.

Action: Check the log for related error messages concerning disk I/O.

##### OVS-05317: invalid stripe size of num specified for volume 'str'

Cause: The stripe size indicated by "width" in the voltab file is not a legal value.

Action: Modify the voltab file to use a legal stripe size.

##### OVS-05321: error in voltab file 'str' at line num: str

Cause: A syntax error was found in the voltab file.

Action: Fix the syntax error in the voltab file by using the format specified in the documentation.

##### OVS-05322: cannot obtain capacity of any disks

Cause: None of the disks are responding to queries about their disk size.

Action: See the log for related error messages.

##### OVS-05323: Media Net error: str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05324: Media Net error issuing RPC 'str' to str: str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05327: volume 'str' not mounted

Cause: The indicated volume was not mounted.

Action: See the log for related error messages.

##### OVS-05329: cannot convert volume 'str' to latest format: volume mounted read-only

Cause: The indicated volume needs to be converted to a different format in order to be compatible with MDS. The conversion can only occur if the volume is mounted in read-write mode.

Action: Remount the volume in read-write mode.

##### OVS-05330: cannot add 'str/str/str'. Table of contents is full

Cause: The table of contents is full.

Action: Remove unused files from the volume.

##### OVS-05331: cannot add 'str/str/str'. Volume is full

Cause: The volume is full.

Action: Remove unused files from the volume.

##### OVS-05336: cannot initialize MKE

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05338: cannot allocate buffer space for copy

Cause: An internal error occurred while copying files.

Action: Contact Oracle customer support.

##### OVS-05339: vertex dropped a message to MDS

Cause: MDS lost a message.

Action: No action required. The log may contain errors from failures related to the lost message.

##### OVS-05340: failed to locate server 'str'

Cause: This process is an MDS client and is unable to locate the MDS server.

Action: Verify that an MDS server is running and accessible to the client.

##### OVS-05341: invalid voltab filename 'str'

Cause: The indicated voltab filename contains a syntax error.

Action: Rerun the program using a voltab filename with legal syntax.

##### OVS-05343: no memory to allocate 'str' in str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05344: smdsdWrite of disk str failed: str

Cause: A write to the indicated disk failed for the reasons given.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05345: smdsdUpdate of disk str failed: str

Cause: A flush to the indicated disk failed for the reasons given.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05346: reading an invalid number of bytes in 'str': str

Cause: An internal error occurred while reading within the indicated file.

Action: Contact Oracle customer support.

##### OVS-05347: writing an invalid number of bytes in 'str': str

Cause: An internal error occurred while writing within the indicated file.

Action: Contact Oracle customer support.

##### OVS-05348: smdsdRead of disk str failed: str

Cause: A read to the indicated disk failed for the reasons given.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05351: smdsdIdle failed: str

Cause: The system-dependent error indicated occurred while waiting for disk I/O to complete.

Action: See your operating system documentation.

##### OVS-05352: cannot support num disks: maximum number of disks for volume 'str' is num

Cause: The voltab specification includes more disks per volume than allowed.

Action: Modify the voltab file to use fewer disks.

##### OVS-05354: str of 'str' failed: too many errors

Cause: The indicated I/O operation failed because too many errors occurred.

Action: See the log for related error messages.

##### OVS-05355: target 'str' is not a file

Cause: This program requires that the indicated argument be a legal filename.

Action: Rerun the program with a valid target filename.

##### OVS-05360: voltab on disk 'str' does not match input voltab for volume 'str'

Cause: An error occurred while verifying the volume's attributes.

Action: See the log for related error messages.

##### OVS-05362: MDS RPC failed with return code of num

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05365: smdsdAlloc failed: not enough memory

Cause: The process cannot allocate memory for the I/O operation.

Action: Contact Oracle customer support.

##### OVS-05367: re_exec failed for string 'str': rc = num

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05370: failed to write table of contents for 'str'

Cause: An error occurred while modifying the table of contents.

Action: See the log for related error messages.

##### OVS-05371: no room in the table of contents for 'str'

Cause: The table of contents is full.

Action: Remove unused files from the volume.

##### OVS-05372: no room in the volume for 'str'

Cause: The volume is full.

Action: Remove unused files from the volume.

##### OVS-05374: warning: volume 'str' not available

Cause: MDS failed to mount the indicated volume.

Action: See the log for related error messages.

##### OVS-05379: NSP operation 'str' failed with error num

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05380: rebuild of disk str failed: error occurred or disk not in any volume

Cause: An error occurred during rebuild.

Action: See the log for related error messages.

##### OVS-05384: smdsdInit failed: str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05387: cannot find size of raw disk str: str

Cause: The indicated disk is not responding to queries about its disk size.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05392: cannot allocate num Mbps for '/mds/str/str': num Mbps available

Cause: The server does not have as much bandwidth as the client requested in the indicated volume.

Action: Be prepared to encounter out-of-bandwidth errors. No immediate action required.

##### OVS-05393: cannot allocate requested bitrate for 'str'

Cause: The server does not have enough bandwidth for the client in the indicated volume.

Action: Wait for other processes to free up bandwidth.

##### OVS-05400: blocking MDS I/O timed-out

Cause: An I/O did not complete because it timed-out.

Action: See the log for related error messages.

##### OVS-05401: blocking MDS RPC timed-out

Cause: A request to the MDS server did not complete because it timed-out.

Action: See the log for related error messages.

##### OVS-05402: number of input files has changed since start of operation

Cause: The number or size of the input files have changed since the program was run.

Action: Rerun the program.

##### OVS-05403: file 'str' has been created or modified since start of operation

Cause: The indicated input file has changed since the program was run.

Action: Rerun the program.

##### OVS-05404: smdsdOpen failed on disk str: no more I/O descriptors

Cause: The process failed to open the indicated disk.

Action: Contact Oracle customer support.

##### OVS-05406: read of 'str' at offset str failed on disk str (num): str

Cause: The read operation indicated failed.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05407: write of 'str' at offset str failed on disk str (num): str

Cause: The write operation indicated failed.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05408: read of 'str' at offset str failed on disk str (num): timed-out

Cause: The read operation indicated failed.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05409: write of 'str' at offset str failed on disk str (num): timed-out

Cause: The write operation indicated failed.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05421: invalid bandwidth reservation token for 'str'

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05422: cannot rebuild volume 'str' in inconsistent read-only mode

Cause: A volume can only be rebuilt if it is mounted in read-only or read-write mode.

Action: Remount volume in read-only or read-write mode.

##### OVS-05423: cannot initialize the TOC of volume 'str': volume is read-only

Cause: The TOC of a volume can only be initialized if it is mounted in read-write mode.

Action: Remount volume in read-write mode.

##### OVS-05426: rebuild disk 'str' immediately

Cause: The disk indicated needs to be rebuilt.

Action: Run mdsrebuild immediately.

##### OVS-05427: disk 'str' and 'str' cannot both be rebuilt - volume may be corrupted

Cause: The disks above both need to be rebuilt. However, since the failures are within the same raid stripe, they cannot both be rebuilt.

Action: Contact Oracle customer support.

##### OVS-05428: cannot read volume attributes on disk 'str'

Cause: An I/O error occurred on the disk indicated.

Action: Determine if the disk is broken. If it is, bring up MDS and specify the disk as a broken disk. Replace the disk with a working one and rebuild it immediately.

##### OVS-05429: cannot read disk mode on disk 'str'

Cause: An I/O error occurred on the disk indicated.

Action: Determine if the disk is broken. If it is, bring up MDS and specify the disk as a broken disk. Replace the disk with a working one and rebuild it immediately.

##### OVS-05430: volume attributes verification failed on all disks

Cause: The volume attributes on disk do not match the input voltab for any of the disks. The volume probably has not been initialized via mdsinit.

Action: If this is the case, run mdsinit to initialize the volume attributes.

##### OVS-05431: cannot execute more than one disk rebuild per volume set

Cause: Each volume or volume set can only support one outstanding disk rebuild at any time.

Action: Wait until the conflicting rebuild has completed before starting this disk rebuild.

##### OVS-05432: volume attributes verification failed on disk 'str': volume has no parity

Cause: Cannot read the volume attributes or mode from the indicated disk. In addition, the disk cannot be rebuilt because the volume does not contain parity information.

Action: Contact Oracle customer support.

##### OVS-05450: Media Net RPC 'str' to 'str' failed: str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05451: Media Net error finding copy slave 'str': str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05452: failed to marshal arguments for 'str' RPC to 'str'

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05461: failed to marshal arguments for RPC str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05462: cannot create link for bandwidth capacity for volume 'str': volume 'str' does not exist

Cause: The volume indicated cannot be mounted because the volume it is supposed to share bandwidth with is not mounted.

Action: Mount the volume with its own bandwidth resources or mount the volume whose bandwidth is to be shared first.

##### OVS-05463: bandwidth capacity for volume 'str' not specified

Cause: A volume must have a bandwidth capacity specified in order to be mounted.

Action: Specify the bandwidth capacity for the volume when mounting it.

##### OVS-05465: invalid address given at input: str

Cause: The address is either negative or exceeds the size of the file.

Action: Rerun the program with a legal input address.

##### OVS-05466: start address str is larger than end address str

Cause: The start address must be smaller than the end address.

Action: Rerun the program with a legal start address.

##### OVS-05467: voltab information not stored on disk 'str': disk not found in voltab

Cause: The input voltab must correspond to the volume containing the disk being rebuilt.

Action: Rerun the program with the correct voltab or initialize the disk directly.

##### OVS-05470: cannot get 'str' from global context manager

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05473: cannot initialize global context manager

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05474: cannot put 'str' into global context manager

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05478: write to 'str' failed: mdsAioWrite cannot perform unaligned writes

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05486: cannot open host file 'str'

Cause: The file indicated cannot be opened.

Action: Verify that the file exists and that its access permission allow the desired type of access.

##### OVS-05487: host file system call 'str' failed

Cause: The host file operation indicated failed.

Action: Verify that the file exists and that its access permission allow the desired type of access.

##### OVS-05488: cannot create server: str

Cause: The server cannot be created for reasons provided above.

Action: If the name server already contains an entry for MDS, restart the system. Otherwise, contact Oracle customer support.

##### OVS-05489: cannot register server: str

Cause: The server cannot be registered for reasons provided above.

Action: If the name server already contains an entry for MDS, restart the system. Otherwise, contact Oracle customer support.

##### OVS-05491: waiting for exclusive access to Media Data Store lock manager

Cause: Another MDS server or utility is holding the lock to the global lock manager.

Action: If this process is still hung, contact Oracle customer support.

##### OVS-05496: could not open file 'str'. Rebuild failed

Cause: The rebuild process cannot open a file that needs to be rebuilt.

Action: See the log for related error messages.

##### OVS-05498: TOC conversion for volume 'str' failed: volume is mounted read-only

Cause: A volume must be mounted in read-write mode in order to be converted to a version compatible with this server.

Action: Remount the volume in read-write mode.

##### OVS-05500: reading or writing past EOF in file 'str'

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05506: cannot create host file 'str'

Cause: The host file indicated cannot be created.

Action: Verify that the filename is legal and the directory's access permissions.

##### OVS-05507: cannot close host file 'str'

Cause: The host file indicated cannot be closed.

Action: Verify that the file exists.

##### OVS-05508: waiting to obtain ownership of file 'str'

Cause: The file indicated is being written by another MDS client.

Action: Wait for that process to close the file.

##### OVS-05509: defragmentation failed. Cannot start up slaves

Cause: The defragmentation slaves could not be launched.

Action: Verify that the defragger was started up as indicated in the documentation. If the problem persists, contact Oracle customer support.

##### OVS-05510: defragmentation failed. Cannot find all slaves

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05513: defragmentation failed. No files corrupted

Cause: A previous error occurred.

Action: See the log for related error messages.

##### OVS-05515: defragmentation failed. File 'str/str/str' may have been corrupted

Cause: A previous error occurred.

Action: See the log for related error messages. The indicated file must be reloaded since its image on disk may have been corrupted.

##### OVS-05516: Media Net error finding defragmentation slave 'str': str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05517: Media Net error issuing defragmentation RPC 'str' to slave num: str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05518: status call to defragmentation slave 'str' failed: str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05519: defragmentation slave 'str' not exiting

Cause: The indicated process is not exiting due to a previous error.

Action: Inform Oracle customer support. No immediate action required.

##### OVS-05525: copy slave 'str' not exiting

Cause: The indicated process is not exiting due to a previous error.

Action: Inform Oracle customer support. No immediate action required.

##### OVS-05557: cannot mount volume 'str': conflicting mount by another MDS server

Cause: The volume indicated cannot be mounted because of the mount status of another MDS server.

Action: Remount the volume in a mode that does not conflict with the other MDS server(s).

##### OVS-05565: read of 'str' at offset str failed on disk str: str

Cause: The read operation indicated failed.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05566: write of 'str' at offset str failed on disk str: str

Cause: The write operation indicated failed.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05584: error in setting disk 'str' to normal mode: str

Cause: The disk cannot be set to normal mode.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05585: error in setting disk 'str' to rebuild mode: str

Cause: The disk cannot be set to rebuild mode.

Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.

##### OVS-05587: invalid start address: str

Cause: The address is either negative or exceeds the size of the file.

Action: Rerun the program with a legal input address.

##### OVS-05588: error reading file 'str'

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05595: volume capacity not specified

Cause: A volume must have a bandwidth capacity specified in order to be mounted.

Action: Specify the bandwidth capacity for the volume.

##### OVS-05596: volume 'str' not unmounted: active readers and writers exist

Cause: A volume cannot be unmounted if MDS clients are actively reading and writing files in that volume.

Action: Wait for all MDS clients to close the files in that volume before unmounting it.

##### OVS-05603: volume 'str' not remounted: active writers exist

Cause: A volume cannot be remounted if MDS clients are writing to files in that volume.

Action: Wait until all MDS clients have finished writing to the volume.

##### OVS-05604: NSP entry 'str' not found

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05605: volume 'str' not unmounted

Cause: The volume indicated was not unmounted.

Action: See the log for related error messages.

##### OVS-05609: volume 'str' not remounted

Cause: The volume indicated was not remounted.

Action: See the log for related error messages.

##### OVS-05610: cannot recover from failure to remount volume 'str'

Cause: The errors encountered while trying to remount the indicated volume are fatal.

Action: See log fore related error messages. Contact Oracle customer support.

##### OVS-05611: volume 'str' not remounted: cannot reduce available bandwidth capacity

Cause: A volume cannot be remounted with less bandwidth capacity.

Action: Remount the volume with at least the same amount of bandwidth capacity.

##### OVS-05612: volume 'str' not mounted: no voltab specified

Cause: To mount a volume, the voltab must be specified.

Action: Remount the volume and specify the voltab.

##### OVS-05632: unable to launch parallel slaves

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05633: cannot terminate slave str: str: str

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05634: failed to locate copy slaves

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05635: copy slave incurred unexpected death

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05639: cannot write to deleted file 'str'

Cause: Files that have been deleted cannot be modified.

Action: If you really want to write to the deleted file, recover the file first by undeleting it.

##### OVS-05642: volume cannot support TOC size of num stripes: volume contains num stripes

Cause: The volume's table of contents is larger than the volume.

Action: Verify that the volume hasn't inadvertently shrunk. If not, then decrease the TOC size by specifying a smaller value in the voltab.

##### OVS-05643: position of TOC of volume 'str' conflicts with position of file 'str'

Cause: The size of the volume's TOC has probably been recently increased. The new TOC is occupying disk space also occupied by the indicated file.

Action: If the size of the volume's TOC has indeed been recently increased, then revert back to the original TOC size. Remove the conflicting files before increasing the TOC size.

##### OVS-05648: source and destination files must be different: str

Cause: The user has specified the same filename for both the source and destination file for an operation that requires the source filename to be different than the destination. Example: mdscp, mdsconcat.

Action: Use different files for src and dst; be aware that wildcarding or links may cause different filenames to refer to the same file.

##### OVS-05649: resource 'str' is incompatible with resource 'str'

Cause: The user has specified incompatible resources. A common cause is specifying incompatible arguments to a process, such as both length_in_bytes and end_address for mdssum.

Action: Consult the documentation for the correct usage.

##### OVS-05651: resource str must be set to interpret relative filename 'str'

Cause: The user has specified a relative filename and the resource mds.cwd is not set. Mds does not know where the file may reside.

Action: Specify an absolute pathname (beginning with /mds), or set the mds.cwd resource, i.e. setenv MDS_CWD /mds/int1

##### OVS-05654: possible corruption: TOC contains num files, maximum possible should be num

Cause: The TOC of the volume appears to be corrupt. This is usually caused by having run mdsvolinit on the volume to change the spec of the TOC, and using a modified voltab file with a different raidsize or stripe width.

Action: If the cause is as described above, rerun mdsvolinit with the correct voltab information. If not, contact WWS.

##### OVS-05657: disk 'str' not reset to normal mode: its volume is mounted and not rebuilt

Cause: The indicated volume is currently being mounted by another MDS server and has not yet been rebuilt. Consequently, the disk mode cannot be set to normal.

Action: Rebuild the indicated disk as soon as possible.

##### OVS-05659: disk 'str' needs to be rebuilt or spared

Cause: The volume attributes on this disk do not correspond with the volume's.

Action: Check the voltab information and verify that it is correct. If the disk should be rebuilt or spared, follow the procedure as documented.

##### OVS-05660: cannot read volume information for disk 'str'

Cause: An attempt to read volume information for the indicated disk failed. MDS expects this disk to be up and readable because either the volume doesn't have parity or another disk disk within the same raid stripe has already failed.

Action: Check the voltab information and verify that it is correct. Check that the disk is on-line and operating correctly. If the error still occurs, contact Oracle customer support.

##### OVS-05662: disk 'str' is not a disk in any volumes in the input voltabs

Cause: MDS expects all of the volumes that exist on the indicated disk to be listed in the input voltabs.

Action: Check that all volumes that exist on the indicated disk are on one of the input voltabs and that the input voltabs are correct.

##### OVS-05664: cannot access disk status information for volume 'str'

Cause: MDS is unable to read or find the disk status information for the indicated volume.

Action: Check that the voltab information is correct. Verify that all disks in the volumes are in the correct mode. Verify that all disks in the volume are on-line and operating correctly. If the error still occurs, contact Oracle customer support.

##### OVS-05666: warning: disk 'str' not reset to normal mode: cannot obtain MDS lock

Cause: Another MDS process has exclusively control of the MDS lock.

Action: Wait for a few seconds and rerun mdsrebuild.

##### OVS-05674: disk 'str' not open in current process

Cause: Internal error.

Action: Contact Oracle customer support.

##### OVS-05675: disk 'str' already in use as spare.

Cause: If a disk is in use a spare, another disk cannot be spared to it.

Action: Either: choose another disk to spare to or unspare the spare disk.

##### OVS-05677: cannot spare disk 'str': volume 'str' has no RAID protection

Cause: Spare disks depend on parity protection to rebuild missing info. Without parity, you cannot spare a disk.

Action: None possible other than a complete redo of volume with parity.

##### OVS-05681: warning: disk 'str' not reset to normal mode: mounted by another MDS system

Cause: Mds believes that the disk is potentially in use by another server. As such, it cannot safely return the disk to normal mode until all known and in-use partitions on the disk have been rebuilt.

Action: Run mdsrebuild within the other servers to rebuild the other partitions of the new disk. When the disk is completely rebuilt, use mdsdiskmode to return the disk to normal mode.

##### OVS-05685: spare disk 'str' needs to be a spare disk in volume 'str'

Cause: The volume was created with a spare disk that is no longer specified or does not match the name of the spare that was originally used.

Action: Correct the voltab to list the original spare disk name, or run "mdsvolinit -s" to change the spare disk name on the other disks.

##### OVS-05686: disk 'str' is part of volume 'str' and cannot be used as a spare

Cause: You cannot spare an operating disk to another operating disk. You can only spare a normal operating disk to a specified spare.

Action: Make sure you are sparing a normal disk in the volume to one of the specified spares for that volume.

##### OVS-05687: minimum disk size for this platform is str bytes: disk 'str' holds str bytes

Cause: The disk (or possibly simulated disk, i.e. a file) is too small.

Action: Acquire bigger disks.

##### OVS-05689: malformed segment: segment len=str, offset=str

Cause: The segment length and offset are invalid. This could either be an internal error, or tar is encountering filenames with incorrect segment information.

Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.

##### OVS-05690: bad header: unable to convert ASCII string 'str' into octal equivalent

Cause: The TAR header appears to be corrupt.

Action: Obtain a new copy of the TAR archive.

##### OVS-05691: open of archive 'str' failed: str

Cause: mdstar was unable to open the archive (usually a physical device).

Action: Check the device or archive name for legality and the correct permissions. Check for hardware connectivity problems.

##### OVS-05692: close of archive failed: str

Cause: mdstar was unable to close the archive (usually a physical device). May be caused by premature shutdown or loss of archive device.

Action: None. However this warning may indicate that the TAR archive may be incomplete.

##### OVS-05695: partial block read; read num bytes out of num

Cause: The TAR archive appears to be corrupt. Tar must always read block multiples of 512 bytes.

Action: Obtain a new copy of the TAR archive.

##### OVS-05696: unexpected EOF

Cause: The TAR archive appears to be corrupt. Tar must always read block multiples of 512 bytes.

Action: Obtain a new copy of the TAR archive.

##### OVS-05697: bad header: no checksum match, no EOA.

Cause: The TAR archive appears to be corrupt. mdstar expected a TAR archive header and found a bad checksum within the header.

Action: Obtain a new copy of the TAR archive.

##### OVS-05698: malformed segment: segment size of str is bigger than str

Cause: The segment length and offset are invalid. This could either be an internal error, or tar is encountering filenames with incorrect segment information.

Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.

##### OVS-05699: malformed segment: expected next segment but found EOA

Cause: Missing a segment. This could either be an internal error, or tar is encountering filenames with incorrect segment information.

Action: Check the segmented filenames carefully to see if they are properly formed and complete. If they are, contact WWS.

##### OVS-05700: malformed segment: expected next segment but segment name ('str') doesn't parse

Cause: Failed to parse the next segment name. This could either be an internal error, or tar is encountering filenames with incorrect segment information.

Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.

##### OVS-05701: write error when extracting file 'str'. Wrote num bytes out of num.

Cause: Unexpected write error probably caused by read-only volume, or having a locked file with the same name present in Mds.

Action: Bring up Mds in read/write mode, or remove the locked file.

##### OVS-05702: read error when creating file 'str'. Read num bytes out of num at offset str

Cause: Unexpected read error. Probably caused by disk unavailability.

Action: None. By default mdstar will try several times to read/write in the face of intermittent errors. Check possible physical problems and for interference from other disk intensive processes.

##### OVS-05704: unable to parse setting for resource 'str'

Cause: An expected resource was not set or was set incorrectly.

Action: Check to see that the resource is set properly, usually via the command line.

##### OVS-05707: at least one action mode must be specified

Cause: mdstar must either extract, create, or list archives.

Action: Specify an action via the command line.

##### OVS-05709: Enter name for next archive or to continue.

Cause: mdstar has reached the end of the archive. Reading a multi-volume archive or creating an archive that is larger than a physical tape will cause mdstar to assume that the archive is spread across multiple tapes.

Action: Insert the next tape and hit return.

##### OVS-05717: warning: disk 'str' not in any mounted volumes and cannot be rebuilt

Cause: The specified disk is not part of any of the volumes currently mounted by the MDS server. A disk rebuild can only occur if the volumes on that disk are mounted.

Action: Verify that the disk name is correct. If it is, start up the MDS server with the associated volumes mounted.

##### OVS-05718: only one server mode option allowed

Action: Specify only one of the options: -I, -R, -W.

##### OVS-05719: volume 'str' listed after multiple volume mount options

Action: Specify the volume with only one of the options: -i, -r, -w.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index