2 ACFS-00100 to ACFS-13378
- ACFS-00100: ENABLED
-
Cause: /*Action single letter option
- ACFS-00501: unable to allocate a buffer
-
Cause: A request for process virtual memory failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-00502: Failed to communicate with the ACFS driver. Verify the ACFS driver has been loaded.
-
Cause: The ACFS control device could not be accessed.
- ACFS-00503: invalid numeric value specified: string
-
Cause: The command argument does not support the specified value.
- ACFS-00504: Invalid unit specified: string. Valid units are K|M|G|T|P.
-
Cause: The command does not support the specified unit.
- ACFS-00505: invalid signature requested
-
Cause: The command failed to verify the ACFS file system metadata.
- ACFS-00506: Failed to read 'string'.
-
Cause: An open file could not be read.
- ACFS-00507: Failed to seek to string prior to writing the volume disk header.
-
Cause: A seek to the volume failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-00508: unable to obtain device major and minor number for volume string
-
Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.
- ACFS-00509: unsupported file type for string, not a block device
-
Cause: Volume provided was not recognized as a block device. This message is accompanied by other message(s) providing details on the error.
- ACFS-00510: unable to obtain volume id for string
-
Cause: Volume id was not obtained. This message is accompanied by other message(s) providing details on the error.
- ACFS-00511: string is mounted on at least one node of the cluster.
-
Cause: Cluster was still using the file system.
- ACFS-00512: A file system check of string is in progress.
-
Cause: The command failed because metadata showed that a file system check was either in progress or incomplete on the specified volume.
- ACFS-00513: unable to obtain ACFS driver version number
-
Cause: The ACFS driver version number could not be retrieved. The accompanying messages provide detailed failure information.
- ACFS-00514: unable to close handle
-
Cause: Handle could not be closed. This message is accompanied by other message(s) providing details on the error.
- ACFS-00515: version mismatch: \n string string version \n string ACFS kernel version
-
Cause: The command failed because of a mismatch between the loaded ACFS driver and the ACFS commands.
- ACFS-00516: stat of string failed
-
Cause: Stat() failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-00517: unable to obtain block device sector size
-
Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.
- ACFS-00518: unable to obtain volume size in sectors
-
Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.
- ACFS-00519: too many arguments: string
-
Cause: Too many arguments were entered on the command line.
- ACFS-00520: string is not an ADVM volume.
-
Cause: Volume specified was not an ADVM volume.
- ACFS-00521: Failed to determine file type of string.
-
Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.
- ACFS-00522: unable to get drive structure
-
Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.
- ACFS-00523: string is an unsupported drive type number.
-
Cause: Failed to obtain volume information. The accompanying messages provide detailed failure information.
- ACFS-00524: unable to obtain partition information
-
Cause: Failed to obtain volume information. This message is accompanied by other message(s) providing details on the error.
- ACFS-00525: failed to seek to string
-
Cause: Failed to seek to volume. This message is accompanied by other message(s) providing details on the error.
- ACFS-00526: read of volume disk header failed
-
Cause: Failed to read volume. This message is accompanied by other message(s) providing details on the error.
- ACFS-00527: unable to dismount volume
-
Cause: Could not dismount volume. This message is accompanied by other message(s) providing details on the error.
- ACFS-00528: Volume string is already mounted on string.
-
Cause: The file system could not be mounted because the specified volume was already mounted using a different mount point.
- ACFS-00531: write of volume disk header failed
-
Cause: Write to volume failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-00532: invalid option: string
-
Cause: The command does not support the specified option.
- ACFS-00533: string requires an argument
-
Cause: The command did not pass a required argument.
- ACFS-00534: A valid numeric string is required.
-
Cause: The command was rejected because the specified value was not a valid numeric string.
- ACFS-00535: insufficient arguments
-
Cause: The command required additional arguments.
- ACFS-00536: unknown extra argument: string
-
Cause: The command was rejected because the indicated argument was not a valid argument for this command.
- ACFS-00538: invalid command or command is not unique: string
-
Cause: The command was rejected because the indicated sub-command was not supported.
- ACFS-00539: missing arguments
-
Cause: The command was rejected because additional arguments were required.
- ACFS-00540: incorrect number of arguments
-
Cause: The command was rejected because an incorrect number of arguments were specified.
- ACFS-00542: argument is not an integer
-
Cause: The command was rejected because a string was specified as an argument instead of an integer.
- ACFS-00543: invalid command
-
Cause: The command was rejected because an invalid sub-command was specified.
- ACFS-00544: option spelling is not unique: string
-
Cause: An attempt to execute a command specifying an abbreviated option name was rejected because there were multiple possible options beginning with the specified string.
- ACFS-00545: string does not support a value: string=string
-
Cause: The command was rejected because an option that does not support a value was specified with a value attached.
- ACFS-00546: failed to change on-disk signature
-
Cause: The command failed to update ACFS metadata on-disk. The accompanying messages provide detailed failure information.
- ACFS-00547: Both the primary and alternate superblocks are damaged.
-
Cause: The file system metadata was found to be damaged.
- ACFS-00548: Failed to communicate with the ACFS driver. Verify that cluster membership has been established.
-
Cause: The ACFS driver's control device could not be accessed.
- ACFS-00549: mount path string already contains a volume mount point for volume string
-
Cause: The mount path contained a reparse point that references a a different volume than the mount request.
- ACFS-00550: checksums for both superblocks are bad
-
Cause: An attempt to validate the metadata on-disk failed due to a metadata inconsistency found in the file system superblocks.
- ACFS-00551: unable to process input from the command line
-
Cause: A failure occurred opening the stdin stream. The accompanying messages provide detailed failure information.
- ACFS-00552: End-of-file received instead of 'y' or 'n'
-
Cause: An end-of-file was received while waiting for the answer to a question prompt.
- ACFS-00554: Unable to obtain group name for gid: number
-
Cause: The command failed because the group name could not be determined using the supplied group id.
- ACFS-00555: unsupported file type for string, not a device file
-
Cause: Volume provided was not recognized as a device file. This message is accompanied by other message(s) providing details on the error.
- ACFS-00556: invalid vfs name string
-
Cause: a helper command was called with an unexpected vfs name argument
- ACFS-00560: Operation not applicable for FSType string
-
Cause: ACFS did not support the specified option.
- ACFS-00562: An attempt to create Oracle Registry ACFS key string resulted in a registry error. string
-
Cause: An error was returned by the Oracle Registry service when attempting to create an ACFS key. This message is accompanied by other message(s) that provide details as to the exact cause of the failure.
- ACFS-00564: unable to delete Oracle Registry key string while trying to recover from an error string
-
Cause: Removal of a key from the Oracle Registry failed.
- ACFS-00565: unable to delete Oracle Registry key string string
-
Cause: Removal of mount key from Oracle Registry failed.
- ACFS-00566: invalid handle received when attempting to close an ACFS mount key within Oracle Registry
-
Cause: An error was returned during the closing of a key in the Oracle Registry.
- ACFS-00567: unknown Oracle Registry error encountered closing key
-
Cause: An error was returned while closing the key from the Oracle Registry.
- ACFS-00568: closing of a key resulted in Oracle Registry error number
-
Cause: An error was returned during the closing of a key in the Oracle Registry.
- ACFS-00569: invalid handle received when attempting to delete an ACFS mount key within Oracle Registry
-
Cause: An error was returned while removing a key from the Oracle Registry.
- ACFS-00570: The ACFS mount key specified for deletion does not exist within Oracle Registry.
-
Cause: The mount key could not be located in the Oracle Registry.
- ACFS-00571: The ACFS mount key specified for deletion is not empty.
-
Cause: The mount key specified for deletion from the Oracle Registry contained dependent subkeys.
- ACFS-00572: permission denied to delete the ACFS mount entry from Oracle Registry
-
Cause: The user permissions were insufficient to remove the key from the Oracle Registry.
- ACFS-00573: Oracle Registry error encountered while deleting an ACFS mount key
-
Cause: An error was returned while removing the key from the Oracle Registry.
- ACFS-00575: deletion request of key resulted in Oracle Registry error number
-
Cause: An error was returned while removing a key from the Oracle Registry.
- ACFS-00584: failed to look up ACFS mount points in the Oracle Registry string
-
Cause: An error was returned while looking up a mount point in the Oracle Registry.
- ACFS-00585: null parameter received
-
Cause: A null parameter was passed to the Oracle Registry.
- ACFS-00587: unknown Oracle Registry error encountered during operation on ACFS mount entry
-
Cause: An error was returned while accessing the key from the Oracle Registry.
- ACFS-00589: key operation resulted in Oracle Registry error number
-
Cause: An error was returned during a key operation with the Oracle Registry.
- ACFS-00591: error found in volume disk header
-
Cause: An attempt to validate the metadata on-disk failed due to a metadata inconsistency found in the volume disk header.
- ACFS-00592: Seek to volume failed. Verify the volume exists.
-
Cause: Seek to a location on the volume failed.
- ACFS-00593: The Oracle Registry returned the following error while attempting to access ACFS key string string
-
Cause: Failed to access either the SYSTEM, SYSTEM.ACFS or SYSTEM.ACFS.Mounts keys in Oracle Registry.
- ACFS-00594: Failed to access ACFS mount information. The Oracle Registry returned the appended error for ACFS key string. string
-
Cause: Failed to access ACFS mount information from the Oracle Registry.
- ACFS-00595: Failed to access ACFS mount value information. The Oracle Registry returned the appended error for ACFS key string. string
-
Cause: Failed to access ACFS mount value information from the Oracle Registry. This might be due to Oracle Registry corruption or a sudden loss of the Oracle Registry service.
- ACFS-00596: A failure occurred while accessing the Oracle Registry ACFS key "SYSTEM" for security purposes and follows this message: string
-
Cause: Failed to retrieve key access rights for the Oracle Registry ACFS key "SYSTEM"
- ACFS-00597: Failed to initialize the Oracle Registry's SCLS context. The SCLS error is included with this message.
-
Cause: An operating system initialization failed.
- ACFS-00598: An error occurred while looking up the current user's operating system account name. The error is included with this message.
-
Cause: ACFS was attempting to add an entry to the Oracle Registry. During this attempt a lookup of the current user's name failed in the operating system failed.
- ACFS-00599: The Oracle Registry returned the following error while attempting to close the ACFS key string string
-
Cause: Possibly due to Oracle Registry corruption or a sudden loss of the Oracle Registry service.
- ACFS-00600: Failed to access ACFS mount subkey information. The Oracle Registry returned the appended error. string
-
Cause: Failed to access ACFS mount information from the Oracle Registry.
- ACFS-00601: Failed to initialize this utility's access to the Oracle Registry. Verify the registry service has started.
-
Cause: Either the Oracle Registry service was unavailable or the registry configuration was incomplete/inaccurate.
- ACFS-00602: An internal error (BADARG) occurred while trying to determine the Oracle Registry configuration.
-
Cause: An Oracle internal error.
- ACFS-00603: Failed to retrieve the Oracle Cluster Registry, OCR, configuration
-
Cause: Failed to obtain OCR information.
- ACFS-00604: Failed to retrieve the Oracle Local Registry, OLR, configuration
-
Cause: Failed to obtain Oracle Local Registry information.
- ACFS-00605: Failed to retrieve the Oracle Registry configuration for an unknown reason
-
Cause: Failed to obtain Oracle Registry information.
- ACFS-00606: Could not determine if the system is configured for RAC or Oracle Restart environment.
-
Cause: The Oracle Registry service configuration could not be detected
- ACFS-00607: Failed to access or create Oracle Registry keys required for ACFS operation
-
Cause: Oracle Registry keys required for operation either could not be accessed or created.
- ACFS-00608: Invalid option combination: string conflicts with another option.
-
Cause: The command did not support the specified option combination.
- ACFS-00609: End-of-file received.
-
Cause: An end-of-file was received while waiting for the answer to a question prompt.
- ACFS-00619: This is a string computer, but the file system was created on a string string computer.
-
Cause: The file system was created on a computer which has a different Endian than the current system. Little Endian machines (such as the intel x86 based systems) store the Least Significant bit in the first byte of an integer value. Big Endian machines (such as Solaris SPARC and AIX Power based systems) store the Most Significant bit in the first byte of an integer value.
- ACFS-00620: This feature is not available for Oracle version string or lower on this platform.
-
Cause: Informational.
- ACFS-00621: Unable to determine privileges
-
Cause: An error occured retrieving the user credentials.
- ACFS-00622: must provide a base mount point
-
Cause: A mount point on the base site was not provided.
- ACFS-00623: must provide a target mount point
-
Cause: A mount point on the target site was not provided.
- ACFS-00624: The path specified is too long.
-
Cause: The path specified exceeded the allowed maximum path length.
- ACFS-00625: string is not a valid ACFS mount point.
-
Cause: The mount point path specified was not a valid mount point.
- ACFS-00999: unexpected assert: "string", string: string: number
-
Cause: An unexpected situation has occurred.
- ACFS-01001: Size specified cannot exceed size of volume.
-
Cause: Volume size was smaller than the requested size.
- ACFS-01002: ACFS requires a minimum volume size of numberMB.
-
Cause: Volume was too small.
- ACFS-01003: failed to generate a unique file system ID
-
Cause: An error occurred during the generation of a unique file system identifier. This message is accompanied by other messages providing details on the error.
- ACFS-01004: string was not formatted.
-
Cause: An error occurred during the formatting of the volume.
- ACFS-01005: unable to allocate a buffer
-
Cause: A request for process virtual memory by the ACFS format command failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01006: unable to open volume device 'string'
-
Cause: Volume device could not be opened. This message is accompanied by other message(s) providing details on the error.
- ACFS-01007: unable to close volume handle
-
Cause: An attempt to close a volume handle failed. The accompanying messages provide detailed information on the failure.
- ACFS-01008: unable to open file system string
-
Cause: File system was not accessible.
- ACFS-01009: unable to close file system handle
-
Cause: An attempt to close a file system handle failed. The accompanying messages provide detailed information on the failure.
- ACFS-01010: Volume already contains an ACFS file system. To reformat the volume, reissue string with the stringf option.
-
Cause: The on-disk metadata indicated that an ACFS file system is located on the volume.
- ACFS-01011: Volume contains an ACFS file system that is being checked. To reformat the volume, reissue string with the stringf option.
-
Cause: The volume contained a file system that was in the process of being checked by fsck (Unix or Linux) or acfschkdsk.exe (Windows).
- ACFS-01014: write of volume label failed
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01015: failed to clear the contents of the volume
-
Cause: An attempt to write to the volume failed. The accompanying messages provide detailed information on the failure.
- ACFS-01017: length of file system name exceeds number
-
Cause: An ACFS file system could not be created because the length of the file system name exceeded the indicated maximum length.
- ACFS-01018: failed to allocate a buffer for number bytes
-
Cause: A request for process virtual memory by the ACFS format command failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01019: This volume contains a mounted ACFS file system. The file system must be dismounted with acfsdismount on all nodes.
-
Cause: The volume was in use by another file system.
- ACFS-01020: This volume contains a mounted non-ACFS file system. The file system must be dismounted with 'advmutil dismount'.
-
Cause: The volume was in use by another non-ACFS file system.
- ACFS-01021: length of volume name exceeds number
-
Cause: An ACFS file system could not be created because the length of the volume name exceeded the indicated maximum length.
- ACFS-01022: failed to bring ADVM volume string online
-
Cause: An ACFS file system could not be created because an error occurred while bringing the volume online. This message is accompanied by other messages providing details on the error.
- ACFS-01025: failed to generate a file system id
-
Cause: An ACFS file system could not be created because an error occurred during the generation of a file system identifier. This message is accompanied by other messages providing details on the error.
- ACFS-01026: storage type mismatch of primary volume and accelerator volume
-
Cause: An ACFS file system could not be created because the supplied primary volume and accelerator volume were different storage types. Storage types include ASM, local volumes.
- ACFS-01033: write to volume failed
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01038: write failed during setup of root directory entry
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01041: write of snaps directory entry failed
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01043: write of lost+found directory entry failed
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01044: write of file entry table failed
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01045: write of global bitmap failed
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01046: read of global bitmap file entry failed
-
Cause: A read of the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01047: write of global bitmap file entry failed
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01049: seek to snap map header failure
-
Cause: A seek to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01050: write to snap map header failure
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01051: partial write to snap map header failure
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01052: write to snap map info entry failure
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01053: partial write to snap map info entry failure
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01054: write to snap map storage entry failure
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01055: partial write to snap map storage entry failure
-
Cause: A write to the volume during file system creation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01094: string cannot be formatted with the supplied options
-
Cause: The file system creation failed because the specified volume was not an ADVM volume. The default set of options requires an ADVM volume. If the specified volume is a local volume, the -l option is required.
- ACFS-01095: unable to determine current directory
-
Cause: An ACFS file system could not be created because an attempt to determine the current directory failed. This message is accompanied by other messages providing details on the error.
- ACFS-01096: length of volume path exceeds number
-
Cause: An ACFS file system could not be created because the length of the volume path exceeded the indicated maximum length.
- ACFS-01113: Block size string is invalid for metadata.
-
Cause: An attempt to create a file system was rejected because the requested metadata block size was invalid.
- ACFS-01150: unable to synchronize in-memory file data to disk
-
Cause: A request to flush all in-memory copies of buffers associated with the open handle failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-01151: Ignoring invalid block size number, using number
-
Cause: An ACFS format command unsupported block size was specified.
- ACFS-01152: The length of accelerator volume name exceeds number.
-
Cause: Accelerator volume name length exceeded the maximum length displayed in the message.
- ACFS-01154: The accelerator volume contains a mounted ACFS file system. The file system must be dismounted with acfsdismount on each node.
-
Cause: The specified volume could not be used as an accelerator volume because it was in use by a mounted file system.
- ACFS-01155: The accelerator volume contains a mounted non-ACFS file system. The file system must be dismounted with 'advmutil dismount'.
-
Cause: The specified volume could not be used as an accelerator volume because it was in use by a mounted non-ACFS file system.
- ACFS-01156: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum 12.1.0.2.0.
-
Cause: An attempt to create a file system with an accelerator volume failed because the ADVM compatibility attribute for the disk group was not set to 12.1.0.2.0 or higher.
- ACFS-01159: The accelerator volume must be different from the volume containing the file system.
-
Cause: The file system could not be created because the same volume was specified for both the accelerator and the file system.
- ACFS-01160: The specified accelerator volume was smaller than the number string required for this file system.
-
Cause: The file system could not be created because the specified accelerator volume was below the minimum allowed size reported in the message.
- ACFS-01164: The specified device 'string' is already in use with a CRS-managed file system.
-
Cause: The file system could not be created because the specified device was already registered with CRS (Cluster Ready Services).
- ACFS-01170: Accelerator volume sector size = number must match primary volume sector size = number
-
Cause: An attempt to create a file system was rejected because the logical sector sizes of primary and accelerator volume were different, as shown. The sector sizes of the primary and accelerator volumes must be the same.
- ACFS-01171: string cannot be formatted as a local file system with ACFS compatibility less than the current release
-
Cause: The file system creation failed because the -l option was specified with a -c option that specified ACFS compatibility for a previous release.
- ACFS-01173: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum 12.2.0.0.0.
-
Cause: An attempt to create a file system failed because the ADVM disk group compatibility had not been upgraded to the indicated version for either the primary or accelerator volume, which is required for that command.
- ACFS-01176: file system format requires volumes with sector size = number
-
Cause: An attempt to create a file system was rejected because the logical sector size of the primary or accelerator volumes was too large for the 512-byte metadata block size format.
- ACFS-01179: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum number.number.number.number.number
-
Cause: An attempt to create a file system failed because the ADVM disk group compatibility had not been upgraded to the indicated version for either the primary or accelerator volume, which is required for that command.
- ACFS-02001: unable to allocate a buffer
-
Cause: A request for process virtual memory by mount command failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-02006: unable to terminate the Oracle Registry connection
-
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry configuration was incomplete/inaccurate.
- ACFS-02012: Mount of string failed, volume string does not exist. Verify that string exists on this node.
-
Cause: Could not mount the file system retrieved from the Oracle Registry.
- ACFS-02014: Mount of string failed. Error number was returned.
-
Cause: Mount operation failed.
- ACFS-02015: Failed to open mount point string. Verify the mount point exists.
-
Cause: Mount point could not be opened.
- ACFS-02016: Mount point, string, is in use by another file system.
-
Cause: The file system could not be mounted because the specified directory was already in use by another file system mount point.
- ACFS-02017: Failed to open volume string. Verify the volume exists.
-
Cause: The volume could not be opened.
- ACFS-02018: Volume string contains an ACFS file system that is being checked. Allow the file system check to complete.
-
Cause: The volume contained a file system that was in the process of being checked by the ACFS checker.
- ACFS-02020: options length exceeds number
-
Cause: An ACFS file system could not be mounted because the length of the options provided exceeded the indicated maximum length.
- ACFS-02021: mount path paired with volume string exceeds number characters
-
Cause: An ACFS file system could not be mounted because the total length of the mount path plus the volume path exceeded the indicated maximum character length.
- ACFS-02026: unable to verify the host names passed in are part of the cluster
-
Cause: Either CSS was unavailable or the CSS configuration was incomplete/inaccurate.
- ACFS-02027: unable to obtain the local CSS node name
-
Cause: Either CSS was unavailable or the CSS configuration was incomplete/inaccurate.
- ACFS-02028: unable to retrieve the list of volumes associated with string
-
Cause: An ACFS file system could not be mounted because an attempt to obtain a list of volumes failed. The accompanying messages provide detailed failure information.
- ACFS-02037: File system not created on a string system. Cannot mount.
-
Cause: An ACFS file system could not be mounted because it was created on a different type of system than the current system.
- ACFS-02038: File system created on an incompatible system (endianness). Cannot mount.
-
Cause: An ACFS file sytem could not be mounted because it was created on a computer which has a different endianness than the current system. Little endianness machines (such as the Intel X86 based systems) store the Least Significant Bit in the first byte of an integer value. Big endianness machines (such as Solaris SPARC and AIX Power based systems) store the Most Significant Bit in the first byte of an integer value.
- ACFS-02039: length of path exceeds number
-
Cause: An ACFS file system could not be mounted because the length of the path exceeded the indicated maximum length.
- ACFS-02040: Path must be a valid directory or drive letter.
-
Cause: An ACFS file system could not be mounted because the mount point path specified was not a valid mount point.
- ACFS-02041: length of volume name exceeds number
-
Cause: An ACFS file system could not be mounted because the length of the volume name exceeded the indicated maximum length.
- ACFS-02043: volume string in use by a non-ACFS file system
-
Cause: The file system could not be mounted because the specified volume was already in use by another file system.
- ACFS-02044: string does not contain a valid ACFS file system. Verify volume contents using acfschkdsk.exe.
-
Cause: The specified file system could not be mounted due to inconsistent file system metadata.
- ACFS-02045: string is in use by another non-ADVM volume
-
Cause: The file system could not be mounted because the specified mount point was already in use by another file system.
- ACFS-02046: Volume string cannot be mounted. Examine the system event log for possible causes.
-
Cause: The volume mount failed. This could be caused by an out of space condition if this is the first mount of a file system on a node.
- ACFS-02048: unable to retrieve full path name for path string
-
Cause: An ACFS file system could not be mounted because an attempt to determine a full path name failed. The accompanying messages provide detailed failure information.
- ACFS-02049: conversion of reparse data Unicode string to ANSI string failed
-
Cause: An ACFS file system could not be mounted because an attempt to convert a unicode string to an ANSI string failed. The accompanying messages provide detailed failure information.
- ACFS-02050: unable to set in-memory mount information
-
Cause: Could not communicate with the mounted file system.
- ACFS-02051: failed to create symbolic link with path string
-
Cause: An ACFS file system could not be mounted because an attempt to create a symbolic link failed. The accompanying messages provide detailed failure information.
- ACFS-02052: broadcast of new symbolic link string failed
-
Cause: An ACFS file system could not be mounted because a system wide broadcast of the symbolic link failed. The accompanying messages provide detailed failure information.
- ACFS-02053: failed to create mount point on directory string
-
Cause: An ACFS file system could not be mounted because the supplied directory could not be turned into a reparse point. The accompanying messages provide detailed failure information.
- ACFS-02054: unable to retrieve a list of active ACFS file systems
-
Cause: An attempt to obtain an active list of ACFS file systems failed. The accompanying messages provide detailed failure information.
- ACFS-02080: Volume string failed to mount due to a version mismatch. Volume version number is not supported by the current driver, which supports a maximum volume version of number.
-
Cause: The volume mount failed because the loaded ACFS driver did not support the volume version of the indicated volume.
- ACFS-02081: Warning: acfschkdsk.exe should be run on volume string at your earliest convenience
-
Cause: A flag in the superblock indicates that a metadata inconsistency has been found on this volume.
- ACFS-02082: unable to verify if the host names provided are part of the cluster
-
Cause: Could not obtain information about the cluster.
- ACFS-02083: cannot get the local CSS node name
-
Cause: Could not obtain local CSS node name.
- ACFS-02088: failed to unlock the volume
-
Cause: An attempt to dismount the ACFS file system failed because the volume could not be unlocked. The accompanying messages provide detailed failure information.
- ACFS-02089: Info: failed to change the volume signature, but continuing with dismount anyway. No action required
-
Cause: An attempt to modify the ACFS file system metadata failed during the dismount. The accompanying messages provide detailed failure information.
- ACFS-02090: unable to retrieve ACFS mount information from CRS
-
Cause: Failed to retrieve mount information the CRS.
- ACFS-02092: Mount of string failed, node string is not a member of the CSS cluster.
-
Cause: Could not mount the file system retrieved from the Oracle Registry.
- ACFS-02119: creating administrative network share for mount point string at share name 'string'
-
Cause: Informational
- ACFS-02120: administrative network share for mount point string already exists at share name 'string'
-
Cause: Informational
- ACFS-02121: administrative network share 'string' already exists, but does not share mount point string
-
Cause: Attempted to create an administrative network share for the specified ACFS mount point, but the required share name was already in use.
- ACFS-02122: retrieving information for administrative network share 'string' failed
-
Cause: While creating an administrative network share for the specified ACFS mount point, failed to retrieve information on any network share that might already exist at the required share name. This message is accompanied by other messages providing details on the error.
- ACFS-02123: creating administrative network share for mount point string at share name 'string' failed
-
Cause: Failed to create an administrative network share for the specified ACFS mount point. This message is accompanied by other messages providing details on the error.
- ACFS-02124: could not create administrative network share for mount point string at share name 'string'
-
Cause: Failed to create an administrative network share for the specified ACFS mount point. This message is accompanied by other messages providing details on the error.
- ACFS-02125: volume 'string' is already in use
-
Cause: The volume was in use by another file system.
- ACFS-02126: Volume string cannot be mounted.
-
Cause: The volume mount failed. This message is accompanied by other messages providing details on the error.
- ACFS-02127: unable to transfer mount data to the ACFS driver
-
Cause: The mount failed because the transfer of mount data from the mount command to the ACFS driver failed. This message is accompanied by other messages providing details on the error.
- ACFS-02128: unable to clean up mount data passed to ACFS driver
-
Cause: The operation to clean up mount data from a temporary location / failed.
- ACFS-02129: Volume string cannot be mounted. Volume is out of space.
-
Cause: The volume mount failed because the volume was out of space.
- ACFS-02130: Volume string cannot be mounted. Volume version does not match the ACFS driver version.
-
Cause: The volume mount failed because the loaded ACFS driver does not support the volume version.
- ACFS-02131: Volume string cannot be mounted. Cluster membership is not established.
-
Cause: The volume mount failed because the ACFS driver could not communicate with Oracle Clusterware.
- ACFS-02132: Volume string cannot be mounted. Insufficient kernel resources to complete the mount.
-
Cause: The volume mount failed due to insufficient kernel resources.
- ACFS-02133: Volume string cannot be mounted. Metadata inconsistency found on-disk.
-
Cause: The volume mount failed due to a metadata inconsistency found in the volume superblock.
- ACFS-02135: Volume string failed to mount due to a version mismatch. Volume version number is not supported by the number.number.number.number.number release.
-
Cause: The volume mount failed because the loaded ACFS driver did not support the volume version of the indicated volume.
- ACFS-02136: Volume string failed to mount due to a version mismatch. Volume version number requires that the loaded ACFS drivers be from the number.number.number.number.number Oracle Database Appliance release.
-
Cause: The volume mount failed because the loaded ACFS driver did not support the volume version of the indicated volume.
- ACFS-02139: Volume string failed to mount. Insufficient options to complete the mount.
-
Cause: The volume mount failed because the -o local option was not specified. This option is required for node local volumes.
- ACFS-02141: Volume string failed to mount. Invalid option combination.
-
Cause: The volume mount failed because the -o local option was specified with an ADVM volume.
- ACFS-03001: Failed to open string. Verify that string exists.
-
Cause: The mount point or file could not be opened.
- ACFS-03002: unable to obtain file system information for string
-
Cause: An attempt to obtain file system information failed. The accompanying messages provide detailed failure information.
- ACFS-03003: Cannot decrease the volume by this amount.
-
Cause: Requested size exceeded the size of the file system.
- ACFS-03004: cannot reduce primary volume size below 200MB
-
Cause: A size request specified a primary volume size less than the minimum allowed.
- ACFS-03005: unable to resize string
-
Cause: An attempt to resize the file system failed. The accompanying messages provide detailed failure information.
- ACFS-03006: smallest size, without loss of data, is: number (numberMB)
-
Cause: A resize request failed because the specified size would result in data loss.
- ACFS-03007: insufficient storage - largest size is: number (numberMB)
-
Cause: A resize request failed because there was not enough storage to accomodate the specified size.
- ACFS-03008: The volume could not be resized. The volume expansion limit has been reached.
-
Cause: The file system's internal storage bitmap has a five extent limit. Growing the file system may fail if it has already been grown four or more times, using up all available storage bitmap extents.
- ACFS-03009: The volume could not be resized at this time. Try again later.
-
Cause: ADVM or ASM was unable to resize the volume.
- ACFS-03012: length of volume name exceeds number
-
Cause: The length of the volume name exceeded the indicated maximum length.
- ACFS-03013: unable to open string
-
Cause: Volume could not be opened to remove the file system.
- ACFS-03014: file system not removed
-
Cause: Failed to remove the ACFS file system from the volume. The accompanying messages provide detailed failure information.
- ACFS-03015: invalid IP address: string
-
Cause: An attempted 'acfsutil repl' command failed because the indicated IP address specification was invalid.
- ACFS-03016: ACFS is busy with online fsck. Try again later.
-
Cause: An attempt to resize a volume was rejected because ACFS was running online fsck.
- ACFS-03018: unsupported operation for local file system string
-
Cause: The requested operation failed because it is not supported by ACFS file systems that are mounted with -o local.
- ACFS-03024: ioctl failed
-
Cause: An attempted utility operation failed because an error occurred in the underlying ioctl operation. The accompanying messages provide detailed failure information.
- ACFS-03025: ioctl call to panic the system failed
-
Cause: An attempt to execute the 'acfsutil panic' command failed because the ioctl request to panic the system failed. The accompanying messages provide detailed failure information.
- ACFS-03027: Invalid product name. Valid product names are OKS, OFS, and AVD.
-
Cause: An attempt to execute the 'acfsutil log' command failed because it was issued with an invalid product name.
- ACFS-03028: Product name not specified. Valid product names are OKS, OFS, and AVD.
-
Cause: An attempt to execute the 'acfsutil log' command failed because no product name was specified.
- ACFS-03029: product name requires a debug level or context
-
Cause: An attempt to execute the 'acfsutil log' command failed because the debug level or context required for the specified product was not provided.
- ACFS-03030: unable to get log buffer size
-
Cause: An attempt to execute the 'acfsutil log' command failed because the ioctl to retrieve log buffer size failed. The accompanying messages provide detailed failure information.
- ACFS-03031: unable to set debug context or level
-
Cause: An attempt to execute the 'acfsutil log' command failed because the ioctl to set the debug context or level failed. The accompanying messages provide detailed failure information.
- ACFS-03032: unable to retrieve log
-
Cause: An attempt to execute the 'acfsutil log' command failed because the ioctl to retrieve the log failed. The accompanying messages provide detailed failure information.
- ACFS-03033: unable to open string
-
Cause: An attempted utility operation failed because the indicated file could not be created and/or opened.
- ACFS-03034: write of log file failed
-
Cause: An attempt to write to the log file failed. The accompanying messages provide detailed failure information.
- ACFS-03035: unable to retrieve mount entries
-
Cause: An attempt to obtain an active list of ACFS file systems failed. The accompanying messages provide detailed failure information.
- ACFS-03036: no mounted ACFS file systems
-
Cause: The system did not have any mounted ACFS file systems.
- ACFS-03037: not an ACFS file system
-
Cause: The specified file or directory was not a part of an ACFS file system.
- ACFS-03038: unable to retrieve list of volumes associated with string
-
Cause: An ACFS informational query failed because an attempt to obtain a list of volumes failed. The accompanying messages provide detailed failure information.
- ACFS-03039: ioctl call to unregister the ACFS driver failed
-
Cause: An ACFS detach command failed because an attempt to unregister the driver failed.
- ACFS-03040: Volumes are still mounted. All ACFS file systems must be dismounted before the ACFS driver can be unregistered.
-
Cause: An ACFS detach command failed to unregister the driver because ACFS file systems were still mounted.
- ACFS-03041: unable to unregister ACFS driver
-
Cause: An ACFS detach command failed because an attempt to unregister the driver failed.
- ACFS-03043: name of snapshot cannot exceed number bytes
-
Cause: At attempt to create a snapshot was rejected because the specified snapshot name was too long.
- ACFS-03044: Failed to open mount point string. Verify the mount point exists.
-
Cause: Mount point could not be opened for snapshot operation.
- ACFS-03045: string is not a mount point
-
Cause: The specified directory was not an ACFS mount point.
- ACFS-03046: unable to perform snapshot operation on string
-
Cause: An attempt to execute the acfsutil snap command failed. The accompanying messages provide detailed failure information.
- ACFS-03048: Snapshot operation could not complete.
-
Cause: An attempt to execute the acfsutil snap command failed. The accompanying messages provide detailed failure information.
- ACFS-03049: There are too many snapshots for the file system associated with string. Reduce the number of snapshots before proceeding.
-
Cause: An attempt to execute the acfsutil snap command failed because there were too many snapshots for the file system.
- ACFS-03050: Cannot create snapshot string. It already exists.
-
Cause: An attempt to create a snapshot failed because a snapshot with the indicated name was found to already exist.
- ACFS-03051: Snapshot string does not exist.
-
Cause: An attempt to execute the acfsutil snap command failed because no snapshot could be found with the indicated name.
- ACFS-03052: unable to delete snapshot string due to open files
-
Cause: An attempt to delete a snapshot failed because there were files open in the snapshot.
- ACFS-03053: Delete of snapshot string succeeded but some disk storage could not be freed. When convenient, run fsck/acfschkdsk to free the storage.
-
Cause: A snapshot was successfully deleted but some of the disk storage could not be freed.
- ACFS-03054: Snapshot string is not a valid snapshot name.
-
Cause: The acfsutil snap command failed because the indicated name was not a valid snapshot name. Possible reasons include: 1) The snapshot name exceeded the limit of 255 characters. 2) The snapshot name equaled "." or "..". 3) The snapshot name contained "/" (Unix or Linux). 4) The snapshot name contained "" or ":" (Windows). 5) The snapshot name contained an illegal character for NTFS file names (Windows).
- ACFS-03055: Snapshot operation failed due to an error on another node. Check Alert logs on other nodes for more details.
-
Cause: An attempt to execute the acfsutil snap command failed because of an error on another node in the cluster.
- ACFS-03089: permission denied
-
Cause: The command failed because the user did not have the required ASM Administrator privilege.
- ACFS-03090: string is an invalid string number
-
Cause: The specified argument value was not a valid numeric value.
- ACFS-03091: Failed to open string. This may mean the string driver is not loaded/running
-
Cause: The driver's control device could not be accessed.
- ACFS-03092: error reading driver tunables
-
Cause: An attempt to read the tunable parameters from the ACFS driver failed. The accompanying messages provide detailed failure information.
- ACFS-03093: no string tunables for this platform
-
Cause: Informational.
- ACFS-03094: invalid value number for tunable parameter string
-
Cause: The specified tunable parameter value was out of range.
- ACFS-03095: tunable parameter string not found
-
Cause: The specified tunable parameter does not exist.
- ACFS-03096: error opening configuration file string
-
Cause: The configuration file cannot be created and/or opened.
- ACFS-03097: error accessing configuration file string
-
Cause: Seek to the end of the configuration file failed.
- ACFS-03098: error writing to configuration file string
-
Cause: An attempt to write to the tunable parameters file failed. The accompanying messages provide detailed failure information.
- ACFS-03099: error updating driver tunables
-
Cause: An attempt to update the kernel version of the tunable parameters failed. The accompanying messages provide detailed failure information.
- ACFS-03106: Invalid combination of arguments. stringa was previously specified to add an ACFS mount point to Oracle Registry.
-
Cause: Invalid option combination.
- ACFS-03107: Invalid combination of arguments. stringd was previously specified to remove an ACFS mount point from the Oracle Registry.
-
Cause: Invalid option combination.
- ACFS-03108: Neither string nor string is an ADVM volume.
-
Cause: Volume specified was not an ADVM volume.
- ACFS-03110: unable to access the Oracle Registry string
-
Cause: Either the Oracle Registry service was unavailable or the registry configuration was incomplete/inaccurate.
- ACFS-03111: unable to add ACFS mount string within Oracle Registry
-
Cause: A request to add the indicated device and mountpoint to the Oracle Registry failed. The accompanying messages provide detailed failure information.
- ACFS-03112: unable to remove mount point string from Oracle Registry
-
Cause: A request to delete the indicated device or mountpoint from the Oracle Registry failed. The accompanying messages provide detailed failure information.
- ACFS-03114: unable to allocate a buffer
-
Cause: A request for process virtual memory by acfsutil registry failed This message is accompanied by other message(s) providing details on the error.
- ACFS-03115: an error occurred while attempting to disconnect from Oracle Registry
-
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry configuration was incomplete/inaccurate.
- ACFS-03117: unable to verify if the hostnames provided are part of the cluster
-
Cause: Could not obtain information about the cluster.
- ACFS-03118: cannot obtain the node number of host string via CSS or the Oracle Registry
-
Cause: Could not determine the node number for the specified host.
- ACFS-03119: Incorrect data format in file 'number'.
-
Cause: The file data was not in the expected format.
- ACFS-03120: Note: Reported snapshot space usage is inaccurate.
-
Cause: The snapshot storage calculated was not expected.
- ACFS-03122: failed to create Oracle Registry ACFS key string string
-
Cause: Failed to create ACFS key(s) SYSTEM.ACFS and/or SYSTEM.ACFS.Mounts in the Oracle Registry.
- ACFS-03123: failed to create Oracle Registry ACFS key string because it already exists
-
Cause: The Oracle Registry ACFS key already exists.
- ACFS-03124: failed to create Oracle Registry ACFS subkey because it already exists
-
Cause: The Oracle Registry mounts subkey already exists.
- ACFS-03125: error retrieving the volume using Oracle Registry key: string
-
Cause: Could not retrieve volume information from mount entry in the Oracle Registry.
- ACFS-03126: error retrieving the mount point using Oracle Registry key: string
-
Cause: Could not retrieve mount point information from mount entry in the Oracle Registry.
- ACFS-03127: error retrieving the mount options using Oracle Registry key: string
-
Cause: Could not retrieve mount options from mount entry in the Oracle Registry.
- ACFS-03128: error retrieving the version using Oracle Registry key: string
-
Cause: Could not retrieve the version for mount entry in the Oracle Registry.
- ACFS-03129: error retrieving the nodes list using Oracle Registry key: string
-
Cause: Could not retrieve the nodes list for mount entry in the Oracle Registry.
- ACFS-03130: Resize request is greater than allowed maximum for ADVM volume.
-
Cause: An attempt to resize an ADVM volume failed because the size requested was larger than the maximum allowed ADVM volume size.
- ACFS-03132: mount point string already exists in the Oracle Registry as:
-
Cause: The indicated mount point was in use in the Oracle Registry.
- ACFS-03133: The Oracle Registry returned the following error while attempting to access the security attributes of key string: \n string
-
Cause: Could not access the security information of Oracle Registry. This message is accompanied by other message(s) from the Registry providing details on the error.
- ACFS-03134: An error occurred while accessing Oracle Registry for a delete mount point operation. string
-
Cause: Could not retrieve data from the Oracle Registry. This message is accompanied by other message(s) providing details on the error.
- ACFS-03135: unable to locate mount point string in Cluster Ready Services
-
Cause: An attempt to access the ACFS mount point failed because the mount point information could not be retrieved from CRS.
- ACFS-03136: unable to locate volume string in Cluster Ready Services
-
Cause: An attempt to access the ASM volume failed because the volume information could not be retrieved from CRS.
- ACFS-03137: Multiple entries exist for the mount point string. Rerun the command with the volume name.
-
Cause: Could not locate unique entry for mount point in the Oracle Registry.
- ACFS-03138: failed to create and set Oracle Registry ACFS mount info key string
-
Cause: Could not create and set a mount info key in the Oracle Registry.
- ACFS-03139: error retrieving the disk group name using Oracle Registry key: string
-
Cause: Could not retrieve the disk group name from the mount entry in the Oracle Registry.
- ACFS-03140: error retrieving the volume name using Oracle Registry key: string
-
Cause: Could not retrieve the volume name from the mount entry in the Oracle Registry.
- ACFS-03141: unable to open device string
-
Cause: The device could not be opened.
- ACFS-03142: Failed to retrieve the diskgroup and volume name for device string. See the attached error.
-
Cause: Possible internal error.
- ACFS-03143: The specified mount point does not exist and therefore cannot be deleted.
-
Cause: The Oracle Registry has not been configured for ACFS or the specified mount point does not exist.
- ACFS-03145: unable to remove ACFS volume string from Oracle Registry
-
Cause: Could not remove volume from Oracle Registry.
- ACFS-03146: Warning: The ACFS mount point group ownership cannot be re-initialized in the Oracle Registry. The registry is initialized from the ACFS control device on first use, and may have changed ownership since then. Current Key Ownership: string
-
Cause: An attempt was made to re-initialize the ACFS mount point group ownership in the Oracle Registry. This may be because the ACFS control device /dev/ofsctl or /dev/acfsctl has changed owners.
- ACFS-03147: invalid ACFS file identifier provided
-
Cause: The ACFS file identifier provided by the user had an illegal value.
- ACFS-03148: ioctl call to obtain pathname associated with file id number failed
-
Cause: An internal ioctl operation to map from an ACFS file identifier to a pathname failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-03149: constructed path name is longer than system limit of number characters
-
Cause: The length of the pathname being constructed has exceeded the system limit of %d characters. This may be due to changes in the file system namespace while the command is running.
- ACFS-03151: The ACFS file identifier provided is not associated with a user file or directory.
-
Cause: The ACFS file identifier, although valid, was not for a user file or directory.
- ACFS-03152: The ACFS file identifier provided is invalid for the mountpoint specified.
-
Cause: The ACFS file identifier was not a valid identifier for the mountpoint specified.
- ACFS-03153: The file system name space has changed and a pathname cannot be obtained.
-
Cause: The ACFS file identifier was valid, but could not be used to obtain a full file pathname.
- ACFS-03154: Failed to determine the full pathname. Too many directory levels.
-
Cause: acfsutil has received information from the operating system that it could not process fully.
- ACFS-03157: unsupported file type for string, not a mount point
-
Cause: An invalid entry was passed on the command line.
- ACFS-03158: unsupported file type for string, not a mount point or a file
-
Cause: An invalid entry was passed on the command line.
- ACFS-03161: Device : string : Mount Point : string already exists in the Oracle Registry
-
Cause: This entry has already been added to the Oracle Registry.
- ACFS-03162: Warning: The file system was resized, but an error occurred while resizing the ADVM volume. File system size now number MB, volume size number MB.
-
Cause: An error occurred during ADVM volume resize.
- ACFS-03165: Unable to add the file system on device string to the ACFS registry. It is currently managed by CRS.
-
Cause: The file system is currently managed by CRS and a file system cannot be managed by both CRS and the ACFS registry.
- ACFS-03166: Unable to add a STOP_DEPENDENCY to the ACFS registry for device string.
-
Cause: The ACFS registry resource could not be updated.
- ACFS-03167: Unable to remove the STOP_DEPENDENCY for device string from the ACFS registry.
-
Cause: The ACFS registry resource could not be updated.
- ACFS-03168: Internal error: string number
-
Cause: An Oracle internal error.
- ACFS-03169: Unable to set log file size.
-
Cause: The ACFS driver was unable to set the log file size.
- ACFS-03170: Minimum log file size is number.
-
Cause: The ACFS driver was unable to set the log file size.
- ACFS-03171: insufficient contiguous free ASM Diskgroup space
-
Cause: An attempt to resize an ADVM volume failed because ASM did not have enough contiguous free diskgroup storage. This could have been a transient condition if ASM rebalance was running, otherwise the ASM alert logs may provide detailed failure indications.
- ACFS-03172: ADVM is busy with Mirror recovery. Try again later.
-
Cause: ADVM could not resize the volume because it is recovering the mirrored volumes.
- ACFS-03173: ADVM or ASM is unable to resize the volume. Check the ASM alert log.
-
Cause: ADVM or ASM is unable to resize the volume.
- ACFS-03174: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than 11.2.0.3.0.
-
Cause: The creation of a read/write snapshot was rejected because the ADVM disk group compatibility had not been upgraded to 11.2.0.3.0 or higher, which is required for that command.
- ACFS-03177: maximum log file size cannot exceed number MB
-
Cause: The ACFS driver was unable to set the log file size.
- ACFS-03178: unable to delete snapshot string while cluster is in rolling migration
-
Cause: The cluster was in rolling migration. Snapshot deletions are not allowed during rolling migration.
- ACFS-03179: unable to create snapshot 'string' while cluster is in rolling migration
-
Cause: The cluster was in rolling migration. Snapshot creations are not allowed during rolling migration.
- ACFS-03180: Unable to obtain ASM volume device information for 'string'
-
Cause: The operation for retrieval of ASM volume device information failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-03182: Device name 'string' does not exist.
-
Cause: An attempt to execute the 'advmutil canonical' command failed because no device could be found with the indicated name.
- ACFS-03185: Unable to obtain ASM volume extent information for string
-
Cause: The operation for retrieval of ASM volume extent information failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-03186: Supplied ACFS file offset value exceeded the maximum of the file and allocation sizes of number.
-
Cause: The supplied file offset value in bytes exceeded both the file size and allocation size.
- ACFS-03187: Extent number (mirror number) is not in use.
-
Cause: Informational
- ACFS-03197: unable to delete snapshot string while it is configured for use by ACFS replication
-
Cause: An attempt to delete a snapshot was rejected because it was configured for use by ACFS replication.
- ACFS-03198: unable to delete snapshot string as a component of ACFS replication
-
Cause: An attempt to delete a snapshot was rejected because it was not
- ACFS-03199: unable to convert snapshot string because it is replication-specific
-
Cause: An attempt was made to convert a replication-specific snapshot while replication was running.
- ACFS-03203: Invalid snap command.
-
Cause: An invalid entry was passed on the command line.
- ACFS-03204: Snapshot 'string' is already read-only.
-
Cause: A request was made to convert a snapshot to be read-only but the snapshot was already read-only.
- ACFS-03205: Snapshot 'string' is already read-write.
-
Cause: A request was made to convert a snapshot to be read-write but the snapshot was already read-write.
- ACFS-03206: The ADVM compatibility attribute for the diskgroup was below the required version (string) for the 'acfsutil snap convert' command.
-
Cause: The 'acfsutil snap convert' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-03207: invalid combination of options
-
Cause: The 'acfsutil snap convert' command was passed an invalid option combination which included both the -r and -w options.
- ACFS-03208: The /r option is not supported on this operating system
-
Cause: The 'acfsutil snap convert /r' option was specified. This functionality requires a minimum operating system version of Windows Server 2008 R2.
- ACFS-03212: There are too many snapshots for the file system associated with string. Only number are allowed. Reduce the number of snapshots before proceeding.
-
Cause: An attempt to create more than the maximum allowed number of active snapshots was rejected.
- ACFS-03213: Creation of a snapshot failed due to presence of snapshots that prevent this functionality.
-
Cause: A snapshot creation which specified a parent snapshot was not processed because of compatibility issues with existing snapshots. Possible causes include: 1) Snapshots of the file system were found that were created before ADVM compatibility attribute was set to 12.1. 2) Snapshots of the file system were found that were created after ADVM compatibility was set to 12.1 but while 11.2 snapshots existed.
- ACFS-03214: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than 12.1.
-
Cause: The creation of a snapshot with a parent snapshot was rejected because the ADVM disk group compatibility had not been upgraded to version 12.1 or higher, which is required for that command.
- ACFS-03216: The ADVM compatibility attribute for the diskgroup was below the required version (string) for unlimited volume expansions.
-
Cause: A request to resize the ACFS file system failed because the volume expansion limit was reached. This limit was in effect because the ADVM compatibility attribute associated with the disk group had not been upgraded to the indicated version, which is required for that command.
- ACFS-03228: unable to retrieve metadata statistics for primary volume associated with mount point string
-
Cause: An internal ioctl operation to retrieve ACFS metadata statistics failed. This message is accompanied by other messages providing details on the error.
- ACFS-03229: unable to retrieve metadata statistics for accelerator volume associated with mount point string
-
Cause: An internal ioctl operation to retrieve ACFS metadata statistics failed. This message is accompanied by other messages providing details on the error.
- ACFS-03243: failed to write Hang Manager entries to the kernel in-memory and persistent logs
-
Cause: An internal ioctl operation to write Hang Manager data to the in-memory and persistent logs failed. This message is accompanied by other messages providing details on the error.
- ACFS-03244: The specified numeric value string is outside the valid range.
-
Cause: The indicated numeric argument was rejected because it was too long to be converted to a 64-bit internal representation.
- ACFS-03255: accelerator volume not replaced
-
Cause: An attempt to replace the accelerator volume failed. This message is accompanied by other messages providing details on the error.
- ACFS-03256: primary volume has no accelerator volume to replace
-
Cause: An attempt to replace the accelerator volume was rejected because the specified volume did not have an accelerator volume associated with it.
- ACFS-03257: the specified primary volume is an accelerator volume. Cannot proceed.
-
Cause: An attempt to replace an accelerator volume was rejected because the volume specified as the primary volume was not a primary volume.
- ACFS-03258: the specified replacement accelerator volume must be at least as large as the accelerator volume it is to replace.
-
Cause: An attempt to replace the accelerator volume was rejected because the specified replacement volume was smaller than the current accelerator volume.
- ACFS-03263: Volume signature indicates that an accelerator operation is in progress.
-
Cause: An attempt to perform a filesystem check could not be completed because metadata showed that an accelerator operation was either in progress or incomplete on the specified volume.
- ACFS-03264: 'acfsutil accel replace' failed due to a version mismatch. The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than number.number.number.number.number.
-
Cause: An attempt to replace an accelerator volume was rejected because the ADVM disk group compatibility had not been upgraded to the release specified in the message or higher, which is required for the operation.
- ACFS-03265: 'acfsutil accel replace' interrupted. Ensure primary volume is accessible then run 'acfsutil accel replace' with the same arguments again to complete the operation.
-
Cause: An event or condition interrupted the execution of the 'acfsutil accel replace' command. This message is accompanied by other messages providing details on the error.
- ACFS-03266: The specified new accelerator volume is already the accelerator volume that corresponds to the specified primary volume.
-
Cause: The specified new accelerator volume was the same as the accelerator volume it was to replace. This state may occur because another operation instructed 'acfsutil accel replace' be run again with the same arguments to recover from or complete a failed accelerator replacement. This message will also be seen as a result of accidentally rerunning the same command.
- ACFS-03267: Volume signature indicates that an accelerator operation is in progress.
-
Cause: An attempt to format a volume could not be completed because an accelerator operation was either in progress or incomplete on the specified volume.
- ACFS-03268: Cannot use volume string. It contains an existing ACFS file system or is being used as an accelerator.
-
Cause: An attempt to replace a file system's accelerator volume was rejected because the on-disk metadata of the indicated volume showed that a valid ACFS file system was located on the volume or that it was an existing accelerator.
- ACFS-03270: New accelerator volume sector size (number) must match existing accelerator volume sector size (number).
-
Cause: An attempt to execute 'acfsutil accel replace' was rejected because the logical sector sizes of the existing and specified new accelerator volumes were different, as shown. The sector size of the accelerator volume must remain the same as the sector size of the associated primary volume.
- ACFS-03271: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the diskgroup was below the required version (string) for the 'acfsutil snap quota' command.
-
Cause: The 'acfsutil snap quota' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-03272: The specified primary volume string does not appear to contain an ACFS file system.
-
Cause: An attempt to replace a primary volume's accelerator volume failed because the on-disk metadata of the indicated primary volume did not show that a valid ACFS file system was located on the volume.
- ACFS-03273: Volume signature indicates that an accelerator operation is in progress.
-
Cause: An attempt to mount a file system could not be completed because an accelerator operation was either in progress or incomplete on the specified volume.
- ACFS-03274: Snap quota can not be enabled for this snapshot.
-
Cause: The command 'acfsutil snap quota' was rejected because the snapshot was created from a file system whose compatibility level was less than 12.2.
- ACFS-03275: Updating CRS dependencies for resource 'string'.
-
Cause: Informational.
- ACFS-03276: CRS dependencies were updated successfully.
-
Cause: Informational.
- ACFS-03277: failed to update CRS resource
-
Cause: An attempt to replace the accelerator failed because an error occurred while updating a resource. The accompanying messages from CRS provide detailed failure information.
- ACFS-03278: restarting replace operation
-
Cause: The metadata of the supplied volumes indicated that a previous invocation of 'acfsutil accel replace' with the same arguments as this one was interrupted before completion. This invocation attempted to complete the replace operation.
- ACFS-03279: The file system on the specified primary volume string is either in use or has been removed.
-
Cause: An attempt to replace a primary volume's accelerator volume failed because the on-disk metadata of the indicated primary volume showed that the file system was either in use or had been removed.
- ACFS-03280: failed to increase log size and change log level of in-memory log on all nodes
-
Cause: An attempt to increase log size and change log level on all nodes of the cluster failed because an error occurred while sending the request to every node.
- ACFS-03281: failed to reset log size and log level of in-memory log on all nodes
-
Cause: An attempt to reset log size and change log level on all nodes of the cluster failed because an error occurred while sending the request to every node.
- ACFS-03283: invalid combination of -o and -f options
-
Cause: The 'acfsutil log' command was issued with both the -f and -o options. This is a conflict, because the log file names are pre-specified for -o and may not be specified using -f.
- ACFS-03284: invalid combination of -o and -n, -T, -c, -s, -q options
-
Cause: The 'acfsutil log -o' command is incompatible with other options included in the commmand line. The -o option can not be combined with the -n, -T, -c, -s, or -q options.
- ACFS-03286: failed to find volume resource for device string
-
Cause: An attempt to replace an accelerator volume with the command 'acfsutil accel replace' failed because the volume resource for the indicated device was not found.
- ACFS-03287: unable to find old accelerator volume resource name
-
Cause: An attempt to replace an accelerator volume with the command 'acfsutil accel replace' failed because the old accelerator resource could not be found because the file system resource dependencies were not correct.
- ACFS-03288: CRS dependencies already had the requested values.
-
Cause: A request to update the dependencies for a file system resource was ignored because the dependencies already had the requested values.
- ACFS-03290: The Oracle ADVM compatibility level for the disk group is less than the required version 18.0.0.0.0 for snap link.
-
Cause: The 'acfsutil snap link' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-03291: Only one snaphshot link can be created for this snapshot.
-
Cause: The command 'acfsutil snap link' was rejected because the snapshot already had a snapshot link.
- ACFS-03294: Insufficient privileges to perform command. Resource Administrator access is required.
-
Cause: An attempt to execute an acfsutil command was rejected because the caller did not have sufficient privileges.
- ACFS-03295: Invalid freeze or thaw command.
-
Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected because an invalid option was specified. The 'acfsutil thaw' command does not accept any options. The 'acfsutil freeze' command accepts the '-f' option only.
- ACFS-03296: cannot freeze or thaw file system string because the Grid Infrastructure has not been upgraded to string
-
Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected because the Grid Infrastructure had not been upgraded to the indicated version.
- ACFS-03297: unable to freeze file system string
-
Cause: The file system could not be frozen. The accompanying messages provide detailed failure information.
- ACFS-03298: unable to thaw file system string
-
Cause: The file system could not be thawed from a frozen state. The accompanying messages provide detailed failure information.
- ACFS-03299: cannot freeze or thaw file system string because the cluster is in rolling migration
-
Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected because the cluster was in rolling migration. Freezing or thawing a file system during rolling migration was not supported.
- ACFS-03300: unable to set tag name on file string
-
Cause: The ACFS driver was unable to complete the request.
- ACFS-03301: unable to unset tag name on file string
-
Cause: The ACFS driver was unable to complete the request.
- ACFS-03302: tag name syntax invalid or length too long
-
Cause: Tag name contains invalid characters or has too many characters.
- ACFS-03303: invalid combination of arguments
-
Cause: The acfsutil tag info -t or -r arguments work only on file pathnames.
- ACFS-03304: Unable to open mount point string. Verify that the mount point exists.
-
Cause: Mount point cannot be opened to display tag name information.
- ACFS-03305: unable to retrieve all tag names for string
-
Cause: Unable to return the full list of tag names.
- ACFS-03306: tag name does not exist in file string
-
Cause: Cannot unset a tag name on a file that does not exist.
- ACFS-03308: The ADVM compatibility attribute for the diskgroup must be set to version 11.2.0.2.0 to allow the acfsutil repl and tag commands.
-
Cause: The acfsutil command was rejected because the ADVM disk group compatibility had not been upgraded to 11.2.0.2.0 or higher, which is required for that command.
- ACFS-03309: path name string does not resolve to an ACFS file system
-
Cause: A path name supplied on an 'acfsutil tag' command did not resolve to an ACFS file system.
- ACFS-03310: amount of change since mount: number MB
-
Cause: Informational
- ACFS-03313: unable to collect ACFS statistics for mount point string
-
Cause: 'acfsutil info fs -s' was unable to communicate with the ACFS driver.
- ACFS-03314: interval cannot exceed number seconds
-
Cause: Statistics interval exceeded maximum number of seconds per interval.
- ACFS-03315: count cannot exceed number
-
Cause: Number of statistics intervals exceeded maximum number allowed.
- ACFS-03316: interval must be a positive integer
-
Cause: A zero or negative integer was provided.
- ACFS-03317: unable to set tag on file "string" because its tag name storage is full
-
Cause: The limit of the file's tag name storage has been reached.
- ACFS-03318: unable to set tag name "string" because this name is reserved
-
Cause: The tag name specified is reserved.
- ACFS-03319: Set tag on file: string
-
Cause: Informational
- ACFS-03320: Removing tag(s) on file: string
-
Cause: Informational
- ACFS-03321: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil tag' commands.
-
Cause: The 'acfsutil tag' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-03322: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil repl' commands.
-
Cause: The 'acfsutil repl' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-03323: stringc option requires the stringt option
-
Cause: The 'c' option was specified without the 't' option. The 'c' option invokes case insensitive substring matching on the tag names specified using the 't' option.
- ACFS-03324: Unable to obtain metric data for string
-
Cause: An internal ioctl operation to access metric data from ACFS file system failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-03344: Error, strings option with repetition interval applied to multiple file systems.
-
Cause: A request to report file system statistics periodically was rejected because it applied to multiple file systems. A single file system must be specified explicitly when supplying the 's' option with a time interval.
- ACFS-03345: cannot reduce accelerator volume size below 256MB
-
Cause: A size request specified an accelerator volume size less than the minimum allowed.
- ACFS-03346: unable to grow the accelerator volume in support of a request to grow the primary volume
-
Cause: A size request required growth of the accelerator volume, which failed. This message is accompanied by other messages providing details on the error.
- ACFS-03347: Error, strings option with repetition interval applied to multiple file systems (string).
-
Cause: A request to report file system statistics periodically was rejected because it applied to multiple file systems. A single file system must be specified explicitly when supplying the 's' option with a time interval.
- ACFS-03348: cannot display file system statistics and individual items at the same time
-
Cause: An attempt to display file system statistics was rejected because one or more of the -s or -d options were specified with the -o option. The display of statistics and the display of individual items are mutually exclusive.
- ACFS-03349: cannot display detailed file system statistics without specifying the statistics option
-
Cause: An attempt to display file system statistics was rejected because the -d option was specified without the -s option. The detail option -d augments the -s option and cannot be used alone.
- ACFS-03350: cannot display file system statistics and fragmentation at the same time
-
Cause: An attempt to display file system statistics was rejected because the -s option was specified with the -f option. The display of statistics and the display of fragmentation are mutually exclusive.
- ACFS-03351: cannot display file system fragmentation and individual items at the same time
-
Cause: An attempt to display file system fragmentation was rejected because the -f option was specified with the -o option. The display of fragmentation and the display of individual items are mutually exclusive.
- ACFS-03352: cannot display file system fragmentation without specifying the fragmentation option
-
Cause: An attempt to display file system fragmentation was rejected because the -v option was specified without the -f option. The verbose option -v augments the -f option and cannot be used alone.
- ACFS-03353: invalid count value supplied
-
Cause: An attempt to display file system statistics was rejected because a zero or negative integer was provided for the count argument.
- ACFS-03354: local statistics dump failed
-
Cause: An attempt to save ACFS file system statistics failed. The accompanying messages provide detailed failure information.
- ACFS-03355: state dump failed
-
Cause: An attempt to save ACFS binary log data failed. The accompanying messages provide detailed failure information.
- ACFS-03400: Invalid repl toggle command.
-
Cause: The command was rejected because an invalid sub-command was specified.
- ACFS-03450: Continue to panic the cluster [y|n] ?
-
Cause: The 'acfsutil panic' command was issued to panic the cluster.
- ACFS-03451: Continue to panic the system [y|n] ?
-
Cause: The 'acfsutil panic' command was issued to panic the system.
- ACFS-03452: failed to move file or directory from string to string
-
Cause: An attempt to rename a file or directory failed because the target was an existing, populated directory or the user permissions were insufficient to perform the operation.
- ACFS-03461: 'accel add' aborted because one node of the cluster did not unmount properly
-
Cause: An attempt to add an accelerator volume was aborted because one node of cluster had crashed prior to running 'acfsutil accel add' command.
- ACFS-03462: accelerator volume not added
-
Cause: An attempt to add an accelerator volume failed. This message is accompanied by other messages providing details on the error.
- ACFS-03463: 'acfsutil accel add' failed due to a version mismatch. The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than number.number.number.number.number.
-
Cause: An attempt to add an accelerator volume was rejected because the ADVM disk group compatibility had not been upgraded to the release specified in the message or higher, which was required for the operation.
- ACFS-03464: restarting add operation
-
Cause: The metadata of the specified volumes indicated that a previous invocation of 'acfsutil accel add' with the same arguments had been interrupted before completion. The current invocation attempted to complete the add operation.
- ACFS-03465: 'acfsutil accel add' interrupted. Ensure primary volume is accessible then run 'acfsutil accel add' with the same arguments again to complete the operation.
-
Cause: An event or condition interrupted the execution of the 'acfsutil accel add' command. This message is accompanied by other messages providing details on the error.
- ACFS-03466: Primary volume has an accelerator volume
-
Cause: An attempt to an the accelerator volume was aborted because the specified primary volume has already had an accelerator volume.
- ACFS-03467: write of Rollback_Log failed
-
Cause: An attempt to add an accelerator volume failed because of an error in a write operation to the primary volume. The accompanying messages provide additional details on the error.
- ACFS-03468: Unable to roll back the operation of add accelerator.
-
Cause: An attempt to roll back the add accelerator operation failed. This message is accompanied by other messages providing details on the error.
- ACFS-03469: Write failed at disk offset: string size: number bytes.
-
Cause: An attempt to write at the indicated disk offset failed. This message is accompanied by other messages providing details on the error.
- ACFS-03500: Unable to access kernel persistent log entries.
-
Cause: Could not get or set persistent log configuration data.
- ACFS-03501: The 'query' option may not be used with any other options.
-
Cause: Additional options to 'query' were specified on the command line.
- ACFS-03502: The specified maximum log file size is less than number MB or is greater than number MB.
-
Cause: An invalid log file size was entered on the command line.
- ACFS-03503: The specified interval is less than number seconds.
-
Cause: An invalid interval value was entered on the command line.
- ACFS-03504: An invalid high water level value (number percent) was specified.
-
Cause: The high water level must be greater than the low water level and less than 100 percent.
- ACFS-03505: An invalid low water level value (number percent) was specified.
-
Cause: The low water level must be greater than zero and less than the high water level.
- ACFS-03506: The selected percentage does not generate an even integer. Changing to number percent.
-
Cause: The specified percentage of the buffer size generates a remainder.
- ACFS-03507: The specified buffer size is less than number KB or is greater than number KB.
-
Cause: An invalid buffer size value was entered on the command line."
- ACFS-03508: The specified maximum number of log files is less than number or greater than number.
-
Cause: An invalid maximum number of log files was entered on the command line.
- ACFS-03509: string is not a Grid infrastructure home.
-
Cause: An invalid Grid infrastructure home was entered on the command line.
- ACFS-03510: There are more log files on the system than are being configured. Removing the oldest files.
-
Cause: A new, lower, maximum number of allowable Oracle Kernel Services (OKS) persistent log files was configured and there are currently more log files on the system. Deleting the oldest files."
- ACFS-03511: Deleting string.
-
Cause: A log file was deleted to satisfy the new configuration.
- ACFS-03512: Renaming string to string.
-
Cause: A log file was renamed to place it in time modified sequential order.
- ACFS-03513: The OKS persistent log configuration settings cannot be queried.
-
Cause: The Oracle Kernel Services (OKS) persistent log was not running.
- ACFS-03514: The directory 'string' can not be converted to an absolute path.
-
Cause: A directory name was specified that could not be converted to an absolute path. The name was either an invalid relative path or, on Windows, included an invalid drive letter.
- ACFS-03528: failed to determine Oracle Base
-
Cause: The operation to retrieve the Oracle Base location failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-03529: Warning: The 'd' option was specified with an argument, which is no longer used - argument ignored.
-
Cause: 'acfsutil plogconfig' now gets the log location internally. The specified log location was ignored and the command continued using the internally derived location.
- ACFS-03530: The 'terminate' option may not be used with any other options.
-
Cause: Conflicting options were specified on the command line.
- ACFS-03531: Snapshot link string does not exist.
-
Cause: An attempt to execute the acfsutil snap link command failed because no snapshot link could be found with the indicated name.
- ACFS-03532: The specified string string is not a valid snapshot link name.
-
Cause: The acfsutil snap link command failed because the indicated name was not a valid snapshot link name. Possible reasons include: 1) The snapshot link name exceeded the limit of 255 characters. 2) The snapshot link name equaled "." or "..". 3) The snapshot link name contained "/" (Unix or Linux). 4) The snapshot link name contained "" or ":" (Windows). 5) The snapshot link name contained an illegal character for NTFS file names (Windows).
- ACFS-03533: compression operation failed because the cluster is in rolling migration
-
Cause: An 'acfsutil compress' command was rejected because the cluster was in rolling migration. Compressing files during rolling migration was not supported.
- ACFS-03534: cannot read from file: string
-
Cause: Execution of a requested application failed because it encountered an error in attempting to read from the indicated file. Additional messages provide detailed failure information.
- ACFS-03539: Base time stamp not found in log file.
-
Cause: Informational. The likely cause is that the running Oracle Kernel Services (OKS) driver is an older version that does not support time stamp conversion.
- ACFS-03540: The specified interval is greater than number seconds.
-
Cause: An invalid interval value was entered on the command line.
- ACFS-03541: The symbolic link 'string' to 'string' cannot be created.
-
Cause: An attempt to start Oracle Kernel Services persistent logging was not completely successful. Logging was started, but the indicated symbolic link could not be created. Most likely the link name was non-empty directory.
- ACFS-03542: The specified OKS log directory 'string' is invalid because it is NFS mounted.
-
Cause: The indicated logging directory was NFS mounted.
- ACFS-03543: The OKS persistent log is not active.
-
Cause: The Oracle Kernel Services (OKS) persistent log was not running.
- ACFS-03544: Directory 'string' exists as a file.
-
Cause: An Oracle Kernel Services (OKS) persistent log directory could not be created because it exists as a file.
- ACFS-03545: The input text is longer than the maximum of number bytes.
-
Cause: The command failed because input text was too long.
- ACFS-03546: failed to update the debug levels for the specified binary log
-
Cause: The 'acfsutil blog' command encountered an error while attempting to update the binary log debug levels.
- ACFS-03547: unable to create snapshot link while replication v1 is active
-
Cause: An attempt to execute the acfsutil snap link command failed because replication v1 is active.
- ACFS-03548: snapshot link cannot be created at the specified path
-
Cause: An attempt to execute the acfsutil snap link command failed because the link is not allowed at the specified path. Possible reasons include: 1) The path is in .ACFS 2) The path is in another snapshot 3) The path is a replication standby
- ACFS-03549: snapshot link cannot be created because the specified path already exists
-
Cause: An attempt to execute the acfsutil snap link command failed because a file already exists at the specified path.
- ACFS-03602: Plug-in is already enabled on 'string'
-
Cause: An attempt was made to enable the plug-in when it is already enabled.
- ACFS-03603: Plug-in is not enabled on 'string'
-
Cause: A plug-in command was attempt when the plug-in is not enabled.
- ACFS-03604: Unable to perform plug-in operation on 'string'
-
Cause: The plug-in operation failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-03610: Invalid plug-in metric type: string
-
Cause: An invalid plug-in metric type was specified.
- ACFS-03611: Invalid interval specified.
-
Cause: An invalid interval was specified.
- ACFS-03612: Unable to retrieve list of plug-in enabled tags.
-
Cause: ACFS was unable to retrieve the list of tags for which the plug-in is collecting metrics. This message is accompanied by other message(s) providing details on the error.
- ACFS-03613: Unable to write plug-in config file.
-
Cause: ACFS was unable to write the plug-in config file to disk.
- ACFS-03614: Plug-in cannot be enabled for more than number tags.
-
Cause: An attempt was made to enable the plug-in for more than the maximum allowed number of tags.
- ACFS-03615: An error occured when copying the list of tags.
-
Cause: This is an internal error.
- ACFS-03621: missing plug-in metric type
-
Cause: No plug-in metric type was specified.
- ACFS-03623: unable to modify the ACFS registration for mount point 'string'
-
Cause: Could not modify the ACFS registration for the specified mount point.
- ACFS-03624: unable to modify registration for ACFS volume 'string'
-
Cause: Could not modify the ACFS registration for the ACFS volume.
- ACFS-03626: invalid combination of -C and -f options
-
Cause: The 'acfsutil log' command was issued with both the -f and -C options. This is a conflict, because the log file names are pre-specified for -C and may not be specified using -f.
- ACFS-03627: logging behavior change specified with cluster option
-
Cause: The 'acfsutil log' command was issued with both the -C option and and an option that modifies the logging behavior.
- ACFS-03637: corruption detected in log file 'string'
-
Cause: The 'acfsutil logconvert' command detected a corrupted log entry.
- ACFS-03641: auto-resize increment below minimum numberG
-
Cause: An attempt to update auto-resize settings specified an auto-resize increment less than the minimum allowed.
- ACFS-03643: failed to update auto-resize settings
-
Cause: The ACFS driver was unable to update the auto-resize settings.
- ACFS-03644: No auto-resize increment is currently configured.
-
Cause: An attempt was made to set an auto-resize maximum when no auto-resize increment was set.
- ACFS-03645: File system of size number string requires an accelerator volume of size number string for best performance, which is larger than the current accelerator volume size number string.
-
Cause: The file system was resized such that the accelerator volume size was then below the minimum size recommended for best performance.
- ACFS-03655: Too many read failures on device string. Exiting.
-
Cause: An attempt to retrieve the metadata from the indicated device was terminated because there were too many read errors. The accompanying error messages provide additional failure details.
- ACFS-03656: invalid compression unit size: number bytes\n Valid compression unit sizes are string bytes.
-
Cause: An invalid value for compression unit size was provided.
- ACFS-03657: Directory string is not on an ACFS Volume.
-
Cause: The specified output directory was not located on an ACFS Volume.
- ACFS-03658: Too many file names were specified.
-
Cause: There were too many file names for the the options being used.
- ACFS-03659: No files to copy were specified.
-
Cause: There were no file names to copy specified.
- ACFS-03660: Compression is not enabled on the volume containing directory string.
-
Cause: The target ACFS volume did not have compression enabled.
- ACFS-03662: partial write during copy of file string
-
Cause: A write to the volume during file copy failed. This message is accompanied by other messages providing details on the error.
- ACFS-03671: failed to set compression information for file string
-
Cause: An internal ioctl operation to set compression information for a file failed. This message is accompanied by other messages providing details on the error.
- ACFS-03674: Pathname string is not a directory.
-
Cause: The pathname following the -r option was not a directory.
- ACFS-03676: Pathname string is not a directory or a regular file.
-
Cause: The pathname provided was not a directory or a regular file.
- ACFS-03677: no output directory specified
-
Cause: No output directory was found in the command line.
- ACFS-03678: too many directories specified
-
Cause: The parameters provided contain more directories than expected for the options used.
- ACFS-03679: File string is a file type that cannot be compressed.
-
Cause: The file specified with the -c option was a type of file that cannot be compressed.
- ACFS-03680: File system path string already exists. Compress copy of file string will not execute.
-
Cause: An attempt to execute the acfsutil compress copy command failed because the indicated destination path name already existed and the forced overwrite option was not specified.
- ACFS-03681: No files were copied.\n
-
Cause: An attempt to execute the acfsutil compress copy command failed because no files could be copied. This message is accompanied by other messages providing detailed failure information.
- ACFS-03682: File system path string is not a regular file.
-
Cause: The specified path name was not a regular file.
- ACFS-03683: File system path string is not a directory.
-
Cause: The last path name specified was not a directory.
- ACFS-03684: File string with internal block size string bytes is being compressed with compression unit size string bytes. It will not be usable by the RDBMS.
-
Cause: The file was copied with a compression unit size that prevents the database from using it.
- ACFS-03685: File system path string cannot be converted to an absolute path.
-
Cause: A path name was specified that could not be converted to an absolute path. The name was either an invalid relative path or, on Windows, included an invalid drive letter.
- ACFS-03691: successful update of mount point 'string' to ACFS compatibility level with number.number.number.number.numberstring release stream
-
Cause: Informational.
- ACFS-03692: Failed to update ACFS compatibility level for mount point 'string'. The active ACFS compatibility level (number.number.number.number.numberstring) is a higher release than the requested release.
-
Cause: The internal ioctl operation to set ACFS compatibility level for a mounted file system failed because the active ACFS compatibility level is higher than the requested release stream.
- ACFS-03693: failed to get ACFS compatibility level for mount point 'string'
-
Cause: An internal ioctl operation to get the ACFS compatibility level for a mounted file system failed. This message is accompanied by other messages providing details on the error.
- ACFS-03695: Invalid release supplied. Requested version of number.number.number.number.number exceeds the active version of the cluster (number.number.number.number.number).
-
Cause: The release supplied was higher than the active version of the cluster.
- ACFS-03696: Invalid release supplied.
-
Cause: The supplied release was invalid.
- ACFS-03697: The ACFS compatibility level must be set to number.number.number.number.number or higher to proceed.
-
Cause: The specified ACFS compatibility level was too low to support the supplied list of options.
- ACFS-03700: failed to set ACFS compatibility level for mount point 'string'
-
Cause: An internal ioctl operation to set ACFS compatibility level for a mounted file system failed. This message is accompanied by other messages providing details on the error.
- ACFS-03731: The Oracle ADVM compatibility level for the disk group is less than the required version 12.2 for auto-resize.
-
Cause: An attempt to enable auto-resize was rejected because the ADVM disk group compatibility level had not been upgraded to the indicated version, which is required for that command.
- ACFS-03732: Skipping invalid or non-numeric -o entry string.
-
Cause: An attempt to copy an item from the additional offset list (-o) encountered the indicated non-numeric or invalid entry. The indicated invalid entry was skipped.
- ACFS-03733: Too many -o arguments. Ignoring entries beyond number.
-
Cause: The command 'acfsutil meta' was not executed for all offset list (-o) entries because the number of -o entries exceeded the indicated limit. Entries beyond that limit were ignored.
- ACFS-03740: The Oracle ADVM compatibility attribute for the disk group is less than the required version (string) for 'acfsutil size -s' command.
-
Cause: An attempt to enable auto-shrink was rejected because the ADVM disk group compatibility level had not been upgraded to the indicated version, which is required for that command.
- ACFS-03741: Failed to set auto-shrink
-
Cause: The ACFS driver was unable to change auto-shrink state.
- ACFS-03751: Unable to modify the set of nodes where this ACFS file system is running.
-
Cause: An attempt to modify the set of nodes where this ACFS file system was running was rejected because that operation was not supported by the command 'acfsutil registry'.
- ACFS-03777: no connection to Oracle ASM
-
Cause: A requested operation that required services from Oracle Automatic Storage Management (ASM) failed because it could not connect to an ASM instance.
- ACFS-03778: unable to perform remote operation 'string' for file string
-
Cause: An attempt to issue the indicated remote command on the indicated file failed. The Oracle Kernel Services (OKS) persistent log provides more detailed failure information.
- ACFS-03780: 'acfsutil meta' metadata file had an unknown file format:\n string expected\n string found
-
Cause: An attempt to expand an ACFS metadata file was rejected because the metadata file had an unknown format, possibly because it was not created by the command 'acfsutil meta', or it was created by an incompatible version of that command.
- ACFS-03783: unable to determine the cluster type
-
Cause: An 'acfsutil' command failed to determine the type of cluster that contained the local server. The accompanying messages provide detailed failure information.
- ACFS-03784: Minimum scan size is numberMB.
-
Cause: An attempt to perform a limited file system scan was rejected because the scan size was smaller than the indicated minimum.
- ACFS-03802: unable to obtain lock statistics
-
Cause: An error occurred while fetching lock statistics. The accompanying messages provide detailed failure information.
- ACFS-03804: invalid sort column: 'string'
-
Cause: An attempt to get lock statistics was rejected because an invalid value was provided for the sort option.
- ACFS-03805: command failed due to an internal error
-
Cause: An attempt to get lock statistics failed due to an internal error.
- ACFS-03807: unknown sort column: 'number'
-
Cause: An internal sort function was called with an unknown sort column. This was an internal error.
- ACFS-03808: command cannot accept the 'string' and 'string' options simultaneously
-
Cause: An 'acfsutil lockstats' command was rejected because of an invalid option combination. 'acfsutil lockstats' could not take the specified options simultaneously.
- ACFS-03809: invalid value for option 't': 'string'
-
Cause: An 'acfsutil lockstats' command was rejected because a value that was not a positive integer was provided for the 't' option.
- ACFS-03813: cannot find the ACFS Checker utility: string
-
Cause: The 'acfsutil meta' back-end utility (the ACFS Checker) could not be found.
- ACFS-03814: stringe stringi stringo stringq options cannot be used with stringg
-
Cause: The 'acfsutil meta' command cannot use the 'e', 'i', 'o', nor 'q' options simultaneously with the 'g' option.
- ACFS-03815: Cannot determine if string was mounted in the cluster.
-
Cause: 'acfsutil meta' cannot determine if the specified device is mounted somewhere in the cluster. This message is accompanied by other messages providing details on the error.
- ACFS-03816: 'acfsutil meta stringg' failed because string was mounted in the cluster.
-
Cause: An attempt to execute the command 'acfsutil meta -g' failed because the specified device is mounted somewhere in the cluster.
- ACFS-03817: The 'acfsutil meta' command was rejected because the stringO, stringC and stringS options can only be used with the stringg option.
-
Cause: The 'O', 'C' and 'S' options can only be used with the 'acfsutil meta' 'g' option.
- ACFS-03818: The 'acfsutil meta' command was rejected because the stringC and stringS options can only be used with the stringO option.
-
Cause: The 'C' and 'S' options can only be used with the 'acfsutil meta' 'O' option.
- ACFS-03819: The online 'acfsutil meta stringg stringO' failed because string was not mounted.
-
Cause: The online 'acfsutil meta -g -O' command found that the specified device was unmounted.
- ACFS-03820: WARNING: Incomplete: string - Check the log file for errors.
-
Cause: 'acfsutil meta' failed while collecting the file system metadata and the specified metadata collection file may be incomplete. The metadata collection log file will have the failure reason.
- ACFS-03821: WARNING: ACFS Checker failed. Re-run 'acfsutil meta' without the stringg option.
-
Cause: ACFS Checker failed while collecting the file system metadata and the specified metadata collection file may be incomplete. The metadata collection log file will have the failure reason.
- ACFS-03822: stringe and stringi options cannot be used when collecting metadata
-
Cause: The 'acfsutil meta' command failed because invalid options were supplied. The 'e' and 'i' options cannot be used when collecting metadata.
- ACFS-03823: The stringstring file cannot be the stringstring file.
-
Cause: The 'acfsutil meta' command failed because the 'f' or 'a' option file was the same as the option 'e' file.
- ACFS-03824: Fshare operation could not complete.
-
Cause: An attempt to execute the 'acfsutil fshare create' command failed. The accompanying messages provide detailed failure information.
- ACFS-03825: Unable to perform file share operation on string
-
Cause: An attempt to execute the 'acfsutil fshare create' command failed. The accompanying messages provide detailed failure information.
- ACFS-03826: Cannot create file share string. It already exists.
-
Cause: An attempt to create a file share failed because a file share with the indicated name was found to already exist.
- ACFS-03827: Cannot create file share string. The file system is full.
-
Cause: An attempt to create a file share failed because the file system is out of space.
- ACFS-03828: File share string does not exist.
-
Cause: An attempt to execute the 'acfsutil fshare create' command failed because no file could be found with the indicated name.
- ACFS-03829: Cannot create file share string as replication V1 is active on this mount point.
-
Cause: Replication V1 was active on the mount point. ACFS Replication V1 and ACFS file shares cannot co-exist on the same mount point.
- ACFS-03830: Cannot create file share string as this operation is not allowed on a standby file system.
-
Cause: An attempt to execute the 'acfsutil fshare create' on a standby file system was attempted.
- ACFS-03831: Cannot create file share string in a read only snapshot.
-
Cause: An attempt to create a file share failed because the snapshot is read only.
- ACFS-03832: Cannot create file share string in a read only mountpoint.
-
Cause: An attempt to create an file share failed because the mountpoint is read only.
- ACFS-03833: Cannot create file share of string as file is compressed.
-
Cause: ACFS Compression and ACFS file shares cannot co-exist on the same file.
- ACFS-03834: Cannot create file share string as destination file is in different namespace.
-
Cause: An attempt to create a file share failed because destination is in a different snapshot or filesystem than the source."
- ACFS-03836: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil fshare' commands.
-
Cause: The 'acfsutil fshare command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-03837: There are too many fshares for the file string. Only number are allowed. Reduce the number of fshares before proceeding.
-
Cause: An attempt to create more than the maximum allowed number of file shares was rejected.
- ACFS-03839: Cannot create file share string as destination file is in different filesystem.
-
Cause: An attempt to create a file share failed because destination is in a different filesystem"
- ACFS-03840: name of file share cannot exceed number bytes
-
Cause: At attempt to create a file share was rejected because the specified name was too long.
- ACFS-03841: The specified string string is not a valid fshare create name.
-
Cause: The 'acfsutil fshare create' command failed because the indicated name was not a valid fshare create name. Possible reasons include: 1) The fshare create name exceeded the limit of 255 characters. 2) The fshare create name equaled "." or "..". 3) The fshare create name contained "/" (Unix or Linux). 4) The fshare create name contained "" or ":" (Windows). 5) The fshare create name contained an illegal character for NTFS file names (Windows).
- ACFS-04001: Failed to open path string. Verify that string exists.
-
Cause: Path could not be opened.
- ACFS-04002: unable to allocate a buffer
-
Cause: A request for process virtual memory by acfsdismount command failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-04003: volume string in use by a non-ACFS file system
-
Cause: The file system could not be dismounted because the specified volume was in use by another non-ACFS file system.
- ACFS-04004: error removing symbolic link for string
-
Cause: An ACFS file system could not be dismounted because an attempt to remove a symbolic link failed. The accompanying messages provide detailed failure information.
- ACFS-04005: error removing DOS definition for string
-
Cause: An ACFS file system could not be dismounted because an attempt to remove a DOS definition failed. The accompanying messages provide detailed failure information.
- ACFS-04006: unable to remove the reparse point on string
-
Cause: An ACFS file system could not be dismounted because an attempt to remove the associated reparse point failed. The accompanying messages provide detailed failure information.
- ACFS-04007: dismount failed due to open files on the volume
-
Cause: An ACFS file system could not be dismounted because an attempt to lock the associated volume failed. The accompanying messages provide detailed failure information.
- ACFS-04008: failed to unlock the volume
-
Cause: An ACFS file system could not be dismounted because an attempt to unlock the associated volume failed. The accompanying messages provide detailed failure information.
- ACFS-04009: unable to retrieve the volume name associated with string
-
Cause: An ACFS file system could not be dismounted because an attempt to retrieve the volume associated with the supplied mount point failed. The accompanying messages provide detailed failure information.
- ACFS-04010: conversion of reparse data Unicode string to ANSI string failed
-
Cause: An ACFS file system could not be dismounted because an attempt to convert a unicode string to an ANSI string failed. The accompanying messages provide detailed failure information.
- ACFS-04011: Failed to open volume string. Verify that string exists.
-
Cause: Volume could not be opened.
- ACFS-04013: acfsdismount /all operation did not complete. Unable to retrieve a mount point from the list of active ACFS file systems to dismount. It is possible that not all file systems were dismounted.
-
Cause: Failed to obtain the next file system to dismount.
- ACFS-04032: removing administrative network share for mount point string at share name 'string'
-
Cause: Informational
- ACFS-04033: administrative network share 'string' does not share mount point string as expected
-
Cause: Attempted to remove the administrative network share associated with the specified ACFS mount point, but the network share does not share the specified ACFS mount point as expected.
- ACFS-04034: administrative network share for mount point string does not exist at share name 'string'
-
Cause: Informational
- ACFS-04035: retrieving information for administrative network share 'string' failed
-
Cause: While removing the administrative network share associated with the specified ACFS mount point, failed to retrieve information on the administrative network share. This message is accompanied by other messages providing details on the error.
- ACFS-04036: removing administrative network share for mount point string at share name 'string' failed
-
Cause: Failed to remove the administrative network share associated with the specified ACFS mount point. This message is accompanied by other messages providing details on the error.
- ACFS-04037: could not remove administrative network share for mount point string at share name 'string'
-
Cause: Failed to remove the administrative network share associated with the specified ACFS mount point. This message is accompanied by other messages providing details on the error.
- ACFS-04038: Volume string is still mounted. Dismount will complete as soon as activity ceases on the file system.
-
Cause: At the conclusion of the file system dismount request, the file system was still mounted. This could be a result of open files on the mount point. The dismount will finish as soon as activity ceases on the file system.
- ACFS-04058: Ignoring unsupported ACFS command option: 'string'
-
Cause: An unsupported 'umount.acfs' command option was specified.
- ACFS-04150: unable to retrieve mount point information from the ACFS driver
-
Cause: During unmount processing, an attempt to retrieve mount point information from the ACFS driver failed.
- ACFS-04151: unmount of mount point string failed
-
Cause: The file system unmount failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-05001: must specify 'primary' or 'standby'
-
Cause: Command syntax requires 'primary' or 'standby' argument.
- ACFS-05002: must provide an Oracle Net alias to the primary replication site
-
Cause: The Oracle Net alias to connect to the primary replication site was not specified.
- ACFS-05003: must provide a primary mount point
-
Cause: The mount point on the replication primary site for the file system to be replicated was not provided.
- ACFS-05004: cannot allocate a list of tag names
-
Cause: A request for process virtual memory failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-05005: invalid tag name: string
-
Cause: User specified a tag name that has incorrect syntax.
- ACFS-05006: unable to initialize replication process data structures
-
Cause: Failed to determine path names for replication directories.
- ACFS-05007: cannot initialize interrupt signal handler
-
Cause: The system could not initialize the mechanism to handle interrupts.
- ACFS-05008: cannot lock file string to serialize ACFS replication commands
-
Cause: Failed to open and lock the specified file. This message accompanied by other message(s) providing details on the error.
- ACFS-05009: ACFS replication initialization is already in progress.
-
Cause: Initialization was in progress on the replication site.
- ACFS-05010: ACFS replication initialization is still in progress.
-
Cause: The command cannot be run until replication initialization completes.
- ACFS-05011: cannot open directory: string
-
Cause: Failed to open the specified directory. This message is accompanied by other message(s) providing details on the error.
- ACFS-05012: ACFS replication is already initialized.
-
Cause: ACFS replication has already been initialized on this system.
- ACFS-05013: ACFS replication cannot be initialized.
-
Cause: This message is accompanied by other message(s) providing details on the error.
- ACFS-05014: cannot verify replication configuration
-
Cause: This message is accompanied by other message(s) providing details on the error.
- ACFS-05015: cannot cleanup replication directories
-
Cause: The application failed to cleanup from a previous replication instantiation.
- ACFS-05016: cannot update replication configuration with new trace level
-
Cause: The application was unable to communicate with the ACFS driver.
- ACFS-05017: cannot create file: string
-
Cause: The application failed to create the specified file. This message is accompanied by other message(s) providing details on the error.
- ACFS-05018: cannot get primary ADVM volume information for string
-
Cause: The application failed to get the ADVM volume path for the mounted ACFS file system.
- ACFS-05019: cannot allocate space for the ADVM volume path
-
Cause: A request for process virtual memory failed. This message is accompanied by other message(s) providing details on the error.
- ACFS-05020: cannot start replication daemons
-
Cause: CRS has failed to start the replication daemons.
- ACFS-05021: cannot stop replication daemons
-
Cause: CRS has failed to stop the replication daemons.
- ACFS-05022: internal CRS error
-
Cause: The application failed to initialize communication with CRS.
- ACFS-05023: error checking for file: string
-
Cause: Informational
- ACFS-05024: The standby replication site is initialized. ACFS replication will begin.
-
Cause: Informational
- ACFS-05025: waiting for the standby replication site to initialize
-
Cause: Informational
- ACFS-05026: caught interrupt; ACFS replication initialization is shutting down.
-
Cause: Informational
- ACFS-05027: cannot remove file: string
-
Cause: File system was not accessible.
- ACFS-05028: cannot obtain current time for events log
-
Cause: The application failed to get the current time for logging.
- ACFS-05029: cannot write to the events log
-
Cause: The application failed to write to the specified file. This message is accompanied by other message(s) providing details on the error.
- ACFS-05030: cannot clean up configuration file
-
Cause: Initialization failed and the configuration file created during failed initialization could not be removed.
- ACFS-05031: standby file system is not empty
-
Cause: The file system was not empty.
- ACFS-05032: unable to determine user permissions
-
Cause: An error occurred attempting to acquire the user permissions. This message is accompanied by other message(s) providing details on the error.
- ACFS-05033: must provide a standby mount point
-
Cause: A mount point on the standby replication site was not provided.
- ACFS-05034: cannot obtain path for directory: string
-
Cause: The application failed to locate the specified directory.
- ACFS-05035: cannot open file for write: string
-
Cause: The application failed to open the specified file. This message is accompanied by other message(s) providing details on the error.
- ACFS-05036: cannot write to file: string
-
Cause: The application failed to write to the specified file. This message is accompanied by other message(s) providing details on the error.
- ACFS-05037: cannot move file string to directory string
-
Cause: The application failed move the specified file.
- ACFS-05038: cannot register Oracle Net service name
-
Cause: Unable to register the Oracle Net service name with the ASM instance.
- ACFS-05039: cannot unregister Oracle Net service name
-
Cause: Unable to unregister the Oracle Net service name from the ASM instance.
- ACFS-05040: cannot obtain Oracle Net service name from alias provided
-
Cause: Unable obtain the Oracle Net service name from the Oracle Net alias provided on the command line.
- ACFS-05041: Oracle Net service name is greater than number bytes
-
Cause: The Oracle Net service name specified for replication is greater than the maximum allowed.
- ACFS-05042: insufficient privileges to perform replication command. Administrator access is required.
-
Cause: The caller does not have sufficient privileges to perform the replication command.
- ACFS-05043: insufficient privileges to perform replication command. ASM administrator group access is required.
-
Cause: The caller does not have sufficient privileges to perform the replication command.
- ACFS-05044: cannot obtain node name
-
Cause: Unable to get local node name through CRS.
- ACFS-05045: invalid interval specified for replication statistics
-
Cause: The caller specified an invalid time interval for replication statistics.
- ACFS-05046: invalid date range specified for replication statistics
-
Cause: The caller specified an invalid date range for replication statistics.
- ACFS-05047: time specified is in the future
-
Cause: The caller specified a date in the future.
- ACFS-05048: start time specified is newer than the end time specified
-
Cause: The caller specified a date range where the start time was more recent the end time.
- ACFS-05049: validating the remote connection
-
Cause: Informational
- ACFS-05050: remote connection cannot be established
-
Cause: The user name, password, or Oracle Net alias used to connect to the remote site was not correct or the remote site was unreachable.
- ACFS-05051: remote connection has been established
-
Cause: Informational
- ACFS-05052: standby replication site requires reinitialization
-
Cause: Initialization was unable to complete on the primary replication site and left the standby replication site in an indeterminate state.
- ACFS-05053: replication's Oracle Net service name conflicts with the existing ASM service name
-
Cause: The service name for replication specified in the Oracle Net alias conflicts eith the Oracle Net service name that ASM uses.
- ACFS-05054: standby replication file system is mounted on more than one cluster node
-
Cause: The standby replication file system was mounted on more than one node in the cluster.
- ACFS-05055: invalid connection string for the primary replication site
-
Cause: The user name, password, or Oracle Net alias used to connect to the primary replication site was not correct or was unreachable.
- ACFS-05056: invalid connection string for the standby replication site
-
Cause: The user name, password, or Oracle Net alias used to connect to the standby replication site was not correct or was unreachable.
- ACFS-05058: command issued on the incorrect replication site
-
Cause: The command was issued on the incorrect replication site.
- ACFS-05059: ACFS replication not initialized
-
Cause: ACFS replication information cannot be retrieved as replication has not been initialized.
- ACFS-05060: waiting for ACFS replication to terminate
-
Cause: Informational
- ACFS-05061: ACFS replication command interrupted
-
Cause: Informational
- ACFS-05062: cannot query CRS resource
-
Cause: The application failed to communicate with CRS.
- ACFS-05063: cannot relocate CRS resource
-
Cause: The application failed to relocate CRS resource.
- ACFS-05064: the service name 'string' is not registered on the standby site
-
Cause: Possible causes include: 1.) Replication was not initialized on the standby site. 2.) Mismatched service names. If the -c option is not used, the service name specified in the alias for the standby file system did not match the service name specified for the primary file system in the alias on the standby site. 3.) The alias for the standby site referred to the wrong set of nodes.
- ACFS-05065: cannot transfer files to the standby file system 'string'
-
Cause: Possible causes include: 1.) The standby mount point did not exist or was not an ACFS file system. 2.) The standby file system was full.
- ACFS-05066: ACFS replication is already paused
-
Cause: ACFS replication was paused by a previous call.
- ACFS-05067: cannot rename file string to string in directory string
-
Cause: The application failed to rename the specified file.
- ACFS-05068: ACFS replication has not been paused
-
Cause: ACFS replication was not paused. Resume operation is not needed.
- ACFS-05069: ACFS replication update must specify at least one attribute
-
Cause: The command to update the replication configuration did not specify any attributes to update.
- ACFS-05070: command must be run on the primary replication site
-
Cause: 'acfsutil repl update' command was not run on the primary replication site.
- ACFS-05071: invalid username or password used to connect to the standby site
-
Cause: The username or password specified on the command line or in the wallet was incorrect.
- ACFS-05072: cannot open events file string
-
Cause: Failed to open events log file.
- ACFS-05073: cannot query events log file
-
Cause: Failed to query events log file.
- ACFS-05075: cannot terminate replication
-
Cause: Failed to terminate replication.
- ACFS-05076: unable to determine CRS user/group
-
Cause: The application failed to determine CRS user and/or group.
- ACFS-05077: could not complete replication synchronization
-
Cause: Failed to complete synchronization of primary and standby replication sites.
- ACFS-05078: failed to synchronize primary and standby replication sites
-
Cause: Failed to synchronize replication sites.
- ACFS-05079: waiting for replication update to complete
-
Cause: Informational
- ACFS-05083: Initialization of the primary file system could not complete because the standby is already configured for replication.
-
Cause: The standby file system was not expecting initialization data from this primary. Possible causes include: 1. Stale replication state detected on standby file system from a previous instantiation. 2. An incorrect replication standby site was supplied. 3. An incorrect replication standby file system was supplied.
- ACFS-05084: The replication standby file system has been newly initialized and is refusing files from the primary. The primary may need to be terminated and newly initialized.
-
Cause: The standby file system was not expecting any data from the primary except initialization data. A possible cause may be the standby file system was terminated and newly initialized, but the primary was not.
- ACFS-05085: cannot start replication because incompatible ACFS features already exist
-
Cause: An attempt to initialize replication was rejected because the file system was in a state incompatible with replication. Possible causes include: 1. The file system was not formatted with 512-byte metadata blocks, the file system was compressed, or the file system contains fshares. 2. The file system was frozen.
- ACFS-05086: listener is not running on the standby site
-
Cause: The listener was not started on the remote site or an incorrect node name was specified in the standby alias definition.
- ACFS-05087: The event log does not cover the time range specifed.
-
Cause: The events log did not cover any portion of the time range specified in the command.
- ACFS-05088: replicated file system size is below the minimum of stringG
-
Cause: An attempt was made to initialize replication on a file system that did not have sufficient space.
- ACFS-05089: replication statistics cannot be queried on the standby site
-
Cause: An attempt was made to query the replication statistics on the standby site.
- ACFS-05090: interval is greater than number years
-
Cause: The interval specified was greater than the maximum allowed.
- ACFS-05091: The mount path specified exceeds the maximum length allowed on this platform.
-
Cause: The specified mount path exceeded the maximum length on this platform.
- ACFS-05092: replicated file system free space is near the minimum threshold of numberGB per active node, continuing with initialization
-
Cause: Initialization of replication was issued on a file system that is near the minimum threshold of free space.
- ACFS-05093: could not retrieve active node count on file system: string, error: number
-
Cause: Could not get the number of nodes active on the specified file system.
- ACFS-05094: replicated file system free space is below the minimum of numberGB per active node, actual free space left: numberGB
-
Cause: An attempt was made to initialize replication on a file system that did not have sufficient space.
- ACFS-05159: Last sync time with primary: string
-
Cause: Informational
- ACFS-05170: Cannot initialize replication while the cluster is in rolling migration
-
Cause: An attempt to initialize replication was rejected because the cluster was in rolling migration. Replication initialization is not allowed during rolling migration.
- ACFS-05171: Cannot terminate replication while the cluster is in rolling migration
-
Cause: An attempt to terminate replication was rejected because the cluster was in rolling migration and the file system was mounted on more than one node.
- ACFS-05172: Replication cannot be terminated because background processes are not running.
-
Cause: Replication background processes were stopped and cannot finish processing replication data.
- ACFS-05200: Stopping ACFS replication daemons on string
-
Cause: Informational
- ACFS-05201: Starting ACFS replication daemons on string
-
Cause: Informational
- ACFS-05202: ACFS replication daemons started successfully on string
-
Cause: Informational
- ACFS-05203: ACFS replication daemons stopped successfully on string
-
Cause: Informational
- ACFS-05204: Attempting to restart replication daemons on string
-
Cause: Informational
- ACFS-05205: Failed to initialize replication because ACFS Security is in use on the standby file system 'string'.
-
Cause: ACFS replication initialization failed on the standby file system because ACFS Security was in use on the file system.
- ACFS-05206: Failed to initialize replication on ACFS Security enabled file system 'string' because ACFS Security is not initialized on the standby site.
-
Cause: Replication initialization failed on ACFS Security enabled primary file system because ACFS Security was not initialized on the standby site.
- ACFS-05207: A request to initialize replication failed because the primary replication file system is enabled for ACFS Security and standby site is not initialized for ACFS Security.
-
Cause: A request to initialize replication failed because the primary replication file system was enabled for ACFS Security and standby site was not initialized for ACFS Security.
- ACFS-05208: A request to initialize replication failed because the primary replication file system is enabled for ACFS Encryption and standby site has PKCS wallet.
-
Cause: Replication initialization failed because the use of PKCS wallet for an ACFS Replication standby site is not supported.
- ACFS-05209: A request to initialize replication failed because the primary replication file system is enabled for ACFS Encryption and an error occurred in accessing OCR at standby site.
-
Cause: Internal error.
- ACFS-05210: Failed to initialize replication because ACFS Encryption is in use on the standby file system 'string'.
-
Cause: ACFS replication initialization failed on the standby file system because ACFS Encryption was in use on the file system.
- ACFS-05211: Failed to initialize replication on ACFS Encryption enabled file system 'string' because PKCS wallet existed on standby site.
-
Cause: Replication initialization failed because the use of PKCS wallet for an ACFS Replication standby site is not supported.
- ACFS-05212: Failed to initialize replication on ACFS Encryption enabled file system 'string' because an error occurred in accessing the OCR at standby site.
-
Cause: Internal error.
- ACFS-05214: Failed to prepare ACFS Security on replication enabled file system 'string' because ACFS Security is not initialized on the standby site.
-
Cause: An attempt to prepare ACFS Security on replication enabled file system failed because ACFS Security was not initialized on the standby site.
- ACFS-05216: Failed to set ACFS encryption on a replication enabled file system 'string' because PKCS wallet is not supported as ACFS encryption key store on standby site.
-
Cause: An attempt to set ACFS encryption on replication enabled file system failed because the standby site was having a PKCS wallet as ACFS encryption key store.
- ACFS-05217: Failed to set ACFS Encryption on replication enabled file system 'string' because an error occurred accessing the OCR at standby site.
-
Cause: Internal error.
- ACFS-05218: Cannot proceed because another conflicting 'acfsutil' command is in progress.
-
Cause: The command could not proceed because one of the following 'acfsutil' commands was in progress in the cluster. a. 'acfsutil repl init' b. 'acfsutil sec prepare' c. 'acfsutil encr set' d. 'acfsutil audit enable'
- ACFS-05219: Cannot proceed because CRS stack is not up.
-
Cause: The command could not proceed because CRS stack was not up.
- ACFS-05220: Cannot proceed because ACFS replication initialization is in progress.
-
Cause: The command could not proceed because ACFS replication initialization was in progress.
- ACFS-05221: Failed to prepare ACFS Security on a replication enabled file system 'string' because ACFS audit is not initialized on the standby site.
-
Cause: An attempt to prepare ACFS Security on a replication enabled file system failed because ACFS Audit was not initialized on the standby site.
- ACFS-05222: Failed to initialize replication on ACFS Audit prepared filesystem string because ACFS Audit is not initialized on the standby site.
-
Cause: Replication initialization failed on an ACFS Audit prepared primary file system because ACFS Audit was not initialized on the standby site.
- ACFS-05223: Failed to prepare ACFS Audit on replication enabled file system 'string' because ACFS audit is not initialized on the standby site.
-
Cause: An attempt to prepare ACFS Audit on a replication enabled file system failed because ACFS Audit was not initialized on the standby site.
- ACFS-05224: Failed to prepare ACFS Audit on replication enabled file system 'string' because an error occurred accessing the OCR at standby site.
-
Cause: Internal error.
- ACFS-05226: Failed to set ACFS Encryption on a replication enabled file system 'string' because ACFS audit is not initialized on the standby site; moreover, PKCS wallet is not supported as ACFS Encryption key store on the standby site.
-
Cause: In ACFS Audit initialized cluster, an attempt to set ACFS Encryption on replication enabled filesystem failed because standby site is not ACFS audit initailized and PKCS wallet is not supported as ACFS Encryption key store on the standby site.
- ACFS-05227: Failed to set ACFS Security on a replication enabled file system 'string' because ACFS Security is not initialized on the standby site; moreover, ACFS Audit is not initialized on standby site.
-
Cause: In an ACFS Audit initialized cluster, an attempt to prepare ACFS Security on a replication enabled filesystem failed because the standby site was neither Audit initialized nor Security initialized.
- ACFS-05228: Failed to set ACFS Encryption on a replication enabled file system 'string' because ACFS audit is not initialized on the standby site.
-
Cause: An attempt to set ACFS Encryption on a replication enabled file system failed because ACFS Audit was not initialized on the standby site.
- ACFS-05229: Failed to prepare ACFS Security on replication enabled file system 'string' because an error occurred accessing the OCR at the standby site.
-
Cause: Internal error.
- ACFS-05230: Failed to get standby site's encryption state.
-
Cause: An attempt to get standby site's encryption status failed because standby site was unreachable.
- ACFS-05231: Failed to get standby site's security state.
-
Cause: An attempt to get standby site's security status failed because standby site was unreachable.
- ACFS-05232: Failed to get standby site's audit state.
-
Cause: An attempt to get standby site's audit status failed because standby site was unreachable.
- ACFS-05233: Cannot prepare a file system for ACFS Security while the cluster is in rolling migration.
-
Cause: An attempt to prepare a file system for ACFS Security was rejected because the cluster was in rolling migration. ACFS Security prepare operation is not allowed during rolling migration.
- ACFS-05234: Cannot set ACFS Encryption parameters while the cluster is in rolling migration.
-
Cause: An attempt to set ACFS Encryption parameters was rejected because the cluster was in rolling migration. ACFS Encryption set operation is not allowed during rolling migration.
- ACFS-05235: Cannot enable ACFS Audit while the cluster is in rolling migration.
-
Cause: An attempt to enable ACFS Audit was rejected because the cluster was in rolling migration. ACFS Audit enable operation is not allowed during rolling migration.
- ACFS-05236: Snapshot cannot serve as replication standby for primary with security enabled.
-
Cause: An attempt to initialize ACFS replication was rejected because a snapshot was specified as the replication standby site for a primary file system with ACFS security enabled.
- ACFS-05237: Snapshot cannot serve as replication standby for primary with encryption enabled.
-
Cause: An attempt to initialize ACFS replication was rejected because a snapshot was specified as the replication standby site for a primary file system with ACFS encryption enabled.
- ACFS-05238: Snapshot cannot serve as replication standby for primary with audit enabled.
-
Cause: An attempt to initialize ACFS replication was rejected because a snapshot was specified as the replication standby site for a primary file system with ACFS audit enabled.
- ACFS-05239: Failed to prepare ACFS Security on replication enabled file system 'string'.
-
Cause: An attempt to prepare security on replication enabled file system because ACFS security is not supported on primary file systems when the standby site is a snapshot.
- ACFS-05240: Failed to set ACFS Encryption on replication enabled file system 'string'.
-
Cause: An attempt to set encryption on the indicated replication enabled file system because ACFS encryption was not supported where the standby site is a snapshot.
- ACFS-05241: Failed to enable ACFS Audit on replication enabled file system 'string'.
-
Cause: An attempt to enable ACFS audit on replication enabled file system because ACFS Audit was not supported where the standby site is a snapshot.
- ACFS-05242: Snapshot creation failed for file system with ACFS Security enabled.
-
Cause: An attempt to create a snapshot using the command 'snap dup create' was rejected because the file system had ACFS Security enabled. Snapshots were not supported for file systems with security enabled.
- ACFS-05243: Snapshot creation failed for file system with ACFS Encryption enabled.
-
Cause: An attempt to create a snapshot using the command 'snap dup create' was rejected because the file system had ACFS Encryption enabled. Snapshots were not supported for file systems with encryption enabled.
- ACFS-05354: Clock difference detected between primary and standby replication sites.
-
Cause: A difference in the system clocks has been detected between the primary and standby replication sites.
- ACFS-05356: The Oracle Local Registry, OLR, cannot be accessed to query the software version.
-
Cause: The OLR is not accessible or is not configured correctly.
- ACFS-05500: ACFS replication error. Contact Oracle Support Services. string
-
Cause: An ACFS replication operation failed.
- ACFS-05501: ACFS replication error. Customer action required. string
-
Cause: This message is accompanied by other message(s) providing details on the error.
- ACFS-05502: ACFS replication error. System administration needed. string
-
Cause: This message is accompanied by other message(s) providing details on the error.
- ACFS-05503: ACFS replication string daemon shutting down. string
-
Cause: This message is accompanied by other message(s) providing details on the error.
- ACFS-05505: The standby replication file system is full.
-
Cause: The standby replication file system is out of space.
- ACFS-05506: The primary replication file system is full.
-
Cause: The primary replication file system is out of space.
- ACFS-05507: The standby replication site failed number times to transport replication files from host string.
-
Cause: The replication transport mechanism failed to transport files from the standby replication site.
- ACFS-05508: The primary replication site failed number times to transport replication files from host string.
-
Cause: The replication transport daemon failed to transfer files from the primary replication site.
- ACFS-05511: The standby replication site host, string, is experiencing number I/O errors.
-
Cause: I/O on the standby replication site failed.
- ACFS-05512: The primary replication site host, string, has experienced number I/O errors.
-
Cause: I/O on the primary replication site failed.
- ACFS-05513: replication monitor daemon has detected a problem
-
Cause: An error log file was received.
- ACFS-05514: The replication monitor daemon has not received receipt or error files within the set threshold.
-
Cause: The time allowed for receiving receipt or error files has surpassed.
- ACFS-05515: The replication monitor received an invalid receipt file and will not process it.
-
Cause: The receipt file that the replication monitor process received is not valid.
- ACFS-05516: The apply daemon failed to regenerate an apply file.
-
Cause: The apply daemon has requested more than the allowed number of regnerations on an apply file.
- ACFS-05517: ACFS replication on string: string
-
Cause: Informational
- ACFS-05518: string is not an ACFS mount point
-
Cause: The command required an ACFS mount point for execution.
- ACFS-05519: must provide an Oracle Net alias to the standby replication site
-
Cause: The Oracle Net alias, which is used to connect to the standby replication site, was not specified.
- ACFS-05520: cannot update replication configuration
-
Cause: The application was unable to communicate with the ACFS driver.
- ACFS-05521: cannot initialize replication configuration
-
Cause: The application was unable to communicate with the ACFS driver.
- ACFS-05522: Cannot terminate replication. Pending operations are unable to complete because the replication standby file system is full.
-
Cause: The standby replication file system is full and replication could not complete applying data before terminating.
- ACFS-05523: The replication relationship for mount point 'string' must be restarted or upgraded.
-
Cause: ACFS replication activity determined that the indicated mount point was using outdated replication infrastructure. Release 12.2 introduced new ACFS replication infrastructure, and migration to the new infrastructure was required.
- ACFS-05524: The replication relationship just initiated must be restarted or upgraded.
-
Cause: A replication relationship was initiated specifically using an outdated replication infrastructure. Release 12.2 introduced new ACFS replication infrastructure, and migration to the new infrastructure was required.
- ACFS-05605: ACFS replication daemon string is exiting due to replication termination. string
-
Cause: Informational
- ACFS-05700: All the tag names specified during the "acfsutil repl init" operation must exactly match those specified on the command line.
-
Cause: Either at least one tag name was not specified during replication initialization or a specified tag name does not match that used during the "acfsutil repl init" operation.
- ACFS-05701: Comparing first tree (<<<) to second tree (>>>):
-
Cause: Informational
- ACFS-05702: Testing for extra files in the second tree.\nSecond tree (<<<) to first tree (>>>):
-
Cause: Informational
- ACFS-05703: Results for file comparison of first tree to second tree:
-
Cause: Informational
- ACFS-05704: Files successfully compared = number
-
Cause: Informational
- ACFS-05705: Files which failed comparison = number
-
Cause: Informational
- ACFS-05706: Results for extra files in the second tree:
-
Cause: Informational
- ACFS-05707: Total files checked = number
-
Cause: Informational
- ACFS-05708: Extra files found = number
-
Cause: Informational
- ACFS-05709: A status check on a file failed. Skipping file: string
-
Cause: Either the first tree is actively being modified or an internal error occurred.
- ACFS-05710: ACFS tags do not support character devices. Skipping file: string
-
Cause: Informational
- ACFS-05711: ACFS tags do not support block devices. Skipping file: string
-
Cause: Informational
- ACFS-05712: ACFS tags do not support FIFOs. Skipping file: string
-
Cause: Informational
- ACFS-05713: ACFS tags do not support sockets. Skipping file: string
-
Cause: Informational
- ACFS-05714: <<< string\n>>> File missing!
-
Cause: The specified file was not found in the second tree.
- ACFS-05715: Found: string
-
Cause: The specified file is an extra file in the second tree.
- ACFS-05716: <<< Tag names exist on file string\n>>> No tag names exist on file string
-
Cause: The file in the first tree has tag names but the file in the second tree has no tag names.
- ACFS-05717: <<< Extended attribute mismatch for string\n>>> Extended attribute mismatch for string
-
Cause: Informational
- ACFS-05718: An unexpected result occurred while comparing the first tree to the second tree. Continuing. Affected files: string string
-
Cause: An unexpected result occurred while comparing the first tree to the second tree.
- ACFS-05719: An unexpected result occurred while comparing the second tree to the first tree. Continuing. Affected files: string string
-
Cause: An unexpected result occurred while comparing the second tree to the first tree.
- ACFS-05720: File type was not recognized. Continuing. Affected files "string" and "string"
-
Cause: An unrecognized file type was encountered which will be ignored.
- ACFS-05721: Could not open the file specified for a checksum operation: string
-
Cause: Either the first tree was modified or an internal error occurred.
- ACFS-05722: A file read failed during a checksum operation: string
-
Cause: Either the first tree was modified or an internal error occurred.
- ACFS-05723: Unable to obtain security attributes on file "string"
-
Cause: Check the access rights on the indicated file.
- ACFS-05724: Unable to convert a security descriptor to a string on file "string"
-
Cause: The Windows security identifier (SID) may not be available on this system.
- ACFS-05725: The replication user 'string' specified using the '-p' option does not match the replication user 'string' specified using the '-s' option.
-
Cause: An attempt to initialize replication on the primary was rejected because the replication user specified using the '-p' option does not match the replication user specified using the '-s' option.
- ACFS-05728: Failed to retrieve file system status information from a system call for mount point "string."
-
Cause: A system call for the status of the file system failed.
- ACFS-05730: Mount point "string" does not support Oracle ACFS tagging.
-
Cause: The "-a" option was passed on the command line to compare ACFS tags. A file system being checked did not support ACFS tagging.
- ACFS-05731: Mount point "string" does not support extended attributes, therefore, the ACFS tag name portion of the comparisons will not be performed.
-
Cause: Informational.
- ACFS-05732: The second tree does not exist: "string" .
-
Cause: Failed to access the specified second tree.
- ACFS-05733: Successfully compared: string string
-
Cause: Informational.
- ACFS-05734: Successfully verified existence: string string
-
Cause: Informational.
- ACFS-05735: string contents not compared for symlink string
-
Cause: Informational.
- ACFS-05736: string symlink contents comparison failed: symlink=string, contents=string
-
Cause: Informational.
- ACFS-05737: string file attribute comparison failed: permissions=string, links=number, uid=number, gid=number, bytes=number, file: string
-
Cause: Informational.
- ACFS-05738: string file size or file contents comparison failed, file: string
-
Cause: Informational.
- ACFS-05739: string security descriptor comparison failed, file: string
-
Cause: Informational.
- ACFS-05740: string file type comparison failed, file: string
-
Cause: Informational.
- ACFS-05741: string file type comparison failed, directory: string
-
Cause: Informational.
- ACFS-05742: string file type comparison failed, soft link: string
-
Cause: Informational.
- ACFS-05743: string file type comparison failed, socket: string
-
Cause: Informational.
- ACFS-05744: string file type comparison failed, character device: string
-
Cause: Informational.
- ACFS-05745: string file type comparison failed, block device: string
-
Cause: Informational.
- ACFS-05746: string file type comparison failed, FIFO: string
-
Cause: Informational.
- ACFS-05747: Directory 'string' is a nested ACFS reparse point and was not included in the file system comparison.
-
Cause: Informational.
- ACFS-05748: The 'strings' option requires either the 'stringa' option or 'stringt' option.
-
Cause: An incorrect combination of options was specified.
- ACFS-05749: The specified trees are the same and will not be compared.
-
Cause: The provided first and second trees resolved to the same location.
- ACFS-05801: The primary replication file system string is at least number%% full.
-
Cause: Free space in the primary replication file system fell below a monitored threshold.
- ACFS-05802: The primary replication file system string has numberGB or less space available per active node.
-
Cause: The primary replication file system was found to be running low on space.
- ACFS-05803: The primary replication file system string has 2GB or less space available per active node. Replication is being terminated.
-
Cause: The primary replication file system was found to be too low on space in order to run efficiently.
- ACFS-05804: The standby replication file system string is out of sync with the primary by at least number minutes.
-
Cause: The time period to process changes on the standby file system was exceeded.
- ACFS-05805: The standby replication file system string is out of sync with the primary by at least 60 minutes.
-
Cause: The standby replication file system finished applying changes from the primary that were made more than 60 minutes ago. The standby is at least 60 minutes out of sync with the primary.
- ACFS-05806: The primary replication file system string has reached an appropriate free space level.
-
Cause: A previously-reported free space shortage in the primary replication file system was relieved.
- ACFS-05807: The standby file system string is less than 15 minutes out of sync now.
-
Cause: A previously-reported out of sync time difference between the standby replication file system and the primary reached an appropriate out of sync time for replication to run efficiently.
- ACFS-05808: The primary replication file system string had an unrecoverable error and replication has been terminated for that file system.
-
Cause: The primary file system encountered an unrecoverable error in the kernel that has caused replication for this file system to be terminated. The cause will be in the Oracle Kernel Services (OKS) persistent log.
- ACFS-05809: invalid query of replication apply events on the standby site
-
Cause: An attempt was made to query the replication apply events on the standby site which failed because the information is available only on the primary site.
- ACFS-05810: invalid query of replication transport events on the standby site
-
Cause: An attempt was made to query the replication transport events on the standby site which failed because the information is available only on the primary site.
- ACFS-05811: ACFS replication initialization failed in Oracle Restart environment.
-
Cause: Initialization failed because the system was configured with Oracle Restart. ACFS replication is not supported for Oracle Restart configurations.
- ACFS-05887: cannot cleanup snapshot directories
-
Cause: The 'acfsutil repl terminate' command failed to cleanup from a previous replication instantiation.
- ACFS-05888: ACFS replication requires reinitialization of mount point string.
-
Cause: This file system has already been initialized with a different version of ACFS replication.
- ACFS-05889: a username and VIP name or username and hostname to the standby replication site was not provided
-
Cause: The username and VIP name or username and hostname used to connect to the standby replication site were not specified.
- ACFS-05890: a username for the standby replication site was not provided
-
Cause: The username on the standby replication site with which the primary replication site will connect and apply changes was not specified.
- ACFS-05891: username string used to connect to the standby site was rejected
-
Cause: The username specified on the command line was not found in the password database on the standby site.
- ACFS-05892: Cannot terminate replication. Pending operations are unable to complete because the replication primary file system is full.
-
Cause: The primary replication file system was full and replication could not complete sending data before terminating.
- ACFS-05893: cannot update the standby replication site
-
Cause: An attempt to update the standby replication site failed because an apply operation was in progress.
- ACFS-05894: invalid zero or negative integer replication interval
-
Cause: The value specified with the 'i' option was not an integer greater than zero.
- ACFS-05895: missing time unit on interval ('stringi') option
-
Cause: A unit of time was not specified with the interval that was provided with the 'i' option.
- ACFS-05896: invalid time unit in replication interval
-
Cause: An unrecognized unit was used following the interval length given with the 'i' option.
- ACFS-05897: missing interval ('stringi') option
-
Cause: The 'acfsutil repl init primary' command was incomplete because a replication interval was not specified.
- ACFS-05901: The specified tag name list exceeds the maximum of number characters.
-
Cause: The specified tag name list was too long.
- ACFS-05902: Snapshot string is read-only and cannot be modified.
-
Cause: A request to write to a snapshot was rejected because the snapshot was configured as read-only.
- ACFS-05903: unable to cleanup old snapshots
-
Cause: Informational.
- ACFS-05904: The base and target operating systems are not compatible.
-
Cause: An attempt to apply changes from a base file system to a target file system was rejected because one system was Unix or Linux and the other system was Windows.
- ACFS-05905: Target file system or snapshot has been altered since the last 'snap duplicate apply'.
-
Cause: An attempt to apply changes from a base file system or snapshot to a target file system or snapshot was rejected because the target had previously been modified and was no longer in sync with the base file system or snapshot.
- ACFS-05906: The system containing the base or primary file system disconnected prematurely.
-
Cause: An attempt to apply changes from the base or primary file system to the target or standby file system could not be completed because connectivity to the system containing the base or primary file system was lost.
- ACFS-05907: The ACFS file system mounted at path string is already running the latest version of replication.
-
Cause: A request to prepare an ACFS file system for replication upgrade was rejected because the file system is already running the latest version of replication.
- ACFS-05908: The replication upgrade control file string cannot be opened.
-
Cause: An attempt to open the replication upgrade control file failed.
- ACFS-05909: Snapshot string is not read only.
-
Cause: An attempt to use the 'snap duplicate create' command failed because the snapshot was writable.
- ACFS-05910: The snapshot specified as the old snapshot by the stringi option is not older than the snapshot specified as the new snapshot.
-
Cause: An attempt to create a snap duplicate failed because the snapshot specified as the old snapshot by the 'i' option is not older than the snapshot specified as the new snapshot.
- ACFS-05911: Target file system or snapshot has been altered since the start of the current 'snap duplicate apply'.
-
Cause: An attempt to apply changes from a base file system or snapshot to a target file system or snapshot was rejected because the target was modified while the apply attempt was in progress, and was no longer in sync with the base file system or snapshot.
- ACFS-05912: unable to perform 'snap duplicate' operation because ACFS replication is initialized on the file system
-
Cause: An attempt to use the 'acfsutil snap duplicate' command was rejected because ACFS replication was initialized on the file system.
- ACFS-05913: unable to contact the standby node string
-
Cause: An attempt to use the ping utility to contact a standby node failed.
- ACFS-05914: user string on node string unable to log in via 'ssh' to the standby node string as user string
-
Cause: An attempt by 'acfsutil repl init primary' or 'acfsutil repl update' to use the ssh utility to log in to a standby node failed.
- ACFS-05915: invalid use of '-t ALL' option
-
Cause: An attempt to execute the 'acfsutil repl compare' command was rejected because the '-t ALL' option was specified on the command line, but no tag names had been specified when the primary was initialized.
- ACFS-05916: path string not found
-
Cause: The ssh utility was not found at the indicated path.
- ACFS-05917: user 'root' on node string unable to continue logging in via 'ssh' to the standby node string as user 'string'
-
Cause: A periodic attempt by ACFS replication to use the ssh utility to continue logging in to a standby node failed.
- ACFS-05918: Replication initialization on primary site cannot confirm replication initialized on standby mount point 'string'.
-
Cause: The 'acfsutil repl init primary' command failed on the primary replication site because it could not confirm that replication has been initialized on the standby replication site.
- ACFS-05919: Replication failed because it was unable to create a backup snapshot for mount point 'string' on standby node 'string'.
-
Cause: The 'acfsutil snap dup apply' operation, as used by ACFS replication, was unable to create a backup snapshot at the end of an apply operation on the standby node named. As a result, replication cannot proceed.
- ACFS-05920: ssh cipher option "string" is invalid for replication
-
Cause: An attempt to configure replication on the primary file system was rejected because the indicated value was specified for the 'sshCipher' option. Replication does not support unencrypted ssh connections.
- ACFS-05921: One or more files under mount point 'string' was not transferred because its path name exceeded number characters. The first such file was in directory 'string' and had name 'string'.
-
Cause: The command 'acfsutil snap duplicate create' did not complete correctly because one or more files located under the indicated mount point had an absolute path name longer than the indicated limit. Any files with path names exceeding the limit were not processed by 'acfsutil'. The directory and basename of the first such file found are shown in the message, but there may be many others.
- ACFS-05922: One or more files under primary mount point 'string' was not replicated because its path name exceeded number characters. The first such file was in directory 'string' and had name 'string'.
-
Cause: ACFS replication did not replicate the primary correctly because one or more files located under the indicated mount point had an absolute path name longer than the indicated limit. Any files with path names exceeding the limit were not replicated. The directory and basename of the first such file found are shown in the message, but there may be many others.
- ACFS-05923: unable to apply the incremental snapshot duplication stream because no initial snapshot duplication stream has been applied
-
Cause: An attempt to apply an incremental snapshot duplication stream failed because no preceding initial snapshot duplication stream has been applied to the snapshot duplication target.
- ACFS-05924: unable to apply the incremental snapshot duplication stream because its starting snapshot does not match the final snapshot used to create the most recently applied snapshot duplication stream
-
Cause: The incremental snapshot duplication stream could not be applied because its starting snapshot did not match the final snapshot of the last stream applied.
- ACFS-05925: unable to re-apply the initial snapshot duplication stream because its starting snapshot does not match the snapshot used to create the partially applied duplication stream
-
Cause: An attempt to apply an initial snapshot duplication stream was interrupted. An attempt was then made to re-apply the initial snapshot duplication stream. The re-apply failed because its starting snapshot did not match the snapshot of the last, partially applied snapshot duplication stream.
- ACFS-05926: The snapshot duplication stream cannot be applied because a previous duplication stream was interrupted.
-
Cause: Snapshot duplication failed because a previously interrupted snapshot duplication stream was detected.
- ACFS-05927: operation not allowed when replication is paused
-
Cause: A request to perform a replication command was rejected because the primary replication site was paused.
- ACFS-05928: The ADVM compatibility attribute for the diskgroup is below the required version (string) for the 'acfsutil snap duplicate' commands.
-
Cause: The command 'acfsutil snap duplicate' was rejected because the ADVM disk group compatibility attribute had not been upgraded to the indicated version, which is required for that command.
- ACFS-05929: Replication could not proceed because it was unable to delete a directory in mount point 'string' on standby node 'string'.
-
Cause: The 'acfsutil snap dup apply' operation, as used by ACFS replication, could not proceed because it was unable to delete a directory in the indicated mount point on the standby replication site shown.
- ACFS-05931: The standby replication ACFS file system mounted at path string at site string is not running a compatible version of replication.
-
Cause: A request to upgrade a primary replication ACFS file system was rejected because the standby file system is not running a compatible version of replication.
- ACFS-05932: cannot upgrade the existing ACFS replication environment
-
Cause: A request to upgrade the existing ACFS replication environment to snapshot-based replication was rejected because the existing tag name list exceeded the limit of 4096 characters imposed by snapshot-based replication.
- ACFS-05933: invalid, out-of-date option given for 'acfsutil repl init'
-
Cause: An attempt to invoke a 'acfsutil repl init' command was rejected because it specified an option specific to an earlier version of ACFS replication.
- ACFS-05934: ACFS replication could not start an apply operation for mount point 'string' due to an existing apply operation.
-
Cause: This message may indicate a problem with networking or storage access that is preventing the existing apply operation from making progress. Alternatively, this message may indicate an internal error.
- ACFS-05935: The ACFS replication primary is mounted on more than one node.
-
Cause: A request to prepare ACFS replication for upgrade was rejected because the file system was mounted on more than one node.
- ACFS-05936: The new snapshot and the old snapshot do not have the same parent.
-
Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the old snapshot by the -i option did not have the same parent as the snapshot specified as the new snapshot.
- ACFS-05937: The new snapshot is not a child of the parent snapshot.
-
Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the new snapshot was not a child of the parent snap specified by the -p option.
- ACFS-05938: The new snapshot is not a child of the mount point.
-
Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the new snapshot was not a child of the specified mount point.
- ACFS-05939: The parent snapshot must be writable.
-
Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the parent snapshot by the -p option was not writable.
- ACFS-05940: The ACFS file system mounted at path string is not prepared for replication upgrade.
-
Cause: A request to undo replication upgrade preparation on an ACFS file system was rejected because the file system had not been prepared for replication upgrade.
- ACFS-05941: The ACFS file system mounted at path string may not be unprepared for replication upgrade.
-
Cause: A request to undo replication upgrade preparation on an Oracle ACFS file system was rejected because its standby file system had already been upgraded.
- ACFS-05942: unable to apply updates to standby mount point 'string' due to user mismatch
-
Cause: An apply update operation on the indicated mount point was rejected because the replication user for the primary mount point and the indicated standby mount point did not match. This could occur if the command 'acfsutil repl update' had been used to change the replication user for one mount point and not the other.
- ACFS-05943: The replication user 'string' may lack needed privileges -- confirm the user's group memberships.
-
Cause: The 'acfsutil repl init standby' command completed correctly and registered the indicated user as specified by the -u option. However additional validation by the command determined that the indicated user was not a member of one or more groups presumed necessary for subsequent correct functioning of replication.
- ACFS-05944: The old and new snapshots are not properly related.
-
Cause: An attempt to create a snap duplicate stream failed because the specified new snapshot was not properly related to the old snapshot specified with -i. The new snapshot must either be a child of the old snapshot or be a child of the same parent as the old snapshot.
- ACFS-05945: Clusterware at site string must be upgraded to support the standby replication ACFS file system mounted at path string.
-
Cause: Following an upgrade of the Oracle Clusterware on the cluster where a primary replication ACFS file system was located, an attempt to do an automatic update of the standby failed, because the cluster where the standby replication ACFS file system was located was not running the same version of Clusterware.
- ACFS-05946: The replication subcommand (string) is not supported by the version of replication configured on the file system or snapshot.
-
Cause: An attempt to execute the indicated replication sub-command was rejected because it was not supported by the configured replication version.
- ACFS-05947: Snapshot string must be writable.
-
Cause: An attempt to initialize replication on a snapshot failed because the snapshot specified was not writable.
- ACFS-05948: The named standby is already in use by a different primary.
-
Cause: An attempt to initialize replication failed because the standby specified was already paired with a different primary.
- ACFS-05949: The standby replication ACFS file system mounted at path string at site string is not running a compatible version of replication.
-
Cause: A request to initiate replication of an ACFS file system was rejected because the indicated standby file system was running an incompatible version of replication.
- ACFS-05950: cannot reverse replication during a rolling upgrade
-
Cause: An attempt to reverse the replication role at a site was rejected because the cluster was in a rolling upgrade. Replication site reversal is not allowed during a rolling upgrade.
- ACFS-05951: snapshot creation is blocked while ACFS replication is updating the standby
-
Cause: An attempt to create a snapshot could not complete immediately because the replication standby was currently being updated by ACFS replication.
- ACFS-05952: A replication standby site cannot be reversed before the primary site is reversed.
-
Cause: An attempt to reverse a replication standby site was rejected because the corresponding replication primary site had not been reversed before the attempted standby reversal.
- ACFS-05953: Replication on the remote site cannot be terminated from the local site.
-
Cause: An attempt to terminate replication on the remote site from the local site failed.
- ACFS-05954: Replication on the remote site cannot be terminated from the local site. Proceeding with local termination.
-
Cause: An attempt to terminate replication on the remote site from the local site failed.
- ACFS-05955: The replication user 'string' specified using the '-s' option does not match the replication user configured on the standby.
-
Cause: An attempt to initialize replication on the primary was rejected because the replication user specified using the '-s' option does not match the replication user specified with the 'acfsutil repl init standby' command using the '-u' option.
- ACFS-05956: Operation not allowed during a rolling upgrade.
-
Cause: An attempt to perform an operation was rejected because the cluster was in a rolling upgrade. Some operations are not allowed during a rolling upgrade.
- ACFS-05957: Unable to initiate a transfer after failover.
-
Cause: The replication daemon detected that the standby was failed over and is no longer participating in this replication relationship as a standby. As such, we can no longer replicate to it so the daemon will terminate.
- ACFS-05958: Invalid standby configuration.
-
Cause: The replication daemon detected that the standby is no longer participating in this replication relationship as a standby. As such, it can no longer be replicated to.
- ACFS-05959: Operation not allowed during role reversal.
-
Cause: An attempt to perform an operation was rejected because a role reversal is in progress for this replication relationship.
- ACFS-05960: Operation not allowed during upgrade.
-
Cause: An attempt to perform an operation was rejected because an upgrade is in progress for this replication relationship.
- ACFS-05961: The new snapshot and the old snapshot have the same names.
-
Cause: An attempt to create a snap duplicate stream failed because the snapshot specified as the old snapshot by the -i option has the same name as the new snapshot.
- ACFS-05962: Multiple connections are not allowed between snapshot sites.
-
Cause: An attempt to configure replication failed because multiple connections were specified but the primary or standby site is a snapshot. Replication does not support multiple connections between snapshot sites.
- ACFS-07016: metadata read failed at disk offset: string size: number bytes
-
Cause: An attempt to read metadata at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07017: metadata read failed at disk offset: string\n bytes requested: number bytes returned: number
-
Cause: A metadata read at the indicated offset was incomplete. The amount of data returned did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07018: metadata write failed at disk offset: string size: number bytes
-
Cause: An attempt to write metadata at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07019: metadata write failed at disk offset: string\n bytes requested: number bytes written: number bytes
-
Cause: A metadata write at the indicated offset was incomplete. The amount of data written did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07021: The File_Entry_Table is corrupt and many of the files in the file system may \nnot be recoverable. It is strongly recommended that the file system be restored \nfrom a backup copy.
-
Cause: The ACFS Checker/Fixer found an inconsistency with the File_Entry_Table metadata. The File_Entry_Table is a critical system structure that is necessary for a functioning file system.
- ACFS-07022: I/O request for (disk offset + size): string exceeds primary volume size: string\nfor structure:\nstring
-
Cause: An I/O request was made for data that exceeded the size of the primary volume.
- ACFS-07023: read failed for metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor structure:\nstring
-
Cause: An attempt to read a metadata structure from disk failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07024: File_Entry_Table entry: string exceeds the maximum value for this file system: string
-
Cause: An entry was referenced that exceeded the File_Entry_Table limit.
- ACFS-07025: File_Entry_Table entry: string already processed for structure:\nstring
-
Cause: File_Entry_Table entries must be unique within a file system, but there were multiple references for this specific entry.
- ACFS-07026: file extent exceeds file system size: string\nextent: _FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring
-
Cause: The extent values of the indicated file referenced data beyond the size of the file system. There are two possible causes: 1. The extent _Length and/or _PhysicalDiskOffset property were incorrect. 2. The file system size value was incorrect.
- ACFS-07027: metadata structure at disk offset: string contains incorrect or invalid type\n found: string, but expected to find: string or string\nfor structure:\nstring
-
Cause: The type property of the indicated metadata structure was not valid. The type must be a DATA extent or a HEADER extent.
- ACFS-07028: DATA extent structure has incorrect _granularity value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _granularity property of the indicated DATA extent structure was invalid. Its value must be -1.
- ACFS-07029: HEADER extent structure has incorrect _granularity value\n found: number, but expected to find: >= 0\nfor structure:\nstring
-
Cause: The _granularity property of the indicated HEADER extent structure was invalid. Its value must be greater than or equal to zero.
- ACFS-07030: file has invalid _FE_OsdSecurity value\nfor file:\nstring
-
Cause: The _FE_OsdSecurity property of the indicated file was invalid.
- ACFS-07031: extent structure has incorrect _ExtentOffset value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _ExtentOffset property of the indicated extent structure did not match its disk offset.
- ACFS-07032: extent structure has incorrect _UpHeaderNodePtr value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _UpHeaderNodePtr property of the indicated extent structure was incorrect. There are two possible causes: 1. The _UpHeaderNodePtr property did not match its parent. 2. The parent identifier property was incorrect.
- ACFS-07033: extent structure has incorrect _granularity value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _granularity property of the indicated extent structure did not match its calculated depth.
- ACFS-07034: extent structure has incorrect _NextFreeExtent value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _NextFreeExtent property of the indicated extent structure was incorrect.
- ACFS-07035: extent[number] appears to be uninitialized\nfor structure:\nstring
-
Cause: An extent of the indicated extent structure appeared to be in use, but all of its values were zero.
- ACFS-07036: extent[number] has invalid _Length value\n found: 0, but expected to find: > 0\nfor structure:\nstring
-
Cause: The _Length property of an extent of the indicated extent structure had a value of zero. _Length values must be greater than zero.
- ACFS-07037: extent[number] has incorrect _SnapIncarnationNumber value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _SnapIncarnationNumber property of the indicated extent structure exceeded the maximum value for the file system.
- ACFS-07038: extent[number] has a non-contiguous _FileOffset value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _FileOffset property of an extent of the indicated extent structure was not contiguous with the _FileOffset of the previous extent.
- ACFS-07039: extent[number] is not in use but it contains non-zero values:\n _FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\n _SnapIncarnationNumber: number\nfor structure:\nstring
-
Cause: An extent of the indicated extent structure was not in use, but it contained non-zero values. There are two possible causes: 1. The extent values were not reset to zero when the extent was freed. 2. The _NextFreeExtent property of the extent structure was incorrect.
- ACFS-07040: calculated extent structure allocation size (sum of data sizes) does not match expected value\n calculated: string, but expected to find:string\nfor structure:\nstring
-
Cause: The sum of all valid extents within the indicated extent structure did not match the value of the corresponding extent in the parent extent structure.
- ACFS-07041: DATA extent list not found\nfor file:\nstring
-
Cause: The list of DATA extent structures of the indicated file did not include the initial DATA extent structure. There are two possible causes: 1. The _LastExtentPointer property of the file was incorrect. 2. The structure identified by the _LastExtentPointer value was not a DATA extent structure.
- ACFS-07042: DATA extent node list missing entry for extent structure:\nstring
-
Cause: The list of DATA extent structures of the indicated file was incomplete. One or more DATA extent structures was missing. There are three possible causes: 1. The _LastExtentPointer property of the file was incorrect. 2. The structure identified by the _LastExtentPointer value was not a valid DATA extent structure. 3. The _NextDataExtent property of one or more DATA extent structures was incorrect.
- ACFS-07043: metadata structure has invalid or incorrect type:\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The type property of the indicated metadata structure did not match the type expected for this structure.
- ACFS-07044: DATA extent list has more nodes than expected\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The list of DATA extent structures of the indicated file contained more nodes than expected. The _NextDataExtent property of one or more DATA extent structures was incorrect.
- ACFS-07045: DATA extent list has fewer nodes than expected\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The list of DATA extent structures of the indicated file contained fewer nodes than expected. There are two possible causes: 1. One or more of the DATA extent structures did not have a valid structure header. 2. The _NextDataExtent property of one or more DATA extent structures was incorrect.
- ACFS-07046: file has _LastExtentPointer that does not match calculated value\n calculated: string, but expected to find: string\nfor file:\nstring
-
Cause: The _LastExtentPointer property of the indicated file did not match the file's last DATA extent structure. There are three possible causes: 1. The _LastExtentPointer value was incorrect. 2. The last DATA extent structure was not found because the The _NextDataExtent property of one or more DATA extent structures was incorrect.
- ACFS-07047: extent node list missing entry for extent structure:\nstring
-
Cause: The list of extent structures of the indicated file was incomplete. One or more extent structures was missing. There are three possible causes: 1. The _LastExtentPointer property of the file was incorrect. 2. One or more extent structures did not have a valid structure header. 3. The _LastExtentPointer property of one or more extent structures was incorrect.
- ACFS-07048: metadata structure has invalid _generation_number value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _generation_number property of the indicated metadata structure was incorrect.
- ACFS-07049: extent list has more nodes than expected\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The list extent structures of the indicated file contained more nodes than expected. The _LastExtentPointer property of one or more extent structures was incorrect.
- ACFS-07050: extent list has fewer nodes than expected\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The list of extent structures of the indicated file contained fewer nodes than expected. There are two possible causes: 1. One or more of the extent structures did not have a valid structure header. 2. The _LastExtentPointer property of one or more extent structures was incorrect.
- ACFS-07051: file has incorrect _LinkCount value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _LinkCount property of the indicated file did not match the number of hard links found for the file. There are four possible causes: 1. The _LinkCount property was incorrect. 2. One or more directory entries for this file was invalid or was not found. 3. A Directory_Entry structure for this file had an incorrect file identifier. 4. The _LinkCount property of an ACFS Internal File was not equal to one.
- ACFS-07052: file has invalid _ProtectionBits value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _ProtectionBits property of the indicated files was incorrect.
- ACFS-07053: file has invalid _ParentID value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _ParentID property of the indicated file was not correct. There are two possible causes: 1. The _ParentID value did not match the file's parent directory. 2. The _ParentID value did not match any valid directory.
- ACFS-07054: file has invalid _WindowsAttributes value(s)\n found: string\n, but expected to find: 0\nfor file:\nstring
-
Cause: The _WindowsAttributes property of the indicated file was invalid. The _WindowsAttributes value must be zero since file was not created on a Windows system.
- ACFS-07055: extent[number] is not in use but it contains non-zero values:\n _FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\nfor file:\nstring
-
Cause: One of the extents of the indicated file was not in use, but it contained non-zero values. There are two possible causes: 1. The extent values were not reset to zero when the extent was freed. 2. The _NextFreeExtent property of the file was incorrect.
- ACFS-07057: extent[number] has incorrect _FileOffset\n found: string, but expected to find: 0\nfor file:\nstring
-
Cause: The _FileOffset property of the initial extent of the indicated file was not zero. The _FileOffset for a file's initial extent must be zero as it identifies the beginning of the file.
- ACFS-07058: file with local extents has invalid _LastExtentPointer value\n found: string, but expected to find: 0\nfor file:\nstring
-
Cause: The _LastExtentPointer property of the indicated file was not zero which is required for files with local extents.
- ACFS-07060: extent[number] appears to be uninitialized\nfor file:\nstring
-
Cause: An extent of the indicated file appeared to be in use, but all of its values were zero.
- ACFS-07061: extent[number] has invalid _Length value\n found: 0, but expected to find: > 0\nfor file:\nstring
-
Cause: The _Length property of an extent of the indicated file had a value of zero. _Length values must be greater than zero.
- ACFS-07062: extent[number] has incorrect _SnapIncarnationNumber value\n found: number maximum: number\nfor file:\nstring
-
Cause: The _SnapIncarnationNumber property of the indicated file exceeded the maximum value for the file system.
- ACFS-07063: extent[number] has a non-contiguous _FileOffset value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _FileOffset property of an extent of the indicated file was not contiguous with the _FileOffset of the previous extent.
- ACFS-07064: file _AllocationSize value not equal to sum of extents\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _AllocationSize property of the indicated file was not equal to the sum of the _Length properties of the file's extents. There are three possible causes: 1. The _AllocationSize value was incorrect. 2. The _Length property of one or more of the file's extents was incorrect. 3. The _NextFreeExtent property of the file was incorrect.
- ACFS-07065: File_Entry_Table calculated allocation size (sum of data extents) does not match its _FileSize value\n found: string calculated: string\nfor file:\nstring
-
Cause: The _FileSize property of File_Entry_Table did not match the sum of the file's extent _Length values. There are two possible causes: 1. The _Length property of one or more extents of the File_Entry_Table was incorrect. 2. The _FileSize property of the File_Entry_Table was incorrect.
- ACFS-07066: extent[number] is not in use but it contains non-zero values:\n _FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\n _SnapIncarnationNumber: number\nfor file:\nstring
-
Cause: One of the extents of the indicated file was not in use, but it contained non-zero values. There are two possible causes: 1. The extent values were not reset to zero when the extent was freed. 2. The _NextFreeExtent property of the file was incorrect.
- ACFS-07073: file has _FileEntry structure with incorrect or invalid _FileEntryType value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _FileEntryType property of the indicated file did not match its expected value. There are two possible causes: 1. The _FileEntryType value was incorrect for this particular file. 2. The _FileEntryType value was not on the list of valid values.
- ACFS-07074: file has _FileEntry structure with incorrect file identifier\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The file identifier property of the indicated file did not match its position within the File_Entry_Table entry.
- ACFS-07075: file has incorrect _FileSize value\n found: string minimum: string\nfor file:\nstring
-
Cause: The _FileSize property of the indicated file was incorrect.
- ACFS-07076: file has invalid _AllocationSize value\n found: string minimum: string\nfor file:\nstring
-
Cause: The _AllocationSize property of the indicated file was invalid. The _AllocationSize value for this file cannot be less than the value described in the message.
- ACFS-07077: Local_Bitmap has incorrect _FileOffset value for Extent[1]\n found: string, but expected to find: 0\nfor file:\nstring
-
Cause: The _FileOffset property in Extent[1] of the indicated Local_Bitmap was not zero.
- ACFS-07078: Local_Bitmap has incorrect _Length value in Extent[1]\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _Length property in Extent[1] of the indicated Local_Bitmap did not match the file system's allocation unit size.
- ACFS-07079: Local_Bitmap has invalid _PhysicalDiskOffset value for Extent[1]\n found: 0, but expected to find: > 0\nfor file:\nstring
-
Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated Local_Bitmap was equal to zero. This _PhysicalDiskOffset value must be greater than zero.
- ACFS-07080: Local_Bitmap has incorrect _PhysicalDiskOffset value for Extent[1]\n found: string maximum: string\nfor file:\nstring
-
Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated Local_Bitmap exceeded the size of the file system.
- ACFS-07081: file has invalid _granularity value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _granularity property of the indicated system file was incorrect. Many system files require local extents which is indicated by a _granularity value of -1.
- ACFS-07082: Global_BitMap space requirement exceeds _AllocationSize value. Bitmap requires string bytes, allocated space: string bytes\nfor file:\nstring
-
Cause: The _AllocationSize property of the Global_BitMap was not large enough to store the Global_BitMap data. There are two possible causes: 1. The _AllocationSize value was incorrect. 2. The value used to indicate the number of bits needed to map file system storage was incorrect.
- ACFS-07083: Global_BitMap has invalid _granularity value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _granularity property of the indicated Global_BitMap was incorrect. The Global_BitMap file must have a _granularity value of -1 which indicates that the file has local extents.
- ACFS-07084: Snap_Map has mismatch between _FileSize and _AllocationSize values\n _FileSize: string _AllocationSize: string\nfor file:\nstring
-
Cause: The _FileSize and _AllocationSize properties of the indicated Snap_Map file did not match. The values for these properties must match for a Snap_Map file. One or both values was incorrect.
- ACFS-07085: file has _FileSize value that exceeds _AllocationSize value\n _FileSize: string _AllocationSize: string\nfor file:\nstring
-
Cause: The _FileSize property of the indicated file exceeded the amount of storage allocated to the file. The _AllocationSize property describes the amount of storage available for the file. One of of these properties was incorrect.
- ACFS-07086: file has _AllocationSize value that is invalid for the file system\n found: string, but expected to find: multiple of string\nfor file:\nstring
-
Cause: The _AllocationSize property of the indicated file was incorrect. Its value must be a multiple of the file system allocation unit size.
- ACFS-07087: file has _AllocationSize value but no extent information\n _AllocationSize: string\nfor file:\nstring
-
Cause: The _AllocationSize property of the indicated file was greater than 0, but there was no corresponding extent information. There are two possible causes: 1. The _AllocationSize should have been zero. 2. The _NextFreeExtent value was incorrect.
- ACFS-07088: Map_File has incorrect _FileSize value\n found: string, but expected to find: multiple of number\nfor file:\nstring
-
Cause: The _FileSize property of the indicated Map_File was incorrect. The _FileSize value for a Map_File must be a multiple of the META_MAP_ENTRY size.
- ACFS-07089: Volume_Log has invalid _FileSize value\n found: string, but expected to find: 0\nfor file:\nstring
-
Cause: The _FileSize property of the indicated Volume_Log file was not equal to zero. The _FileSize value for a Volume_Log must be zero.
- ACFS-07090: Volume_Log has invalid _granularity value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _granularity property of the indicated Volume_Log file was incorrect. Volume_Log files must have a _granularity value of -1 which indicates that the file has local extents.
- ACFS-07091: Volume_Log has incorrect _NextFreeExtent value\n found: number, but expected to find: 0 or 1\nfor file:\nstring
-
Cause: The _NextFreeExtent property of the indicated Volume_Log file was incorrect. A Volume_Log file can have at most one extent.
- ACFS-07092: file has invalid _security_data_offset value\nfor file:\nstring
-
Cause: The _security_data_offset property of the indicated file did not have a corresponding entry in any Security_Metadata file. There are three possible causes: 1. The _security_data value was incorrect. 2. The Security_Metadata file had incorrect data at the corresponding offset. 3. The Security_Metadata file was not found.
- ACFS-07094: file has invalid _SnapMetaIncarnationNumber value\n found: number maximum: number\nfor file:\nstring
-
Cause: The _SnapIncarnationNumber property of the indicated file exceeded the maximum _SnapIncarnationNumber value for the file system.
- ACFS-07095: CHARACTER special file has invalid major_device_number value\n found: 0, but expected to find: > 0\nfor file:\nstring
-
Cause: The major_device_number property of the indicated CHARACTER special file was invalid. major_device_number values must be greater than zero.
- ACFS-07096: file has incorrect _EAOffset value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _EAOffset property of the indicated file was incorrect.
- ACFS-07097: file has invalid _TimeofCreation value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _TimeofCreation property of the indicated file was incorrect.
- ACFS-07098: file has invalid _TimeLastAccessed value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _TimeLastAccessed property of the indicated file was incorrect.
- ACFS-07099: file has invalid _TimeLastModified value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _TimeLastModified property of the indicated file was incorrect.
- ACFS-07100: file has invalid _FileSize value\n found: string minimum: string\nfor file:\nstring
-
Cause: The _FileSize property of the indicated file was invalid. The _FileSize value for this file cannot be less than the value described in the message.
- ACFS-07101: file has invalid _TimeLastChanged value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _TimeLastChanged property of the indicated file was incorrect.
- ACFS-07102: file has invalid _TimeofCreation value\n found: 0\nfor file:\nstring
-
Cause: The _TimeofCreation property of the indicated file was invalid. The _TimeofCreation value must be non-zero.
- ACFS-07103: file has invalid _TimeLastAccessed value\n found: 0\nfor file:\nstring
-
Cause: The _TimeLastAccessed property of the indicated file was invalid. The _TimeLastAccessed value must be non-zero.
- ACFS-07104: file has invalid _TimeLastModified value\n found: 0\nfor file:\nstring
-
Cause: The _TimeLastModified property of the indicated file was invalid. The _TimeLastModified value must be non-zero.
- ACFS-07105: file has invalid _TimeLastChanged value\n found: 0\nfor file:\nstring
-
Cause: The _TimeLastChanged property of the indicated file was invalid. The _TimeLastChanged value must be non-zero.
- ACFS-07106: file has invalid _WindowsAttributes value(s)\n found: string\n valid values: string\nfor file:\nstring
-
Cause: The _WindowsAttributes property of the indicated file was invalid. One or more of the _WindowsAttributes values were not within the range of valid values. Refer to the corresponding messages for a list of valid values.
- ACFS-07107: file has incorrect _rep_incarnation value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _repFE_incarnation_number property of the indicated file was incorrect.
- ACFS-07108: file has incorrect _rep_VFN value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _rep_VFN property of the indicated file was incorrect.
- ACFS-07109: file has incorrect _rep_SCN value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _rep_SCN property of the indicated file was incorrect.
- ACFS-07110: file has incorrect _EncrMetaOffset value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _EncrMetaOffset property of the indicated file was incorrect.
- ACFS-07111: file has incorrect _Vault_MetaOffset value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _Vault_MetaOffset property of the indicated file was incorrect.
- ACFS-07112: file has incorrect _EncrSecFlags value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _EncrSecFlags property of the indicated file was incorrect.
- ACFS-07113: file has incorrect _EA_ContainerUnits value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _EA_ContainerUnits property of the indicated file was incorrect.
- ACFS-07115: Local_Bitmap has incorrect _FileSize value\n found: string, but expected to find: 0\nfor file:\nstring
-
Cause: The _FileSize property of the indicated Local_Bitmap was invalid. The _FileSize value for a Local_Bitmap must be zero.
- ACFS-07116: BLOCK special file has invalid major_device_number value\n found: 0, but expected to find: > 0\nfor file:\nstring
-
Cause: The major_device_number property of the indicated BLOCK special file was invalid. major_device_number values must be greater than zero.
- ACFS-07117: Directory_Entry structure has invalid file identifier value:\n found: string maximum: string\nfor structure:\nstring
-
Cause: The file identifier property of the indicated Directory_Entry structure exceeded the maximum file identifier for the file system.
- ACFS-07118: System metadata file is corrupt and cannot be repaired\nfor file:\nstring
-
Cause: The ACFS Checker/Fixer found an inconsistency with the indicated system metadata file. This metadata file cannot be repaired due to the nature of the corruption.
- ACFS-07119: _Locator structure has incorrect _global_dir_blk value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _global_dir_blk property of the indicated structure was incorrect.
- ACFS-07120: _Locator structure has invalid node identifier for entry number in _node_number array\n found: number maximum: number\nfor structure:\nstring
-
Cause: A node identifier in the _node_number array of the indicated structure that exceeded the maximum value for the file system.
- ACFS-07121: _Locator structure has invalid file identifier for entry number in _local_dir_blk array\n found: string maximum: string\nfor structure:\nstring
-
Cause: A file identifier for a Local_Metadata_Directory in the _local_dir_blk array of the indicated _Locator structure exceeded the maximum file identifier for the file system.
- ACFS-07122: _Locator structure has incorrect _local_dir_blk_disk_offset for entry number in _local_dir_blk_disk_offset array\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The disk offset for a Local_Metadata_Directory in the _local_dir_blk_disk_offset array of the indicated _Locator structure was incorrect. There are two possible causes: 1. The _local_dir_blk_disk_offset value was incorrect. 2. The structure at the _local_dir_blk_disk_offset was not a Local_Metadata_Directory structure.
- ACFS-07123: _Locator structure has duplicate entries for node number\nfor structure:\nstring
-
Cause: There was more than one entry for the same node within the _Locator structure(s). Node identifies must be unique.
- ACFS-07124: _Locator structure has duplicate entries for Local_Metadata_Directory: string\nfor structure:\nstring
-
Cause: There was more than one entry for the same Local_Metadata_Directory within the _Locator structure(s). Local_Metadata_Directory file identifiers must be unique.
- ACFS-07125: _Locator structure has incorrect _node_count value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _node_count property of the indicated _Locator structure did not match the number of valid nodes found.
- ACFS-07126: _Locator structure has incorrect _next_locator_blk_disk_offset value\n found: string\nfor structure:\nstring
-
Cause: The _next_locator_blk_disk_offset property of the indicated _Locator structure was incorrect. There are two possible causes: 1. The _next_locator_blk_disk_offset was incorrect. 2. The structure at the _next_locator_blk_disk_offset was not a _Locator structure.
- ACFS-07127: Global_Virtual_FileID_Pool structure has incorrect _repFreeVFNGroup value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _repFreeVFNGroup property of the indicated Global_Virtual_FileID_Pool structure was incorrect.
- ACFS-07128: Global_Virtual_FileID_Pool structure has incorrect _repFreeVFNIncarnNum value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _repFreeVFNIncarnNum property of the indicated Global_Virtual_FileID_Pool structure was incorrect.
- ACFS-07129: Replication_Log_Initiator structure has incorrect _initiator_node_id value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _initiator_node_id property of the indicated Replication_Log_Initiator structure was incorrect.
- ACFS-07130: Replication_Log_Initiator structure has incorrect _new_rlog_recovered value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _it_rep_logs_processed property of the indicated Replication_Log_Initiator structure was incorrect.
- ACFS-07131: Replication_Log_Initiator structure has incorrect _next_cord_id value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _next_cord_id property of the indicated Replication_Log_Initiator structure was incorrect.
- ACFS-07132: Replication_Log_Initiator structure has incorrect _next_segment_id value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _next_segment_id property of the indicated Replication_Log_Initiator structure was incorrect.
- ACFS-07133: Local_Bitmap has incorrect _AllocationSize value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _AllocationSize property of the indicated Local_Bitmap did not match the _Length value of its first extent.
- ACFS-07134: invalid global_dir_fileid value\n found: string, but expected to find: string
-
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
- ACFS-07135: Global_Metadata_Directory structure has incorrect _node_number value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _node_number property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07136: Global_Metadata_Directory structure has incorrect _global_free_blk_list value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _global_free_blk_list property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07137: Global_Metadata_Directory structure has incorrect _global_bitmap_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _global_bitmap_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07138: Global_Metadata_Directory structure has incorrect _SuperBlock_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _SuperBlock_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07139: Global_Metadata_Directory structure has incorrect _gdrfl_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _gdrfl_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07140: Global_Metadata_Directory structure has incorrect _dotofs_dir_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _dotofs_dir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07141: Global_Metadata_Directory structure has incorrect _ready_dir_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _ready_dir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07142: Global_Metadata_Directory structure has incorrect _repl_config_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _repl_config_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07143: Global_Metadata_Directory structure has incorrect _mmap_log_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _mmap_log_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07144: Global_Metadata_Directory structure has incorrect _repGlobalVFNPool_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _repGlobalVFNPool_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07145: Global_Metadata_Directory structure has incorrect _repl_config_tbl_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _repl_config_tbl_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07146: Global_Metadata_Directory structure has incorrect _repLogCutInitiatorBlock_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _repLogCutInitiatorBlock_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07147: Global_Metadata_Directory structure has incorrect _repLogCutInitiatorBlock_offset value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _repLogCutInitiatorBlock_offset property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07148: Global_Metadata_Directory structure has incorrect _snap_map_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _snap_map_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07149: Global_Metadata_Directory structure has incorrect _snaps_dir_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _snaps_dir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07150: Global_Metadata_Directory structure has incorrect _global_tagdir_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _global_tagdir_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07151: Global_Metadata_Directory structure has incorrect _ea_change_fileid\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _ea_change_fileid property of the indicated Global_Metadata_Directory structure was incorrect.
- ACFS-07152: orphan directory 'string' (file identifier: string) \nadded to 'lost+found' directory
-
Cause: The indicated directory did not have a valid entry in any parent directory. The ACFS Fixer move the file to the 'lost+found' directory.
- ACFS-07154: An attempt to create a low-fragmentation memory heap failed.\nstring will attempt to continue with the standard memory heap but may run out of memory.
-
Cause: A call to the Windows HeapCreate function failed. Refer to the accompanying message(s) for more information on the error.
- ACFS-07155: An attempt to initialize a low-fragmentation memory heap failed.\nstring will attempt to continue with the standard memory heap but may run out of memory.
-
Cause: A call to the Windows HeapSetInformation function failed. Refer to the accompanying message(s) for more information on the error.
- ACFS-07156: Local_Metadata_Directory structure has incorrect _map_file_disk_offset value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _map_file_disk_offset property of the indicated Local_Metadata_Directory structure was incorrect.
- ACFS-07157: Local_Metadata_Directory structure has incorrect _vol_log_disk_offset value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _vol_log_disk_offset property of the indicated Local_Metadata_Directory structure was incorrect.
- ACFS-07158: unable to create Security_Metadata file offset list\nfor file:\nstring
-
Cause: The ACFS Checker could not create the Security_Metadata file offset list. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07159: Local_Metadata_Directory structure has incorrect _smf_fileid value \n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _smf_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
- ACFS-07160: Local_Metadata_Directory structure has incorrect _it_rlog_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _it_rlog_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
- ACFS-07161: Local_Metadata_Directory structure has incorrect _rlog_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _rlog_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
- ACFS-07162: Local_Metadata_Directory structure has incorrect _it_rmap_file_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _it_rmap_file_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
- ACFS-07163: Local_Metadata_Directory structure has incorrect _rmap_file_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _rmap_file_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
- ACFS-07164: Local_Metadata_Directory structure has incorrect _repLocalVFNPool_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _repLocalVFNPool_fileid property of the indicated Local_Metadata_Directory structure was incorrect.
- ACFS-07165: invalid file identifier: string
-
Cause: The file identifier enetered must be a valid numeric value, greater than or equal to 0, and less than the maximum file identifier value for the file system.
- ACFS-07167: Functionality may be limited due to problems accessing the accelerator volume: string.
-
Cause: An attempt to open the accelerator volume failed. Refer to the accompanying messages for more information on the problem.
- ACFS-07168: Global_BitMap has incorrect value for bitmap size\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The bitmap size property of the indicated Global_BitMap file was incorrect. Its value did not the bitmap size that was calculated for the file system.
- ACFS-07169: Global_BitMap has incorrect _AllocationSize value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _AllocationSize property of the indicated Global_BitMap file was incorrect. The _AllocationSize value was not large enough to store the Global_BitMap data as determined by the ACFS Checker.
- ACFS-07170: Global_BitMap has incorrect values for Extent[0]\n found: _FileOffset: string _Length: string _PhysicalDiskOffset: string\n, but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring
-
Cause: The _PhysicalDiskOffset property of the first extent of the indicated Global_BitMap file was incorrect. The Global_BitMap data must begin at the disk offset described in the message.
- ACFS-07171: attempt to read SuperBlock FileEntry failed\nfor file:\nstring
-
Cause: An attempt to read SuperBlock metadata failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07172: file has incorrect values for Extent[number] \n found: _FileOffset: string _Length: string _PhysicalDiskOffset: string \n, but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string \nfor file:\nstring
-
Cause: One or more values of an extent of the indicated file was incorrect.
- ACFS-07175: file has incorrect values for Extent[number]\n found: _FileOffset: string _Length: string \n, but expected to find: _FileOffset: string _Length: string\nfor file: \nstring
-
Cause: One or more values of an extent of the indicated file was incorrect.
- ACFS-07176: file has invalid _AllocationSize value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _AllocationSize property of the indicated file was incorrect.
- ACFS-07177: file has incorrect _FileSize value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _FileSize property of the indicated file was incorrect.
- ACFS-07178: file has incorrect _granularity value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _granularity property of the indicated file was incorrect. Some ACFS internal files must have a _granularity value equal to -1 which indicates that the file has local extents.
- ACFS-07179: file has incorrect _NextFreeExtent value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _NextFreeExtent property of the indicated file was incorrect.
- ACFS-07180: There is an inconsistency between the ACFS Map_File and the ACFS Log_File.
-
Cause: An inconsistency was found between the ACFS Map and Log Files which prevented the processing of transaction data.
- ACFS-07184: Log_File not processed for node number\nfor file:\nstring
-
Cause: A Log_File was found but not processed. Unprocessed Log_Files could result in false errors being reported because transaction data was not applied to the file system.
- ACFS-07185: The ACFS Map _FileSize: number indicates that there is transaction data \nto be processed, but the ACFS Log _AllocationSize: number indicates that \nthere is no data available. \nACFS Map_File:\nstring \nACFS Log_File: \nfor file: \nstring
-
Cause: An inconsistency was found between the ACFS Map and Log Files which prevented the processing of transaction data.
- ACFS-07188: Map_File has entry with incorrect _Length value\n found: number\nfor file:\nstring
-
Cause: There are two possible causes: 1. The Map_File entry's _Length was equal to zero. 2. The Map_File entry's _Length was not a multiple of the volume's sector size as detailed in the message.
- ACFS-07189: Map_File has entry with incorrect _ActualDiskOffset value\n found: string minimum: string\nfor file:\nstring
-
Cause: The _ActualDiskOffset property for an entry in the indicated Map_File was incorrect. The _ActualDiskOffset value in a Map_File entry must be greater than the previous entry's _ActualDiskOffset.
- ACFS-07190: Map_File has an entry with invalid _LogDiskOffset value\n found: string minimum: string maximum: string\nfor file:\nstring
-
Cause: The _LogDiskOffset property for an entry in the indicated Map_File was incorrect. The _LogDiskOffset value in a Map_File entry must be within the corresponding Log_File data.
- ACFS-07191: Map_File has duplicate entries for _ActualDiskOffset:string\nfor file:\nstring
-
Cause: The indicated Map_File contained more than one entry for the same disk offset. _ActualDiskOffset values must be unique within a Map File.
- ACFS-07192: Map_File has incorrect Map_Entry _Length for the Volume_Disk_Header\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _Length property for an entry in the indicated Map_File was incorrect. The entry was for a Volume_Disk_Header structure, but its _Length value did not match the size of a Volume_Disk_Header structure.
- ACFS-07193: Map_File entry with an invalid _ActualDiskOffset value\n found: string maximum: string\nfor file:\nstring
-
Cause: The _ActualDiskOffset property for an entry in the indicated Map_File was incorrect. The _ActualDiskOffset value that exceeded the size of this file system.
- ACFS-07195: metadata write failed while processing Volume_Log transaction data at disk offset: string\nfor file:\nstring
-
Cause: An error occurred while writing Volume_Log transaction data to the file system. Refer to the accompanying message(s) for more information.
- ACFS-07196: write failed for Map_File metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring
-
Cause: An attempt to write a metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07197: discarding Volume_Log and Map_File contents on node number due to processing error
-
Cause: An error occurred while processing file system transaction data. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07199: write failed for Volume_Log metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring
-
Cause: An attempt to update a metadata structure of the indicated Volume_Log file failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07200: duplicate _SnapFetaFenum: string found for the following snapshots:\n
-
Cause: The _SnapFetaFenum property of the indicated snapshots had the same value. _SnapFetaFenum values must be unique.
- ACFS-07201: Global_Free_Block list is corrupt
-
Cause: A metadata inconsistency was found within the Global_Free_Block list for the file system.
- ACFS-07202: Free_Block_List has incorrect _free_blk_count value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _free_blk_count property of the indicated Free_Block_List was incorrect.
- ACFS-07203: results for Snap_Map data may be limited or incorrect due to inconsistencies with Snap_Map metadata
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07204: write failed for Global_BitMap metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring
-
Cause: An attempt to update a metadata structure of the indicated Global_BitMap file failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07205: functionality may be limited due to File_Entry_Table metadata inconsistency
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07206: read failed for Local_BitMap metadata structure at disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring
-
Cause: An attempt to read a metadata structure of the indicated Local_BitMap file failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07207: functionality related to snapshots disabled due to problems accessing Snap_Map file
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07208: Local_BitMap (file identifier: string) has incorrect size\n found: string, but expected to find: string \nfor file:\nstring
-
Cause: The size property of the indicated Local_BitMap was incorrect.
- ACFS-07209: Local_BitMap (file identifier: string) has incorrect Global_BitMap file offset: string or incorrect disk offset: string \nfor file:\nstring
-
Cause: The Global_BitMap offset property of the indicated Local_BitMap was incorrect.
- ACFS-07211: mismatch between Local_BitMap (file identifier: string) and temporary Global_BitMap for disk offset: string
-
Cause: The bitmap data of the indicated Local_BitMap did not match the corresponding bitmap data of the temporary Global_BitMap for the described disk offset.
- ACFS-07212: temporary Global_BitMap bit set for disk offset: string exceeds maximum offset: string
-
Cause: The bitmap data of the temporary Global_BitMap referenced storage that is beyond the size of this file system.
- ACFS-07215: Volume_Disk_Header has invalid _VolSignature value\n found: 'string',\n but expected to find: string, string, string, string or string\nfor structure:\nstring
-
Cause: The _VolSignature property of the indicated Volume_Disk_Header was not a valid ACFS volume signature.
- ACFS-07216: Volume_Disk_Header has incorrect _Checksum value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _Checksum property of the indicated Volume_Disk_Header did not match its calculated value.
- ACFS-07217: Volume_Disk_Header version does not match string version\n found: number.number, but expected to find: number.number\nfor structure:\nstring
-
Cause: The _MajorVersionNumber and _MinorVersionNumber properties of the indicated Volume_Disk_Header did not match the version of the ACFS Checker/Fixer or ACFS debug utility that was being used. The ACFS Checker/Fixer or ACFS debug utility was not compatible with this file system. There are two possible causes: 1. The version information in the Volume_Disk_Header structure was not correct. 2. The ACFS Checker/Fixer or ACFS debug utility was not the correct version for the file system.
- ACFS-07218: Volume_Disk_Header has incorrect _VolVolumeSize value\n found: string maximum: string\n- temporarily assuming Volume Size: string\nfor structure:\nstring
-
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header exceeded the size of the volume. The ACFS Checker temporarily assumed the maximum volume size during processing.
- ACFS-07219: Volume_Disk_Header has incorrect _VolVolumeSize value\n found: string minimum: string\n- temporarily assuming Volume Size: string\nfor structure:\nstring
-
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header was less than the minimum supported volume size as detailed in the message. The ACFS Checker temporarily assumed the maximum volume size during processing.
- ACFS-07220: Volume_Disk_Header has incorrect _VolClusterSize value\n found: string, but expected to find: string\n- assuming default size: string\nfor structure:\nstring
-
Cause: The _VolClusterSize property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default value during processing.
- ACFS-07221: Volume_Disk_Header has incorrect _VolFETALPosition value\n found: string, but expected to find: string\n- assuming default File_Entry_Table offset: string\nfor structure:\nstring
-
Cause: The _VolFETALPosition property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default File_Entry_Table offset during processing.
- ACFS-07222: Volume_Disk_Header has incorrect _VolOrigVolumeSize value\n found: string must be aligned on a string byte boundary\nfor structure:\nstring
-
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
- ACFS-07223: Volume_Disk_Header has incorrect _VolExtentHeaderSize value\n found: string, but expected to find: string\n- assuming default value: string\nfor structure:\nstring
-
Cause: The _VolExtentHeaderSize property of the indicated Volume_Disk_Header was incorrect. The ACFS Checker temporarily assumed the default value during processing.
- ACFS-07224: cannot process command due to Snap_Map File metadata inconsistency
-
Cause: An acfsdbg command was not executed due to a metadata inconsistency.
- ACFS-07225: Volume_Disk_Header has invalid _VolFileSystemEndian value\n found: character, but expected to find: string or string\nfor structure:\nstring
-
Cause: The _VolFileSystemEndian property of the indicated Volume_Disk_Header was invalid.
- ACFS-07226: Volume_Disk_Header has invalid _VolStateFlag values.\n found: string\n, but expected to find: string or string\nfor structure:\nstring
-
Cause: The _VolStateFlag property of the indicated Volume_Disk_Header contained one or more invalid values.
- ACFS-07227: missing snapshot name or identifier
-
Cause: A snapshot name or identifier was not entered as required for this command.
- ACFS-07228: cannot determine disk geometry for volume: string
-
Cause: The program was unable to determine the geometry of the indicated volume. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07229: volume: string has invalid sector size\n found: number, but expected to find: number\n- assuming default value: number
-
Cause: The sector size of the indicated volume was invalid. The ACFS Checker temporarily assumed the default sector size during processing.
- ACFS-07230: cannot determine size for volume: string
-
Cause: The program was unable to determine the size of the indicated volume. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07231: seek to end of volume failed for volume: string offset: string
-
Cause: The program was unable to seek to the end of the indicated volume. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07232: seek to end of volume failed for volume: string\n requested offset: string returned offset: string
-
Cause: The request to seek to the end of the indicated volume failed. The offset set returned did not match the offset requested. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07233: read failed for Primary Volume_Disk_Header at disk offset: string
-
Cause: An attempt to read the Primary Volume_Disk_Header at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07234: read failed for Alternate Volume_Disk_Header at disk offset: string
-
Cause: An attempt to read the Alternate Volume_Disk_Header at the indicated disk offset failed. Refer to the accompanying message(s) for more information on the problem. problem.
- ACFS-07235: extent[number] has invalid _PhysicalDiskOffset value\n found: 0, but expected to find: greater than 0\nfor file:\nstring
-
Cause: The _PhysicalDiskOffset property of an extent structure of the indicated file had a value of zero. _PhysicalDiskOffset values must be greater than zero.
- ACFS-07236: extent[number] has invalid _PhysicalDiskOffset value\n found: 0, but expected to find: greater than 0\nfor structure:\nstring
-
Cause: The _PhysicalDiskOffset property of an extent of the indicated extent structure had a value of zero. _PhysicalDiskOffset values must be greater than zero.
- ACFS-07237: read failed for File_Entry_Table extent metadata structure at disk offset: string\nfor file:\nstring
-
Cause: An attempt to read an extent metadata structure of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07239: File_Entry_Table count incorrect\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The number of entries found in the File_Entry_Table file did not match the expected number of entries. One or more of the extent structures was invalid.
- ACFS-07240: Invalid Security_Metadata_File
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07241: Security_Metadata file has invalid _security_descriptor record\nfor file:\nstring
-
Cause: A _security_descriptor record of the indicated Security_Metadata file was invalid.
- ACFS-07243: Security_Metadata file has no valid _security_data records\nfor file:\nstring
-
Cause: The indicated Security_Metadata file did not contain any valid valid _security_data records.
- ACFS-07245: Security_Metadata file contains invalid _security_descriptor data\nfor file:\nstring
-
Cause: The indicated Security_Metadata file contained at least one invalid _security_data record. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07246: Security_Metadata file _Private structure is invalid for:\nfor file:\nstring
-
Cause: The _Private structure of the indicated Security_Metadata file was invalid. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07247: Security_Metadata file has invalid Hash_Table data\nfor file:\nstring
-
Cause: The Hash_Table of the indicated Security_Metadata file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07250: Security_Metadata file _Private structure has invalid _maxFree value\n found: number minimum: number\nfor structure:\nstring
-
Cause: The _maxFree property of the indicated _Private metadata structure was incorrect.
- ACFS-07251: Security_Metadata file _Private structure has invalid _freeDataListTail value\n found: number minimum: number\nfor structure:\nstring
-
Cause: The _freeDataListTail property of the indicated _Private metadata structure was incorrect.
- ACFS-07252: Security_Metadata file node not on _freeDataList\nfor file:\nstring
-
Cause: One or more of the _security_data nodes of the indicated Security_Metadata file was not found on the free data node list. The _next property for one or more of the _security_data nodes was incorrect.
- ACFS-07254: Security_Metadata file has invalid _security_record for _Administrator default\nfor file:\nstring
-
Cause: The default _Administrator _security_record of the indicated Security_Metadata file was invalid.
- ACFS-07256: file has unexpected _ProtectionBits value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _ProtectionBits property of the indicated files was not expected.
- ACFS-07257: unable to process request for volume string; volume is not open
-
Cause: An attempt to read metadata failed because the volume was not open. Refer to the accompanying messages for more information on the problem.
- ACFS-07258: unable to reset context to snapshot string due to File_Entry_Table metadata inconsistency
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07259: file system does not contain a valid Local_Metadata_Directory
-
Cause: There was no valid Local_Metadata_Directory in the file system. At least one Local_Metadata_Directory is required.
- ACFS-07260: Volume_Disk_Header has incorrect _VolNumOFSNodes value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _VolNumOFSNodes property of the indicated Volume_Disk_Header structure was incorrect. Its value did not match the number of valid ACFS nodes found.
- ACFS-07261: unable to reset context to snapshot string due to Snap_Map file metadata inconsistency
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07262: unable to reset context to snapshot string because it no longer exists
-
Cause: The identified snapshot no longer exists due to on-disk metadata changes that are allowed whenever the acfsdbg utility is operating in read-only mode.
- ACFS-07263: Free_Block_List has incorrect _first_free_group value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _first_free_group property of the indicated Free_Block_List structure was incorrect.
- ACFS-07264: Free_Block_List has incorrect _last_free_blk value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _last_free_blk property of the indicated Free_Block_List structure was incorrect.
- ACFS-07265: write failed for Free_Block metadata structure at disk offset: string size: number bytes\nfor structure:\nstring
-
Cause: An attempt to write a Free_Block metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07266: write failed for Free_Block_List metadata structure at disk offset: string size: number bytes\nfor structure:\nstring
-
Cause: An attempt to write a Free_Block_List metadata structure to disk failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07267: file marked for deletion (file identifier: string, disk offset: string) cannot be removed due to inconsistent file metadata
-
Cause: Inconsistent metadata was found for the indicated file that was marked for deletion. The file could not be deleted.
- ACFS-07268: file marked for deletion (file identifier: string, disk offset: string) has invalid _LinkCount value\n found: number, but expected to find: 0
-
Cause: The indicated file was marked for deletion, but its _LinkCount property was not zero. Files to be deleted must have a _LinkCount value of zero. The file could not be deleted.
- ACFS-07271: orphan file : string (file identifier: string) added to 'lost+found' directory
-
Cause: The indicated file did not have a valid entry in any parent directory. The ACFS Fixer move the file to the 'lost+found' directory.
- ACFS-07272: read failed for extent metadata structure at disk offset: string\nfor file:\nstring
-
Cause: An attempt to read an extent metadata structure for the indicated file failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07274: missing or invalid snapshot name
-
Cause: No snapshot name was provided or the name entered was not valid.
- ACFS-07275: cannot read File_Entry_Table _FileEntry metadata structure\n- file system validation cannot continue
-
Cause: An attempt to read the _FileEntry metadata structure of the File_Entry_Table failed. The File_Entry_Table is a critical ACFS metadata structure that is required for file system validation or repairs. The ACFS Checker/Fixer could not process the file system. NOTE: It is also possible that there was no ACFS file system on this volume.
- ACFS-07276: File_Entry_Table _FileEntry metadata structure is invalid\n- file system validation cannot continue
-
Cause: The File_Entry_Table's _FileEntry metadata structure is either corrupt or is missing critical information. NOTE: It is also possible that there is no ACFS file system on the volume.
- ACFS-07280: checking File_Entry_Table entry: string at disk offset: string
-
Cause: The ACFS Checker found a File_Entry_Table entry that has not been processed. This entry was an orphan file or an orphan internal metadata structure.
- ACFS-07282: read failed for File_Entry_Table entry: string at disk offset string
-
Cause: An attempt to read a File_Entry_Table entry failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07283: orphan File_Entry_Table metadata structure found for\n identifier: string at disk offset: string\n structure type: string
-
Cause: A File_Entry_Table entry was found that had not been processed. This entry was an orphan file or an invalid internal metadata structure.
- ACFS-07284: orphan system file found for file identifier: string at disk offset:string
-
Cause: The indicated system file did not have a valid parent directory.
- ACFS-07285: snapshot: string (identifier: number) has invalid File_Entry_Table identifier: string that exceeds the maximum value for this file system: string
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07286: orphan file found for file identifier: string at disk offset: string
-
Cause: The indicated file did not have a valid parent directory.
- ACFS-07287: orphan Free_Block metadata structure found for file identifier: string at disk offset: string
-
Cause: The indicated Free_Block metadata structure was not found on any free block list.
- ACFS-07288: orphan file 'string' (file identifier: string) \nadded to 'lost+found' directory
-
Cause: The indicated file did not have a valid entry in any directory which meant that the file did not have a valid file name. The file was given the generic name described in the message and moved to the 'lost+found' directory.
- ACFS-07289: orphan Local_Metadata_Directory metadata structure found for file identifier: string at disk offset: string
-
Cause: The indicated Local_Metadata_Directory metadata structure was not found on any _Locator list for Local_Metadata_Directory structures.
- ACFS-07290: orphan Free_List_Header metadata structure found for file identifier: string at disk offset: string
-
Cause: The indicated Free_List_Header metadata structure was not found on any valid Local_Metadata_Directory structure.
- ACFS-07291: orphan _Locator metadata structure found for file identifier: string at disk offset: string
-
Cause: The indicated _Locator metadata structure was not found in any list of valid _Locator structures.
- ACFS-07292: orphan Global_Metadata_Directory metadata structure found for file identifier: string at disk offset: string
-
Cause: The File_Entry_Table contained a duplicate Global_Metadata_Directory metadata structure. Global_Metadata_Directory structures must be unique.
- ACFS-07294: orphan Global_Virtual_FileID_Pool metadata structure found for identifier: string at disk offset: string
-
Cause: The File_Entry_Table contained a duplicate entry for the Global_Virtual_FileID_Pool metadata structure. Global_Virtual_FileID_Pool structures must be unique.
- ACFS-07295: orphan Local_Virtual_FileID_Pool metadata structure found for identifier: string at disk offset: string
-
Cause: The indicated Local_Virtual_FileID_Pool metadata structure was not found on any valid Local_Metadata_Directory structure.
- ACFS-07296: orphan Replication_Log_Initiator metadata structure found for identifier: string at disk offset: string
-
Cause: The File_Entry_Table contained a duplicate entry for a Replication_Log_Initiator metadata structure. Replication_Log_Initiator structures must be unique.
- ACFS-07297: File_Entry_Table entry: string at disk offset: string is not a valid metadata structure
-
Cause: The indicated entry in the File_Entry_Table was not a metadata structure recognized by ACFS.
- ACFS-07298: cannot convert file identifier: 'string' to numeric value
-
Cause: The format entered for the file identifier was invalid.
- ACFS-07300: directory Hash_Table contains duplicate entries for offset: string\nfor file:\nstring
-
Cause: The Hash_Table of the indicated directory file had duplicate entries for the offset described in the message. Hash_Table entries must map to unique offsets.
- ACFS-07301: directory _hash_key: string for offset: string has no corresponding file entry\nfor file:\nstring
-
Cause: The _hash_key property of the indicated directory file was invalid. Its value did not reference a valid file entry.
- ACFS-07302: directory _hash_key for offset: string is incorrect\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _hash_key property of the indicated directory file was incorrect. Its value did not match the hash value calculated for the corresponding file entry.
- ACFS-07303: Security_Metadata file Hash_Table contains multiple entries for offset: string\nfor file:\nstring
-
Cause: The Hash_Table of the indicated Security_Metadata file had duplicate entries for the offset described in the message. Hash_Table entries must map to unique offsets.
- ACFS-07304: Security_Metadata file _hash_key: string for offset: string has no corresponding entry\nfor file:\nstring
-
Cause: The _hash_key property of the indicated Security_Metadata file was invalid. Its value did not reference a valid entry.
- ACFS-07305: Security_Metadata file _hash_key for offset: string is incorrect\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _hash_key property of the indicated Security_Metadata file was incorrect. Its value did not match the hash value calculated for the corresponding entry.
- ACFS-07306: Hash_Table _hash_key order is incorrect\nfor file:\nstring
-
Cause: The _hash_key properties of the Hash_Table of the indicated file were not ordered correctly.
- ACFS-07308: Hash_File_Index structure for block number at disk offset: string already processed\nfor file:\nstring
-
Cause: The Hash_File node list of the indicated file was invalid. One or more of the Hash_File structures had an invalid _next property.
- ACFS-07309: cannot access Hash_File_Index node metadata structure at disk offset: string\nfor file:\nstring
-
Cause: An attempt to access the indicated Hash_File_Index metadata structure failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07310: Hash_File_Index node has incorrect _next value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _next property of the indicated Hash_File_Index structure was incorrect.
- ACFS-07311: Hash_Bucket for block number at disk offset: string already processed\nfor structure:\nstring
-
Cause: The Hash_Bucket structure of the indicated file has already been processed. One or more of the Hash_File structures had an invalid _next property.
- ACFS-07312: cannot access Hash_Bucket metadata structure at disk offset: string\nfor file:\nstring
-
Cause: An attempt to access the indicated Hash_Bucket metadata structure failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07313: Hash_Bucket has incorrect _controlling_bkt value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was incorrect.
- ACFS-07314: Hash_Bucket has incorrect _split_count value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _split_count property of the indicated Hash_Bucket structure was incorrect.
- ACFS-07315: Hash_Bucket has incorrect _next value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _next property of the indicated Hash_Bucket structure was incorrect.
- ACFS-07316: cannot access Hash_File_Master_Block metadata structure at disk offset: string\nfor file:\nstring
-
Cause: An attempt to access the indicated Hash_File_Master_Block metadata structure failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07317: Hash_File metadata structure for block:number at disk offset: string already processed\nfor file:\nstring
-
Cause: The list of nodes of the indicated Hash_File file was invalid. One or more of the Hash_File structures had an invalid _next property.
- ACFS-07318: Hash_File_Master_Block structure has incorrect _initial_bkt_count value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _initial_bkt_count property of the indicated Hash_File_Master_Block structure was incorrect.
- ACFS-07319: Hash_File_Master_Block structure has incorrect _double_count value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _double_count property of the indicated Hash_File_Master_Block structure was incorrect.
- ACFS-07320: Hash_File_Master_Block structure has incorrect value for entry number in _hash_bucket_group array\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The entry in _hash_bucket_group array of the indicated Hash_File_Master_Block was incorrect.
- ACFS-07321: _hash_entry number has no corresponding entry\nfor file:\nstring
-
Cause: The _hash_entry property in the Hash_Table of the indicated file did not have a valid entry associated with it.
- ACFS-07322: metadata read failed at disk offset: string size: number bytes\nfor file:\nstring
-
Cause: An attempt to read metadata of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07326: metadata read failed at disk offset: string\n bytes requested: number bytes returned: number\nfor file:\nstring
-
Cause: An attempt to read metadata of the indicated file failed. The amount of data returned did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07327: metadata write failed at disk offset: string size: number bytes\nfor file:\nstring
-
Cause: An attempt to write metadata of the indicated file failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07331: metadata write failed at disk offset: string\n bytes requested: number bytes written: number\nfor file:\nstring
-
Cause: An attempt to write metadata of the indicated file failed. The amount of data written did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07332: cannot convert snapshot identifier: 'string' to numeric value
-
Cause: The format entered for the snapshot identifier was invalid.
- ACFS-07333: invalid snapshot identifier entered: string\n minimum: 1 maximum: number
-
Cause: The snapshot identifier entered was not within the valid range for this file system.
- ACFS-07334: invalid snapshot name 'string' entered
-
Cause: The snapshot name entered did not exist.
- ACFS-07335: Directory_Node has invalid _dir_entry_free_list_tail value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _dir_entry_free_list_tail property of the indicated Directory_Node structure was incorrect.
- ACFS-07336: Directory_Node structure has invalid _next_free_dirnode value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _next_free_dirnode property of the indicated Directory_Node structure was incorrect.
- ACFS-07337: Directory_Entry structure has incorrect file identifier for file 'string'\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The file identifier property of the indicated Directory_Entry structure did not match the file identifier of the corresponding file.
- ACFS-07338: Directory_Entry structure has incorrect _rec_len value for file 'string'\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _rec_len property of the indicated Directory_Entry structure was incorrect.
- ACFS-07339: Directory_Entry structure has incorrect _name_len value for file 'string'\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _name_len property of the indicated Directory_Entry structure was incorrect.
- ACFS-07340: Directory_Entry structure has invalid or incorrect _attributes for file 'string'\n found: string\n, but expected to find: string\nfor structure:\nstring
-
Cause: The _attributes property of the indicated Directory_Entry structure did not match the _attributes property of the corresponding file.
- ACFS-07341: starting disk offset string exceeds ending disk offset string
-
Cause: The starting storage map offset was greater than the ending offset.
- ACFS-07342: Directory_Entry structure has incorrect filename for file\n found: 'string', but expected to find: 'string'\nfor structure:\nstring
-
Cause: The filename property of the indicated Directory_Entry structure did not match the name of the file.
- ACFS-07343: unused Directory_Entry structure has incorrect _name_len value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _name_len property of the indicated Directory_Entry structure was incorrect.
- ACFS-07344: Directory_Entry structure has incorrect _rec_len value for file 'string'\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _rec_len property of the indicated Directory_Entry structure was greater than the maximum value.
- ACFS-07345: Directory_Entry structure has incorrect _rec_len value for file 'string'\n found: number minimum: number\nfor structure:\nstring
-
Cause: The _rec_len property of the indicated Directory_Entry structure was less than the minimum value.
- ACFS-07346: Directory_Entry structure has invalid _name_len value\n found: number operating system maximum: number\nfor structure:\nstring
-
Cause: The _name_len property of the indicated Directory_Entry structure was greater than the maximum value for this operating system.
- ACFS-07347: Directory_Entry structure has incorrect _name_len value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _name_len property of the indicated Directory_Entry structure was greater than the maximum value for this entry.
- ACFS-07350: command disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap' to set context
-
Cause: The acfsdbg utility could not process the request because the File_Entry_Table context was not set. The acfsdbg utility requires a valid File_Entry_Table context to locate on-disk metadata structures.
- ACFS-07351: requested Snap_Info_Entry structure not available due to inconsistencies with Snap_Map metadata
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07352: snapshot directory contains files with incorrect attributes; attempting to continue processing
-
Cause: The _attributes property for a file in the indicated snapshot directory was incorrect. The _attributes value indicated that the file was not a directory. All files in a snapshot directory must be directories.
- ACFS-07354: file has incorrect or invalid _attributes value\n found: string\n, but expected to find: string\nfor file:\nstring
-
Cause: The _attributes property of the indicated file was incorrect.
- ACFS-07355: Cannot fix orphaned files because the lost+found directory is damaged.
-
Cause: Fsck could not move the orphan files because there was an inconsistency with the lost+found directory. Files that do not have a valid parent directory are considered to be orphan files and are moved to the lost+found directory.
- ACFS-07356: file is a symbolic link but has no storage for the target name \nfor file:\nstring
-
Cause: The indicated file was a symbolic link but did have a target. The target of a symbolic link must have storage.
- ACFS-07360: deleting file due to invalid _attributes: string\nfile:\nstring
-
Cause: The _attributes property of the indicated file was invalid. The file must be deleted in order to preserve the integrity of the file system.
- ACFS-07361: truncating file 'string' to number bytes\nfor file:\nstring
-
Cause: The indicated file was truncated in order to preserve file system integrity.
- ACFS-07363: Volume_Disk_Header has invalid _VolFeatureFlag values.\n found: string\n, but expected to find: string or string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07364: file has incorrect values for Extent[number]\n found: _Length: string _PhysicalDiskOffset: string\n, but expected to find: _Length: string _PhysicalDiskOffset: string\nfor file:\nstring
-
Cause: One or more or the extent properties of the indicated file was incorrect.
- ACFS-07365: extent metadata structure has incorrect values for Extent[number]\n found: _FileOffset: string _Length: string _PhysicalDiskOffset: string \n, but expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string \nfor structure:\nstring
-
Cause: One or more properties of the indicated extent metadata structure was incorrect.
- ACFS-07366: directory has incorrect _attributes value\n found: string\n, but expected to find: string\nfor file:\nstring
-
Cause: The _attributes property of the indicated directory file was incorrect.
- ACFS-07367: Volume_Disk_Header has invalid _VolStateFlag values for accelerator volume: string\n found: string,\n but expected to find: string \nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07369: directory has invalid _FileSize value\n found: number minimum: number\nfor file:\nstring
-
Cause: The _FileSize property of the indicated directory file was incorrect.
- ACFS-07370: directory has invalid _FileSize: string _AllocationSize: string values\nfor file:\nstring
-
Cause: The _FileSize and _AllocationSize properties of the indicated directory file were incorrect.
- ACFS-07374: cannot access directory _Private structure for block number at disk offset: string\nfor file:\nstring
-
Cause: An attempt to access the indicated directory _Private metadata structure failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07375: directory _Private structure at disk offset: string contains invalid data\nfor file:\nstring
-
Cause: The _Private structure of the indicated directory file contained invalid data. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07376: directory _Private structure has incorrect header type at disk offset: string, this file may not be a directory\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The indicated file did not contain a _Private directory metadata structure as required for directory files. It appeared that the file was incorrectly identified as being a directory.
- ACFS-07377: directory has invalid node list\nfor file:\nstring
-
Cause: The node list of the indicated directory file was invalid. There are three possible causes: 1. One or more of the file's directory structures had an invalid structure header. 2. The _next_dirnode property of one or more of the file's directory structures was incorrect. 3. The _first_dirnode property of the _Private directory structure was incorrect.
- ACFS-07378: directory _Private structure has incorrect _last_dirnode value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _last_dirnode property of the indicated _Private directory structure was incorrect.
- ACFS-07379: directory has invalid free block list\nfor file:\nstring
-
Cause: The free block list of the indicated directory file was invalid. There are three possible causes: 1. One or more of the file's directory structures had an invalid structure header. 2. The _next_free_dirnode property of one or more of the file's directory structures was incorrect. 3. The _dir_entry_free_list_head property of the _Private directory structure was incorrect.
- ACFS-07381: directory _Private structure has incorrect _dir_entry_free_list_tail value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _ dir_entry_free_list_tail property of the indicated _Private directory structure was incorrect.
- ACFS-07382: directory has invalid hash block free list; invalid reference for free hash block\n found: number maximum: number\nfor file:\nstring
-
Cause: The hash block free list of the indicated directory file was invalid. There are two possible causes: 1. The _hash_blk_free_list property of the _Private directory structure referenced a block that exceeded the directory's size. 2. The _next_free_blk property of a directory free block referenced a block that exceeded the directory's size.
- ACFS-07383: directory has invalid hash block free list\nfor file:\nstring
-
Cause: The free hash block list of the indicated directory file was invalid. There are three possible causes: 1. One or more of the file's directory structures had an invalid structure header. 2. The next_free_blk property of one or more of the file's directory structures was incorrect. 3. The hash_blk_free_list property of the _Private directory structure was incorrect.
- ACFS-07384: snapshot: string (identifier: number) has invalid _SnapIncarnationNumber\n found: 0, but expected to find: > 0\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07385: directory has orphan Directory_Node metadata structure for block number at disk offset: string\nfor file:\nstring
-
Cause: The indicated directory file had a Directory_Node metadata structure that was not found on any directory node list.
- ACFS-07386: directory has incorrect _FileSize value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _FileSize property of the indicated directory file was incorrect.
- ACFS-07388: directory contains invalid _Private structure for block number at disk offset: string\nfor file:\nstring
-
Cause: A _Private metadata structure of the indicated directory file was found in the wrong block. _Private metadata structures must be located at block one of a directory's metadata.
- ACFS-07389: directory has orphan free block number at disk offset: string\nfor file:\nstring
-
Cause: The indicated directory file had a free block that was not found on the directory's free list.
- ACFS-07391: directory has invalid metadata structure string type for block number at disk offset: string\nfor file:\nstring
-
Cause: The structure found at the block of the indicated directory file was not a valid directory metadata structure.
- ACFS-07392: Directory_Entry has incorrect or invalid _attributes value\n found: string\n, but expected to find: string\nfor file:\nstring
-
Cause: The _attributes property of the indicated Directory_Entry was incorrect.
- ACFS-07395: directory has incorrect or invalid _attributes values\n found: string\n, but expected to find: string\nfor file:\nstring
-
Cause: The _attributes property of the indicated directory file was incorrect.
- ACFS-07396: directory has incorrect Hash_Table data\nfor file:\nstring
-
Cause: The Hash_Table of the indicated directory file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07399: directory has incorrect _LinkCount value\n found: number, but expected to find: number\nfor file:\nstring
-
Cause: The _LinkCount property of the indicated directory file was incorrect.
- ACFS-07400: mismatch between _NOLSTXPTR feature and _NOUPHDRPTR feature\n _NOLSTXPTR: string _NOUPHDRPTR: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07402: Deferred_Delete_Storage_List structure has invalid delete list pointers: _PrevDeferredListLink: string _NextDeferredListLink: string\nfor structure:\nstring
-
Cause: The _PrevDeferredListLink or _NextDeferredListLink property of of the indicated structure were incorrect. Both values must be zero or non-zero.
- ACFS-07407: Snap_Map_Header contains invalid _SnapCreatePending field\nfound: 0, but expected to find: > 0\nfor structure:\nstring
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07408: Snap_Map_Header contains invalid _SnapDeletePending field\nfound: 0, but expected to find: > 0\nfor structure:\nstring
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07411: snapshot metadata checking will be limited due to an error reading snapshot metadata
-
Cause: An attempt to read snapshot metadata failed. Snapshot validation was limited since not all snapshot metadata was not available.
- ACFS-07412: Accelerator Volume_Disk_Header has invalid _VolSignature value\n found: 'string'\n, expected: string\nfor structure: \nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07413: unable to create internal structure needed for processing
-
Cause: Refer to the accompanying message(s) for more information on the problem.
- ACFS-07414: snapshot: string (identifier: number) has invalid snap_map_tuples for file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07415: invalid snap_map_tuple: ( string, string ) for disk offset: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07416: file has invalid _FileSize value\n found: string minimum: string\nfor file:\nstring
-
Cause: The _FileSize property of the indicated file was invalid.
- ACFS-07417: Snap_Map_Header structure has invalid _snap_incarnation values; _SnapHighestActiveIncarnNumber: number must be less than _SnapNextIncarnationNumber: number\nfor structure:\nstring
-
Cause: One or both of the _SnapHighestActiveIncarnNumber and _SnapNextIncarnationNumber properties of the indicated Snap_Map_Header metadata structure was incorrect.
- ACFS-07418: Snap_Map_Header structure has invalid _SnapCreatePending value\n found: number, but expected to find: number or < number\nfor structure:\nstring
-
Cause: The _SnapCreatePending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapCreatePending value must be zero or less than the value indicated in the message.
- ACFS-07419: Snap_Map_Header structure has invalid _SnapDeletePending value\n found: number, but expected to find: number or < number\nfor structure:\nstring
-
Cause: The _SnapDeletePending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapDeletePending value must be zero or less than the value indicated in the message.
- ACFS-07420: found partially created snapshot for snapshot: 'string'
-
Cause: Initialization of the indicated snapshot did not complete. There are two possible causes: 1. The volume went offline while the snapshot was being created. 2. The process creating the snapshot was unexpectedly terminated do to a shutdown of the system.
- ACFS-07421: found partially deleted snapshot
-
Cause: A snapshot was not completely deleted. There are several possible causes: 1. The volume was unmounted before the asynchronous phase of snapshot deletion had completed. 2. The volume went offline while the snapshot was being deleted. 3. The process deleting the snapshot was unexpectedly terminated do to a shutdown of the system.
- ACFS-07423: snapshot 'string' has invalid file identifier\n found: string maximum: string\nfor structure:\nstring
-
Cause: The file identifier property of the indicated snapshot was invalid. Its value exceeded the maximum value for the file system.
- ACFS-07424: snapshot 'string' has invalid _SnapIncarnationNumber value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _SnapIncarnationNumber property of the indicated snapshot was invalid.
- ACFS-07425: snapshot (_snapid value: string) has invalid name: 'string'\nfor structure:\nstring
-
Cause: The name of indicated snapshot contained invalid characters.
- ACFS-07426: snapshot 'string' has invalid _SnapVisibility value\n found: number, but expected to find: number or number\nfor structure:\nstring
-
Cause: The _SnapVisibility property of the indicated snapshot was invalid.
- ACFS-07427: duplicate _SnapIncarnationNumber: number found for snapshots 'string' and 'string'
-
Cause: The _SnapIncarnationNumber property of the indicated snapshots had the same value. _SnapIncarnationNumber values must be unique across all snapshots.
- ACFS-07429: Snap_Map_Header structure has incorrect _SnapCount value\n found: number, but expected to find: number\nfor structure:\nstring
-
Cause: The _SnapCount property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapCount value did not match the number of valid snapshots found.
- ACFS-07430: cannot determine free space for volume associated with directory 'string'; attempting to continue with current directory 'string'
-
Cause: A temporary file is needed to store information during processing. This file was targeted for the indicated directory. The ACFS Checker was unable to determine the mount of space available for the volume associated with the directory. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07431: cannot determine free space for volume associated with current directory 'string'
-
Cause: A temporary file is needed to store information during processing. This file was targeted for the current directory. The ACFS Checker was unable to determine the mount of space available for the volume associated with the directory. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07432: insufficient space available to store temporary file in\ndirectory 'string' or directory 'string'\nspace needed: number bytes\n- unable to continue
-
Cause: A temporary file is needed to store information during processing but there was not enough space to store the file in either of the The size of this file is dependent on the size of the file system. indicated directories.
- ACFS-07435: invalid path name length for temporary file\n length: number minimum: number maximum: number
-
Cause: The path name for a temporary file does not exist or its length exceeds the maximum for this system. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07436: string has encountered an internal error: invalid parameter passed to fb_create
-
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error.
- ACFS-07437: string has encountered an internal error: invalid parameter passed to fb_ref\n disk offset: string size: string fbSize: string fbCacheSize: string
-
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error.
- ACFS-07438: file has storage allocated to it that is also allocated to another file\nfor file:\nstring
-
Cause: Storage allocated to the indicated file was also allocated to at least one other file. Storage can only be allocated to a single file. Storage can never be allocated to multiple files.
- ACFS-07439: Snapshot_BitMap conflicts with the Global_BitMap for disk offset: string
-
Cause: One or more snapshot bitmaps claimed storage that was also claimed by the Global_BitMap.
- ACFS-07440: Snapshot_BitMap has bit set for non-existing snapshot for disk offset: string
-
Cause: One or more bitmaps reserved for unused snapshot incorrectly claimed storage. Bitmaps for snapshots that are not in use cannot claim any storage.
- ACFS-07441: Snapshot_BitMap has bits set for storage at disk offset: string that is beyond the file system size
-
Cause: One or more snapshot bitmaps incorrectly claimed storage that exceeded the size of the file system.
- ACFS-07443: Global_BitMap has invalid value for number of bits set\n found: string maximum: string\nfor file:\nstring
-
Cause: The Global_BitMap property that indicates the number of bits set exceeded the size of the bitmap.
- ACFS-07444: Global_BitMap has invalid value for number of bits set.\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The Global_BitMap property that indicates the number of bits set did not match the amount of storage allocated to all valid files.
- ACFS-07445: Global_BitMap has invalid value for next offset to search\n found: string maximum: string\nfor file:\nstring
-
Cause: The Global_BitMap property that indicates the next offset to search for available bits to allocate exceeded the size of the bitmap.
- ACFS-07446: mismatch between temporary Global_BitMap and on-disk Global_BitMap
-
Cause: The temporary Global_BitMap that was populated by traversing all valid file system data did not match the on-disk copy of the Global_BitMap.
- ACFS-07447: invalid snap_map_tuple for disk offset: string\n found: ( 0, 0 ), but expected non-zero values\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07448: invalid snap_map_tuple for disk offset: string\n found: ( 0, 0 ), but expected non-zero values
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07449: snapshot 'string' storage bitmap is incorrectly set for disk offset: string
-
Cause: The bitmap of the indicated snapshot claimed storage that was allocated to allocated file. Storage can only be allocated to a single file. Storage can never be allocated to multiple files.
- ACFS-07450: snapshot 'string' storage bitmap is not set for disk offset: string
-
Cause: The bitmap of the indicated snapshot did not claim storage that was allocated to one of its files. A snapshot's bitmap must claim all storage allocated to its files.
- ACFS-07451: snapshot 'string' storage bitmap is incorrectly set for disk offset: string with no corresponding file data
-
Cause: The bitmap of the indicated snapshot claimed storage but the storage was not allocated to any file.
- ACFS-07452: unable to locate directory for snapshot 'string' (id: number)\n processing will continue for other snapshots
-
Cause: The directory of the indicated snapshot was not found. This snapshot could not be processed.
- ACFS-07453: Snap_Root_Directory file identifier for snapshot 'string' was incorrect\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The Snap_Root_Directory file identifier property of the indicated snapshot was incorrect.
- ACFS-07455: unable to open file: string
-
Cause: An attempt to open a file failed. Refer to the accompanying message(s) for more information on the error.
- ACFS-07456: Global_Metadata_Directory structure has incorrect _accelerator_GBM_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07458: The request to cancel string was incomplete because volume string was not accessible. The file system cannot be mounted in this state.\nRerun string once the volume is accessible to enable file system mounts.
-
Cause: The ACFS Checker/Fixer could not reset the volume to allow for file system mounts because the volume was not accessible. Refer to the accompanying message(s) for more information on the error.
- ACFS-07459: Volume_Label metadata structure has invalid _VolLabelLength value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _VolLabelLength property of the indicated Volume_Label metadata structure exceeded the maximum value.
- ACFS-07460: Volume_Label metadata structure has invalid _VolIDLength value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _VolIDLength property of the indicated Volume_Label metadata structure exceeded the maximum value.
- ACFS-07461: Volume_Label metadata structure has invalid _ClusterNameLength value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _ClusterNameLength property of the indicated Volume_Label metadata structure exceeded the maximum value.
- ACFS-07462: file has incorrect or invalid _attributes values\n found: string\n valid values: string\nfor file:\nstring
-
Cause: The _attributes property of the indicated file contained invalid and/or incorrect values.
- ACFS-07463: Global_Metadata_Directory structure has incorrect _accelerator_snap_map_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07464: file has invalid _attributes value\n found: string\nfor file:\nstring
-
Cause: The _attributes property of the indicated file contained invalid values. These values are not supported on Windows systems.
- ACFS-07465: file has _attributes set that are mutually exclusive\n found: string\nfor file:\nstring
-
Cause: The _attributes property of the indicated file describe more than one type of file. File types are mutually exclusive.
- ACFS-07466: file has no _attributes value\nfor file:\nstring
-
Cause: The _attributes property of the indicated file did not describe a file type. The _attributes property must describe a valid file type.
- ACFS-07467: metadata structure has a non-zero value for field: string\nfor structure:\nstring
-
Cause: The indicated ACFS metadata structure had a reserved or unused field that contained a non-zero value. The field was overwritten or was not initialized correctly.
- ACFS-07468: file has invalid _SynchFlags value\n found: string\n expected: string\nfor file:\nstring
-
Cause: The _SynchFlags property of the indicated file contained values that were not within the range of valid values.
- ACFS-07469: file cannot be modified; _SynchFlag value:\n found: string\nfor file:\nstring
-
Cause: The indicated file had an internal inconsistency that prevented it from being modified.
- ACFS-07470: file cannot be accessed; _SynchFlag value:\n found: string\nfor file:\nstring
-
Cause: The indicated file had an internal inconsistency that prevented it from being accessed.
- ACFS-07471: file incorrectly marked for deletion with _SynchFlag value:\n found: string\nfor file:\nstring
-
Cause: The _SynchFlag property of the indicated file incorrectly identified the file as marked for deletion while it was still part of a valid directory.
- ACFS-07474: invalid program name\n found: string, but expected to find: string or string
-
Cause: The ACFS Checker/Fixer or Debug utility has been renamed to a value that is not recognized.
- ACFS-07475: attempting to continue with standard memory heap
-
Cause: The file system checker was unable to use the more efficient memory allocation facility, so the file system checker attempted to continue with the standard memory allocation facility.
- ACFS-07481: An I/O error occurred while reading ACFS metadata, some snapshot metadata checks will not be performed.
-
Cause: The I/O error prevented full snapshot checking because required ACFS metadata was not available. Refer to the accompanying message(s) for more information on the error.
- ACFS-07482: snapshot string with _snapid value: string has invalid parent snapshot with _snapid value: string
-
Cause: The indicated snapshot does not have a valid parent.
- ACFS-07483: snapshot with _snapid value: string has invalid ancestor snapshot
-
Cause: The indicated snapshot has an invalid ancestor snapshot.
- ACFS-07484: valid ACFS volume path name required
-
Cause: A valid volume path name was not entered.
- ACFS-07485: unable to determine temporary directory
-
Cause: An attempt to determine the system's temporary directory failed. For UNIX systems this directory is either "/usr/tmp" or "/tmp". For Windows systems this directory is the system's temporary folder. Refer to the accompanying message(s) for more information on the error.
- ACFS-07486: unable to determine current directory
-
Cause: An attempt to determine the current directory failed. Refer to the accompanying message(s) for more information on the error.
- ACFS-07487: unable to open volume: string
-
Cause: An attempt to open a volume failed. Refer to the accompanying message(s) for more information on the error.
- ACFS-07488: This volume is now in a mountable state. \nThe file system was not checked before changing the volume's state. \nUse of this file system may encounter serious errors since it has \nnot been checked.
-
Cause: The volume was forced into a mountable state without checking the integrity of the file system. The file system may contain incorrect or invalid data.
- ACFS-07489: maximum number of passes: number exceeded, program terminating
-
Cause: There are two possible causes: 1. There is a problem with the file system that the ACFS Fixer cannot repair. 2. The ACFS Fixer has encountered an internal problem.
- ACFS-07490: Metadata structure has non-zero values for various fields\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07498: extent[number] has invalid _Length value\n found: string, but expected to find multiple of: string\nfor file:\nstring
-
Cause: The _Length property of an extent structure of the indicated file was invalid. _Length values must be a multiple of the file system allocation unit size.
- ACFS-07499: extent[number] has invalid _Length value\n found: string, but expected to find multiple of: string\nfor structure:\nstring
-
Cause: The _Length property of an extent of the indicated extent structure was invalid. _Length values must be a multiple of the file system allocation unit size.
- ACFS-07500: extent[number] has invalid _FileOffset value\n found: string, but expected to find multiple of: string\nfor file:\nstring
-
Cause: The _FileOffset property of an extent structure of the indicated file was invalid. _FileOffset values must be a multiple of the file system allocation unit size.
- ACFS-07501: extent[number] has invalid _FileOffset value\n found: string, but expected to find multiple of: string\nfor structure:\nstring
-
Cause: The _FileOffset property of an extent of the indicated extent structure was invalid. _FileOffset values must be a multiple of the file system allocation unit size.
- ACFS-07502: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find multiple of: string\nfor file:\nstring
-
Cause: The _PhysicalDiskOffset property of an extent structure of the indicated file was invalid. _PhysicalDiskOffset values must be a multiple of the file system allocation unit size.
- ACFS-07503: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find multiple of: string\nfor structure:\nstring
-
Cause: The _PhysicalDiskOffset property of an extent of the indicated extent structure was invalid. _PhysicalDiskOffset values must be a multiple of the file system allocation unit size.
- ACFS-07504: snapshot with _snapid value: string has invalid ancestor snapshot (_cycle)
-
Cause: The indicated snapshot has an invalid ancestor snapshot.
- ACFS-07505: metadata structure read failed at disk offset: string for structure: string
-
Cause: An attempt to read the indicated metadata structure at the described disk offset failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07519: Snap_Map_Header structure has invalid _SnapConvertPending value\n found: number, but expected to find: less than number\nfor structure:\nstring
-
Cause: The _SnapConvertPending property of the indicated Snap_Map_Header metadata structure was incorrect. The _SnapConvertPending value must be zero or less than the value indicated in the message.
- ACFS-07520: Snap_Map_Info structure has invalid _SnapInfoFlags value\n found: string\nfor structure:\nstring
-
Cause: The _SnapInfoFlags property of the indicated Snap_Map_Info metadata structure was invalid.
- ACFS-07521: Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n found: string\nfor structure:\nstring
-
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.
- ACFS-07522: snapshot: string (identifier: number) has invalid _SnapParentId: number, parent snapshot does not exist
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07523: snapshot: string (identifier: number) has invalid _SnapParentId value\n found: number, but expected to find: 0\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07524: snapshot: string (identifier: number) has invalid _SnapAncestorIncarn value\n found: number, but expected to find: 0\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07525: snapshot: string (identifier: number) has invalid _SnapAncestorIncarn value\n found: number, must be less than _SnapIncarnationNumber: number\nfor structure:\nstring
-
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.
- ACFS-07526: Volume_Disk_Header has invalid _VolStateFlag values.\n found: string,\n but expected to find: string \nfor structure:\nstring
-
Cause: The _VolStateFlag property of the indicated Volume_Disk_Header contained one or more invalid values.
- ACFS-07527: Volume Disk Header has invalid VolFeatureFlag values \n found: string \nstring but expected to find: string \nstringfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07528: found partially created snapshot: string (identifier: number)
-
Cause: Initialization of the indicated snapshot did not complete. There are two possible causes: 1. The volume went offline while the snapshot was being created. 2. The process creating the snapshot was unexpectedly terminated do to a shutdown of the system.
- ACFS-07529: found partially deleted snapshot: string (identifier: number)
-
Cause: A snapshot was not completely deleted. There are several possible causes: 1. The volume was unmounted before the asynchronous phase of snapshot deletion had completed. 2. The volume went offline while the snapshot was being deleted. 3. The process deleting the snapshot was unexpectedly terminated do to a shutdown of the system.
- ACFS-07530: snapshot: string (identifier: number) has invalid file identifier\n found: string maximum: string\nfor structure:\nstring
-
Cause: The file identifier property of the indicated snapshot was invalid. Its value exceeded the maximum value for the file system.
- ACFS-07531: snapshot: (identifier: number) has invalid name: 'string'\nfor structure:\nstring
-
Cause: The name of indicated snapshot contained invalid characters.
- ACFS-07532: snapshot: string (identifier: number) has invalid _SnapVisibility value found: number, but expected to find: number, number or number\for structure:\nstring
-
Cause: The _SnapVisibility property of the indicated snapshot was invalid.
- ACFS-07533: duplicate _SnapIncarnationNumber: number found for the following snapshots:\n
-
Cause: The _SnapIncarnationNumber property of the indicated snapshots had the same value. _SnapIncarnationNumber values must be unique.
- ACFS-07534: request for disk offset: string exceeds the size for this file system: string
-
Cause: A request was made for a disk offset that exceeded the size of the file system.
- ACFS-07536: snapshot: string (identifier: number) has invalid parent snapshot identifier: number, maximum: number\nstructure:\nstring
-
Cause: The indicated snapshot does not have a valid parent.
- ACFS-07537: snapshot: string (identifier: number) has invalid ancestor snapshot: string (identifier: number)
-
Cause: The indicated snapshot has an invalid ancestor snapshot.
- ACFS-07538: snapshot: string (identifier: number) has invalid ancestor snapshot (_cycle)
-
Cause: The indicated snapshot has an invalid ancestor snapshot.
- ACFS-07539: Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n found: number\nfor structure:\nstring
-
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata structure was invalid.
- ACFS-07540: deleting snapshot: string (identifier: number) to maintain file system integrity
-
Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the file system. Refer to the corresponding message(s) for more information on the problem(s) associated with the snapshot.
- ACFS-07541: Snap_Map_header has invalid value for SnapMapFlags\n found: string\n string\n but expected to find: string\n string\nfor structure: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07542: Snapshot string (identifier number) has invalid _SnapStorageCount value found: number, but expected to find: number, for structure: \nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07543: snapshot string (identifier number) has invalid _SnapStorageCount value found: number, but it should not be greater than the total amount of the storage all snapshots have number, for structure: \nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07544: Compressed file:\nstring\n has an incorrect value number\nfor the _compression_unit_size_index property of the _FileEntry\nand cannot be used.
-
Cause: The _FileEntry indicated that compression was enabled but the _compression_unit_size_index property was not set to a valid value.
- ACFS-07545: Compressed file:\nstring\nhas an incorrect value number\nfor the compression algorithm and cannot be used.
-
Cause: The file entry indicated that compression was enabled but the compression algorithm was not set to a valid value.
- ACFS-07546: extent[number] has invalid _FileOffset value\n found: string, but expected to find multiple of: string\nfor compressed file:\nstring
-
Cause: The _FileOffset property of an extent of the indicated extent structure was invalid. _FileOffset values must be a multiple of the file's compression unit size, for compressed files.
- ACFS-07547: Compressed file has extents that overlap.\n_FileOffset: string and\n_FileOffset: string\nfor file:\nstring
-
Cause: Two file extents with the _FileOffset values shown, were found to use the same disk storage incorrectly.
- ACFS-07548: Compressed file extent is in an inconsistent state.\n_FileOffset: string\nfor file:\nstring
-
Cause: A file extent with the _FileOffset value shown was found to be using disk storage incorrectly.
- ACFS-07549: File has _attributes value indicating compression but this is inconsistent with the volume header.\n found: string\nFile:\nstring\nshould not be compressed
-
Cause: The volume header indicated that compression was never enabled but a file entry indicating compression was found.
- ACFS-07550: The default compression algorithm value string for the volume is incorrect.
-
Cause: The volume header indicated that compression was enabled but the default compression algorithm was not set as expected.
- ACFS-07551: The Volume_Disk_Header indicates that this file system has an accelerator volume, but the Global_Metadata_Directory structure does not contain an accelerator volume name.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07552: Global_Metadata_Directory structure has no value for _accelerator_device, but contains a non-zero value for _accelerator_GBM_fileid or _accelerator_snap_map_fileid\n _accelerator_GBM_fileid: string\n _accelerator_snap_map_fileid: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07554: unable to close volume: string
-
Cause: An attempt to close a volume failed. Refer to the accompanying messages for more information on the error.
- ACFS-07555: unable to close file: string
-
Cause: An attempt to close a file failed. Refer to the accompanying messages for more information on the error.
- ACFS-07556: I/O request for (disk offset + size): string exceeds accelerator volume size: string\nfor structure:\nstring
-
Cause: An I/O request was made for data that exceeded the size of the accelerator volume.
- ACFS-07557: found accelerator volume: string associated with this file system,\nbut accelerator volumes are not supported on this operating system: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07558: unable to process SnapMap metadata on the accelerator volume due to a problem with the primary volume's SnapMap metadata
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07559: The _FileEntry metadata structure for the accelerator volume storage SnapMap is invalid.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07560: \nextent[number] is not in use but it contains non-zero values:\n _FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\n _SnapIncarnationNumber: number\n _VolId: string\n _ExtFlags: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07563: volume: string had an unsupported logical sector size\n found: number, but only number or number are supported\n
-
Cause: File system check has identified the metadata inconsistency reported in the message.
- ACFS-07564: Snap_Clone_ID structure has an invalid Version value\n found: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07565: Snap_Clone_ID structure has an invalid Flags value\n found: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07566: extent[number] at _FileOffset value string has invalid _PhysicalDiskOffset value \n found: string, but expected to find multiple of: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07567: extent[number] at _FileOffset value string has invalid _PhysicalDiskOffset value \n found: string, but expected to find multiple of: string\nfor compressed file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07568: Volume_Disk_Header has incorrect metadata size value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The MetadataSize property of the indicated Volume_Disk_Header did not match supported values.
- ACFS-07570: snap_map_tuple for disk offset: string conflicts with primary file system\n found: ( string, string )\n expected: ( 0, 0 )
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07571: snap_map_tuple for disk offset: string not set in Global BitMap\n snap_map_tuple: ( string, string )
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07572: invalid snap_map_tuple found for for disk offset string,\nfirst value must be less than or equal to second value\n snap_map_tuple: ( string, string )
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07573: orphan snap_map_tuple found for for disk offset string\n snap_map_tuple: ( string, string )
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07574: snapshot marked for delete: string (identifier: number) was still present
-
Cause: File system checking has identified the metadata inconsistency reported in the message. A snapshot was marked for delete, but did not get deleted due to open files in the snapshot. There are two possible causes why the snapshot was not deleted. 1. The volume went offline while there were still open files in the snapshot. 2. The system was unexpectedly shutdown while there were still open files in the snapshot.
- ACFS-07575: command takes no arguments
-
Cause: The command entered does not take any arguments.
- ACFS-07576: Compressed file:\nstring\nhas an incorrect value number\nfor the _range_size value and cannot be used.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07577: extent structure has incorrect _NextDataExtent value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07578: extent structure has incorrect _NextDataExtentVolId value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07579: HEADER extent structure found in _NextDataExtent list for file that does not support range locking\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07580: Remap_Bitmap has an invalid volume offset beyond the current volume size (EAOffset)\n found: string, but expected: string\nfor structure: \n string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07581: disk storage used string greater than sum of extents allocation size string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07582: file _DiskUsage value not equal to disk storage used by DATA extents\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07583: invalid file entry number found in deferred release file at offset: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07584: found a number in the Remap_Bitmap for offset string where a number was expected
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07585: unable to set File_Entry_Table context
-
Cause: The ACFS Debug utility was not able to set the File_Entry_Table context. Lookups by file identifier were disabled. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07586: Do you want to continue [y|n] ?
-
Cause: The ACFS Checker/Fixer or Debug utility detected a situation that could leave the file system in an inconsistent or unusable state. Refer to the corresponding error message for more information.
- ACFS-07588: Metadata read of size string bytes failed at disk offset: string.\n Can not read beyond end of primary volume, size: string.
-
Cause: An attempt to read metadata failed because the data requested was beyond the size of the primary volume for this file system.
- ACFS-07590: Metadata write of size string bytes failed at disk offset: string.\n Can not write beyond end of primary volume, size: string.
-
Cause: An attempt to write metadata failed because the write location was beyond the size of size of the primary volume for this file system.
- ACFS-07592: metadata structure has incorrect header for:\nstring
-
Cause: One or more properties of the header of the indicated metadata structure contained invalid or incorrect values. Refer to accompanying messages for more information on the error.
- ACFS-07598: Metadata read of size string bytes failed at disk offset: string.\n Can not read beyond end of accelerator volume, size: string.
-
Cause: An attempt to read metadata failed because the data requested was beyond the size of the accelerator volume for this file system.
- ACFS-07600: Metadata write of size string bytes failed at disk offset: string.\n Can not write beyond end of accelerator volume, size: string.
-
Cause: An attempt to write metadata failed because the write location was beyond the size of size of the accelerator volume for this file system.
- ACFS-07601: unable to determine size of file: string
-
Cause: An attempt to determine the size of the indicated file failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07602: failed to create temporary paging file 'string'
-
Cause: An attempt to create the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07603: write failed at position: string for temporary paging file 'string'
-
Cause: An attempt to write to the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07604: seek failed at position: string for temporary paging file 'string'
-
Cause: An attempt to seek within the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07606: read failed at position: string for temporary paging file 'string'
-
Cause: An attempt to read the indicated temporary paging file failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07607: metadata read failed at disk offset: string\n bytes requested: number bytes returned: number
-
Cause: An attempt to read metadata at the indicated offset was incomplete. The amount of data read did not match the amount requested. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07608: found number incorrectly set bits in the Remap_Bitmap
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07609: found number incorrectly unset bits in the Remap_Bitmap
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07610: Volume_Disk_Header has incorrect _VolVolumeSize value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header metadata structure was incorrect.
- ACFS-07611: Global_BitMap has bits incorrectly set for storage beyond the file system size\nfor file:\nstring
-
Cause: The Global_BitMap had bits set in an area reserved for future expansion. All of these storage bits must be zero. There is no valid storage associated with these bits.
- ACFS-07612: file has invalid _NextFreeExtent value:\n found: number minimum: number\nfor file:\nstring
-
Cause: The _NextFreeExtent property of the indicated file was incorrect.
- ACFS-07613: file has invalid _NextFreeExtent value:\n found: number maximum: number\nfor file:\nstring
-
Cause: The _NextFreeExtent property of the indicated file was incorrect.
- ACFS-07614: Global_BitMap's first extent is not located at the expected disk offset\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The first extent of the indicated Global_BitMap was not located at the correct disk offset. The Global_BitMap's first extent must be located at the disk offset described in the message.
- ACFS-07615: Global_BitMap file has extents that overlap\n Extent[number] _Length: string _PhysicalDiskOffset: string\n Extent[number] _Length: string _PhysicalDiskOffset: string\nfor file:\nstring
-
Cause: The extents of the indicated Global_BitMap mapped some or all of the same storage. All extents within a file must map storage that is mutually exclusive.
- ACFS-07616: string has encountered an internal error: could not post error to ACFS Fixer
-
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an unexpected, internal error. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07619: truncating file from number bytes to number bytes to ensure metadata consistency; file content following file offset: number has been lost\nfor file:\nstring
-
Cause: The ACFS Fixer was not able to fully repair the indicated file due to an inconsistency within its metadata. The file had to be truncated to maintain the integrity of the file system.
- ACFS-07622: resetting _security_descriptor to administrator default value for:\nfor file:\nstring
-
Cause: The _security_descriptor the indicated file was invalid or incorrect. It was reset to the default administrator value.
- ACFS-07623: unable to repair problem with file _attributes; deleting file to maintain file system integrity\nfor file:\nstring
-
Cause: The ACFS Fixer was not able to resolve a problem with the _attributes property of the indicated file. The file had to be deleted to maintain the integrity of the file system.
- ACFS-07624: file cannot be repaired; deleting file to maintain file system integrity\nfor file:\nstring
-
Cause: The ACFS Fixer was not able to repair a problem with the indicated file. The file had to be deleted to maintain file system integrity.
- ACFS-07625: failed to create system directory\nfor file:\nstring
-
Cause: The ACFS Fixer was not able to create a directory for the indicated internal system file. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07628: invalid snapshot name 'string' entered
-
Cause: The snapshot entered did not exist.
- ACFS-07629: numeric argument too large: number
-
Cause: The numeric value entered as an argument exceeded the largest possible value for this type of argument.
- ACFS-07630: file has invalid _oracle_file_type value\n found: number\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07631: extent[number] has invalid _Length value\n found: string, but expected to find multiple of: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07632: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find multiple of: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07633: extent[number] has invalid _Length value\n found: string, but expected to find multiple of: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07634: extent[number] has invalid _PhysicalDiskOffset value\n found: string, but expected to find multiple of: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07635: extent[number] has invalid _Length value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07636: extent[number] has invalid _Length value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07637: extent[number] has invalid _Length value\n found: string, but expected to find less than: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07638: extent[number] has invalid _Length value\n found: string, but expected to find less than: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07641: Remap_Bitmap has number bits set without corresponding offsets
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07642: Storage referenced directly at disk offset: string is also referenced via remapping from disk offset: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07647: local extent limit reached for extending files; indirect extents not supported for extending files\nfor file:\nstring
-
Cause: The ACFS Fixer was not able to create an indirect extent to extend the indicated file.
- ACFS-07648: cannot set Global_BitMap bits for offset: string for number bytes\nfor file:\nstring
-
Cause: The ACFS Fixer was unable to set the range of bits described in the message. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07649: deleting snapshot to maintain file system integrity
-
Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the file system. Refer to the corresponding message(s) for more information on the problem(s) associated with the snapshot.
- ACFS-07650: unable to repair _VolStateFlag value in Volume_Disk_Header
-
Cause: The ACFS Fixer was unable to update the _VolStateFlag in the Volume_Disk_Header. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07652: Volume_Disk_Header has invalid _VolOSCreatedOn value\n found: number, but expected to find: 1 (Windows_XP), 2 (Linux), 3 (Solaris), or 4 (AIX)\nfor structure:\nstring
-
Cause: The _VolOSCreatedOn property of the indicated Volume_Disk_Header was incorrect. Its value must be one of the values listed in the message.
- ACFS-07653: Security_Metadata file _Private structure has invalid _freeDataListTail value\n found: 0, but expected to find: > 0\nfor structure:\nstring
-
Cause: The _freeDataListTail property of the indicated Security_Metadata _Private metadata structure was invalid. The value must be greater than zero.
- ACFS-07655: This file system had been removed. It has now been restored.
-
Cause: This file system was removed via the acfsutil rmfs utility. It has now been restored by the ACFS Fixer.
- ACFS-07656: unable to continue
-
Cause: The ACFS Checker/Fixer or Debug utility has encountered a fatal error and cannot continue. Refer to the accompanying message(s) for more information on the error.
- ACFS-07658: Ensure that volume string is not mounted on this node. \nNote that data displayed may not be current if volume string is mounted on any other node due to file system caching
-
Cause: The volume cannot be mounted on this node while running the acfsdbg utility in read-only mode. This restriction is limited to Windows systems. The acfsdbg utility reads metadata directly from disk and data may not be current if the file system is mount on any other nodes due file system caching.
- ACFS-07659: command is disabled in read-only mode
-
Cause: The command entered attempted to modify file system metadata while running in read-only mode. Modifications to file system metadata are not allowed when running the ACFS Debug utility in read-only mode.
- ACFS-07660: unable to modify metadata for volume string; volume is not open
-
Cause: An attempt to modify metadata failed because the volume was not open. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07661: metadata lookup by file identifier is disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap snapshot name' to set the context
-
Cause: The acfsdbg utility could not process the request because there was no File_Entry_Table context. The acfsdbg utility requires a valid File_Entry_Table context for lookups by file identifier since the same file identifier may appear in multiple snapshots.
- ACFS-07662: unable to set snapshot context due to Snap_Map file metadata inconsistency
-
Cause: An attempt to set the metadata lookup context to a snapshot failed because there was a problem accessing the SnapMap metadata. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07663: disk offset request: string is not aligned on a sector: number bytes; results may be inconsistent
-
Cause: The disk offset entered was not sector aligned. All ACFS metadata structures are sector aligned.
- ACFS-07664: read failed for metadata structure at disk offset: string for number bytes
-
Cause: An attempt to read a metadata structure at the indicted disk offset failed. Refer to accompanying message(s) for more information on the problem.
- ACFS-07666: unrecognized metadata found at disk offset: string
-
Cause: The data found at the indicated disk offset did not contain a valid ACFS metadata structure type. There are two possible causes: 1. The data at the disk offset was not an ACFS metadata structure. 2. The metadata structure at the disk offset was in an inconsistent state.
- ACFS-07667: request for file identifier: string exceeds the maximum value for this file system: string
-
Cause: A request was made for a file identifier that exceeded the maximum for the file system.
- ACFS-07669: metadata lookup by file identifier is disabled due to File_Entry_Table metadata inconsistency
-
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the accompanying message.
- ACFS-07682: file system check has been cancelled
-
Cause: File system checking was terminated because a signal was received, such as Control-C.
- ACFS-07683: found incorrect size string for the Remap_Bitmap
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07685: string is unable to detect the ACFS driver on this system. \nProceeding could leave the file system in an inconsistent and possibly \nunusable state if the file system is mounted or being fixed on another system.
-
Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the ACFS driver that failed. It appeared that the ACFS driver was not loaded on this system.
- ACFS-07690: data displayed may not be current if volume string is mounted on any node due to file system caching
-
Cause: The acfsdbg utility reads metadata directly from disk. Metadata updates to disk may be delayed due standard file system caching.
- ACFS-07691: command entered: 'string' is invalid or not unique
-
Cause: There are two possible causes: 1. The command entered was not recognized by the acfsdbg utility. 2. A partial command name was entered and there was more than one command that matched the characters entered.
- ACFS-07692: cannot convert disk offset as specified: string
-
Cause: The format entered for the disk offset was invalid.
- ACFS-07693: Volume_Disk_Header has invalid _VolVolumeSize value\n found: string must be aligned on a number byte boundary\nfor structure:\nstring
-
Cause: The _VolVolumeSize property of the Volume_Disk_Header was invalid. Its value must be aligned on the byte boundary described in the message.
- ACFS-07694: too many arguments for string
-
Cause: Too many arguments were supplied for the string option. The string option takes one argument.
- ACFS-07695: The ACFS driver should be loaded on all nodes for a safe check of this file system.
-
Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the ACFS driver that failed. It appeared that the ACFS driver was not loaded on this system.
- ACFS-07696: The file system on volume string is currently in the string state. This state indicates that a file system check is currently in progress.
-
Cause: There are two possible causes: 1. The file system on this volume was being checked on this system or another system in the cluster. 2. The ACFS Checker/Fixer was unexpectedly terminated leaving the file system state incorrectly set.
- ACFS-07697: unable to determine program name
-
Cause: The ACFS Checker/Fixer or Debug utility was invoked in a non-standard way such that the program name could not be determined.
- ACFS-07698: orphan directory found for file identifier: string at disk offset: string
-
Cause: No parent directory entry was found for the indicated directory file. 1. The directory file had no corresponding parent directory entry. 2. The directory file had a parent directory entry, but there was a problem with corresponding parent directory file.
- ACFS-07701: There are metadata transaction log file(s) that have not been processed. Failure \nto process these transaction logs may result in metadata inconsistencies. \nDo you want to process the transaction log(s)? [y|n]
-
Cause: Transaction Log files contain updates to the file system's metadata. The ACFS Checker found at least one transaction log that was not completely processed. This indicates that metadata updates were not completed which could leave the file system in an inconsistent state.
- ACFS-07708: unable to read File_Entry_Table entry: string at disk offset: string
-
Cause: An attempt to read the File_Entry_Table for the indicated entry failed. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07709: orphan file (file identifier: string, disk offset: string) marked for deletion not on delete list
-
Cause: The indicated file was marked for deletion but it was not found on any of the delete file lists.
- ACFS-07710: orphan file found for file identifier: string at disk offset: string
-
Cause: No directory entry was found for the indicated file. There are two possible causes: 1. The file had no corresponding directory entry. 2. The file had a directory entry, but there was a problem with corresponding directory file.
- ACFS-07711: orphan metadata structure (type: string) found for file identifier: string at disk offset: string
-
Cause: The indicated metadata structure was found but had no corresponding parent metadata structure.
- ACFS-07720: new allocation size is invalid\n found: number, but expected to find multiple of: number\nfor file:\nstring
-
Cause: The new allocation size property of the indicated file was incorrect. Its value must be a multiple of the file system allocation unit size.
- ACFS-07721: file has invalid _NextFreeExtent value\n found: number maximum: number\nfor file:\nstring
-
Cause: The _NextFreeExtent property of the indicated file was incorrect.
- ACFS-07722: file has invalid _NextFreeExtent value:\n found: number minimum: 1\nfor file:\nstring
-
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
- ACFS-07723: could not clear temporary Global_BitMap bits at offset: string for number bits
-
Cause: The ACFS Fixer was unable to free the indicated storage on the temporary Global_BitMap.
- ACFS-07724: unable to set temporary Global_BitMap bits at offset: string for number bits
-
Cause: The ACFS Fixer was unable to reserve the indicated storage on the temporary Global_BitMap.
- ACFS-07725: unable to allocate storage; file system has no free space
-
Cause: The ACFS Fixer was unable to allocate storage because there was no free storage available.
- ACFS-07726: could not find sufficient free storage to rebuild Global_BitMap extent\n found: string requested: string\nfor file:\nstring
-
Cause: The ACFS Fixer could not find enough contiguous storage to rebuild the Global_BitMap file's extent map.
- ACFS-07727: could not rewrite Global_Bitmap data for file:\nstring
-
Cause: The ACFS Fixer could not update the file system's storage bitmap. Refer to the accompanying message(s) for more information on the problem.
- ACFS-07728: The Global_BitMap file has reached the maximum number of extents (number). The file system can no longer be expanded. Running string in fixer mode will attempt to consolidate the storage bitmap into fewer extents which would allow for file system expansion via the 'acfsutil size' command.
-
Cause: The ACFS Checker found the file system's storage bitmap was using its maximum number of extents.
- ACFS-07729: The Global_Bitmap file has been\n consolidated into number extents.\nThis may allow for file system expansion via the 'acfsutil size' command.
-
Cause: The Global_Bitmap file was using the maximum number of extents supported. The ACFS Fixer has consolidated the Global_Bitmap file into fewer extents thus allowing future file system growth using the 'acfsutil size' command if unused storage is available.
- ACFS-07733: directory _Private structure has invalid _first_dirnode value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _first_dirnode property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
- ACFS-07734: directory _Private structure has invalid _last_dirnode value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _last_dirnode property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
- ACFS-07735: directory _Private structure has invalid _hash_blk_free_list value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _hash_blk_free_list property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
- ACFS-07736: directory _Private structure has invalid _dir_entry_free_list_head value\n found: string maximum: string\nfor structure:\nstring
-
Cause: The _dir_entry_free_list_head property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
- ACFS-07737: directory _Private structure has invalid _dir_entry_free_list_tail value\n found: string maximum: string\nfor structure:\nstring
-
Cause: The _dir_entry_free_list_tail property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
- ACFS-07740: Could not consolidate the file system's temporary\n storage bitmap to less than number extents. Need\n at least number bytes free contiguous storage.
-
Cause: The file system's internal storage bitmap could not be consolidated to less than five extents because there was insufficient free contiguous storage.
- ACFS-07741: could not rebuild file system storage bitmap\n free contiguous bytes found: number\n contiguous bytes requested: number\nfor file: string
-
Cause: The ACFS Fixer could not find enough contiguous free storage to rebuild the file system's storage bitmap.
- ACFS-07742: _ustEAContainerEntry property has an invalid value\n found: number for structure:\nstring
-
Cause: The _ustEAContainerEntry property of the indicated _ustEAContainer structure was not within the range of valid offset values.
- ACFS-07743: _ustEAEntryHdrFlags property has an invalid value\n found: string for _ustEAContainerEntry at offset: number for structure:\nstring
-
Cause: The _ustEAEntryHdrFlags property of the indicated _ustEAContainer structure contained one or more invalid values.
- ACFS-07744: _ustEAEntryHdrNextFreeOffset property has an invalid value\n found: number, but expected to find: number for _ustEAContainerEntry at offset: number for structure:\nstring
-
Cause: The _ustEAEntryHdrNextFreeOffset property of the indicated _ustEAContainer structure was incorrect.
- ACFS-07745: _ustEAEntryHdrNameLen property has an invalid value\n found: number, but expected to find no greater than: number\n for _ustEAContainerEntry at offset: number for structure:\nstring
-
Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr property at the _ustEAContainerEntry offset for the indicated _ustEAContainer structure was invalid. Its value exceeded the maximum length for an extended attribute name or ACFS tag name.
- ACFS-07746: ACFS tag name contains invalid syntax\n found: string for _ustEAContainerEntry at offset: number for structure:\nstring
-
Cause: The _ustEAEntryName property of the indicated _ustEAContainerEntry property in the _ustEAContainer structure contained invalid syntax for an ACFS tag name.
- ACFS-07747: _ustEAEntryValueLen property has an invalid value\n found: number, but expected to find: number\n for _ustEAEntry offset: number for structure:\nstring
-
Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value length.
- ACFS-07748: _ustEAEntryValue property has an invalid value\n found: string, but expected to find: string\n for _ustEAEntry offset: number for structure:\nstring
-
Cause: The _ustEAEntryValue property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value string for an ACFS tag name.
- ACFS-07749: _ustEAContainerHdrNextContainer property has an invalid value\n found: string for structure:\nstring
-
Cause: The _ustEAContainerHdrNextContainer property of the indicated _ustEAContainer structure contained an invalid offset value.
- ACFS-07750: _ustEAContainerHdrNumEAEntries property has an invalid value\n found: number, but expected to find: number for structure:\nstring
-
Cause: The _ustEAContainerHdrNumEAEntries property of the indicated _ustEAContainer structure contained an incorrect count of valid entries.
- ACFS-07751: Inconsistent amount of available space\n found: number, but expected to find: number\n for structure:\nstring
-
Cause: The _ustEAContainer structure had an incorrect amount of free space.
- ACFS-07752: _LocalTags property has invalid characters for _FileEntry:\nstring
-
Cause: The _LocalTags property of the indicted _FileEntry structure contained invalid characters for ACFS tag names.
- ACFS-07753: _ustEAEntry property offset: number is marked free\n but is missing from the free list for structure:\nstring
-
Cause: The _ustEAContainer structure had an incorrect amount of free space.
- ACFS-07754: _ustEAContainer property has inconsistent\n total free and assigned _ustEAContainerEntry property space\n found: number, but expected to find: number for structure:\nstring
-
Cause: The _ustEAContainer structure contained free and active _ustEAContainerEntry property entries that indicate its total space exceeded the size of a _ustEAContainer structure.
- ACFS-07755: _ustEAContainerHdrNextFreeOffset property has an invalid value\n found: number, but expected to find less than: number for structure:\nstring
-
Cause: The ustEAContainerHdrNextFreeOffset property of the indicated _ustEAContainer structure was not within the range of valid offset values.
- ACFS-07756: _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property has an invalid value\n found: number, but expected to find less than: number for _ustEAContainerEntry at offset: number for structure:\nstring
-
Cause: The _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property of the indicated _ustEAContainerEntry property for the _ustEAContainer structure was not within the range of valid offset values.
- ACFS-07757: file extended attribute container structure exceeds file system size: string\n _Length: string\nfor structure:\nstring
-
Cause: The extended attribute container structure of the indicated file referenced meta data beyond the size of the file system. There are two possible causes: 1. The extended attribute container structure disk offset was incorrect. 2. The file system size value was incorrect.
- ACFS-07758: _ustEAEntryHdrNameLen property has an invalid value\n found: number, but expected non-zero value\n for _ustEAContainerEntry at offset: number for structure:\nstring
-
Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr property at the _ustEAContainerEntry offset for the indicated _ustEAContainer structure was invalid. Its value was zero but must be non-zero for an extended attribute name entry.
- ACFS-07759: _ustEAEntryValueLen property has an invalid value\n found: number, but expected to find less than: number\n for _ustEAEntry offset: number for structure:\nstring
-
Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property in the _ustEAEntryContainer structure contained an invalid value length that was larger than expected for this structure.
- ACFS-07760: _ustEAContainerHdrNextFreeOffset property has an invalid value\n found: number, but expected to find: number for structure:\nstring
-
Cause: The _ustEAContainerHdrNextFreeOffset property of the indicated _ustEAContainer structure was not within the range of valid offset values.
- ACFS-07761: directory _Private structure has invalid _dir_bitmap_start value\n found: string maximum: string\nfor structure:\nstring
-
Cause: The _dir_bitmap_start property of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
- ACFS-07762: Directory contains invalid bitmap block number at disk offset: string\nfor file:\nstring
-
Cause: A bitmap block of the indicated directory file was found in the wrong location. Directory bitmap blocks must be located contiguously after the first bitmap block.
- ACFS-07763: Directory bitmap is not contiguous from block number to block number at disk offset: string\nfor file:\nstring
-
Cause: A discontinuity was seen in the directory bitmap. Directory bitmap blocks must be located contiguously after the first bitmap block.
- ACFS-07764: Directory bitmap has incorrect last block\n found: number expected: number\nfor file:\nstring
-
Cause: The directory bitmap does not end where expected.
- ACFS-07765: Version 11.2.0.3 or earlier directory contains bitmap block number at disk offset: string\nfor file:\nstring
-
Cause: The directory _Private structure indicates that the directory does not have a bitmap, yet a bitmap block was found in the directory.
- ACFS-07766: Directory bitmap does not match state of block number\n bitmap: string block: string\nfor file:\nstring
-
Cause: The directory bitmap indicates an incorrect state for the directory block.
- ACFS-07767: Directory bitmap contains non-zero value for bit number mapping beyond end of directory:\nstring
-
Cause: The directory bitmap contains a non-zero bit in the range mapping blocks beyond the end of the directory.
- ACFS-07768: Directory _Private structure has invalid _dir_bitmap_size value\n found: string minimum: string\nfor structure:\nstring
-
Cause: The _dir_bitmap_size property of the indicated _Private directory structure was invalid. Its value did not meet the minimum value for the directory.
- ACFS-07769: Number of bitmap blocks found does not match value of _dir_bitmap_size in directory _Private structure\n found: string expected: string\nfor structure:\nstring
-
Cause: The number of bitmap blocks in the directory does not match the number of blocks that were expected.
- ACFS-07770: System directory _Private structure has invalid on-disk version\n found: string expected: string\nfor structure:\nstring
-
Cause: The on-disk version of the indicated _Private directory structure was invalid.
- ACFS-07771: directory _Private structure has invalid directory bitmap end value\n found: string maximum: string\nfor structure:\nstring
-
Cause: The calculated end of the directory bitmap of the indicated _Private directory structure was invalid. Its value exceeded the maximum value for the directory.
- ACFS-07772: snapshot 'string' has invalid _SnapLinkParentFenum value\n found: number maximum: number\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07773: snapshot link to non-existent snapshot
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07774: Global_Metadata_Directory structure has incorrect _remap_table_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07775: Global_Metadata_Directory structure has incorrect _remap_bitmap_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07776: Global_Metadata_Directory structure has incorrect _accelerator_remap_table_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07777: Global_Metadata_Directory structure has incorrect _accelerator_remap_bitmap_fileid value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07864: A request to cancel string was made \nwhile the file system was being repaired. This could leave the file system \nin an inconsistent state. It is strongly recommended that string \nbe rerun to complete file system repairs.
-
Cause: The ACFS fixer was cancelled before all file system repairs were completed.
- ACFS-07900: Security_Metadata file _Private structure has invalid _freeDataList value\n found: number maximum: number\nfor structure:\nstring
-
Cause: The _freeDataList property of the _Private structure of the indicated Security_Metadata file was incorrect. The _freeDataList value exceeded the maximum value for this Security_Metadata file.
- ACFS-07901: Hash_Bucket metadata structure has incorrect _controlling_bkt value\n found: string maximum: string\nfor structure:\nstring
-
Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was incorrect. Its value exceeded the maximum value for the hash table.
- ACFS-07902: Hash_File_Master_Block metadata structure has incorrect value for entry number in _hash_bucket_group array\n found: number minimum: number\nfor structure:\nstring
-
Cause: The entry in _hash_bucket_group array of the indicated Hash_File_Master_Block structure was incorrect.
- ACFS-07903: Hash_Bucket metadata structure has invalid data; expected all zeros\nfor structure:\nstring
-
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
- ACFS-07907: directory file has no storage allocated to it\nfor file:\nstring
-
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
- ACFS-07908: Root_Directory cannot be repaired\nfile:\nstring
-
Cause: The ACFS Checker/Fixer found an inconsistency with the Root_Directory metadata.
- ACFS-07909: System metadata was truncated, possibly resulting in the deletion of files.
-
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
- ACFS-07924: Snap_Map_header has invalid value for RW snap storage not in map\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The Snap_Map_header property that indicates the amount of RW snap storage not recorded in the Snap_Map file is incorrect.
- ACFS-07925: Snap_Map_header has invalid value for snap storage in map\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The Snap_Map_header property that indicates the amount of snap storage recorded in the Snap_Map file is incorrect.
- ACFS-07926: Snap_Map_header has invalid value for snap map flags\n found: string\nfor file:\nstring
-
Cause: The Snap_Map_header flags field is invalid.
- ACFS-07928: Plug-in configuration file has invalid _FileSize value\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: The _FileSize property of the indicated plug-in configuration file was incorrect.
- ACFS-07929: The string command is unable to open the storage accelerator volume string that is associated with this file system.
-
Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.
- ACFS-07930: Continuing will result in the storage accelerator volume being removed from the file system, which could leave the file system in an inconsistent and possibly unusable state if critical system metadata is stored on the storage accelerator volume.
-
Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.
- ACFS-07932: Volume string does not contain a valid ACFS storage accelerator.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07933: Accelerator volume string is associated with a different file system.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07934: The file identifier for the accelerator volume storage bitmap is invalid.\n found: string maximum: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07935: The _FileEntry metadata structure for the accelerator volume storage bitmap is invalid.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07936: Extent structure has incorrect _VolId value.\n found: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07937: File extent exceeds accelerator volume size.\n string\nextent: _FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07938: Accelerator Global_BitMap has invalid value for number of bits set.\n found: string maximum: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07939: Accelerator Global_BitMap has invalid value for number of bits set.\n found: string, but expected to find: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07940: Accelerator Global_BitMap has invalid value for next offset to search.\n found: string maximum: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07941: mismatch between temporary Global_BitMap and on-disk accelerator Global_BitMap
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07942: Accelerator Global_BitMap has bits incorrectly set for storage beyond the file system size for file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07943: The specified volume is an accelerator volume. Cannot proceed.
-
Cause: The volume specified on the command line was an accelerator volume. The command requires the primary file system volume.
- ACFS-07944: could not set up _VolDiskHdr STRUCT_INFO
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07945: found _DirNode in block: number at disk offset: string\nfor directory:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07946: string has an invalid extent node at disk offset string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07947: Mount point directory 'string' was specified when device name expected.
-
Cause: The ACFS Checker rejected the mount point because a file system device name was expected.
- ACFS-07950: File has _range_size value which does not match extent metadata.\n found: string expected: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07951: signal number received
-
Cause: The ACFS Checker received the indicated interrupt signal.
- ACFS-07952: File has _SynchFlags value indicating range locking which is not supported on this file system.\n found: string\nFile:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07953: File has invalid _range_size value.\n found: number expected: number\nFile:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07954: The specified volume is an accelerator volume so cannot be made mountable.
-
Cause: An attempt to force a volume into a mountable state using 'fsck.acfs -f' was rejected because the supplied volume was an accelerator. An accelerator can only be used in conjunction with its primary volume.
- ACFS-07955: read of global directory file entry failed
-
Cause: A read of the volume metadata during an invocation of 'fsck.acfs -f' failed. Accompanying messages provide failure details.
- ACFS-07956: accelerator volume found and restored
-
Cause: During an invocation of 'fsck.acfs -f', the supplied primary volume's metadata showed that it had made use of an accelerator volume. Both the primary and accelerator volumes have been restored, but the metadata has not been verified.
- ACFS-07957: unable to mount removed file system string
-
Cause: An attempt to mount the indicated file system was rejected because it had been removed via the acfsutil rmfs utility.
- ACFS-07960: acfsdbg cannot find the ACFS storage accelerator volume
-
Cause: An attempt to locate the ACFS storage accelartor volume failed. Either: - the file system did not have an ACFS storage accelerator, or - the metadata for locating the ACFS storage accelerator was corrupt, or - the 'acfsdbg' command was being used to analyze the output of the 'acfsutil meta' command, and the sparse copy of the ACFS storage accelerator volume was not provided.
- ACFS-07961: GBM Lookup Table is corrupt and must be removed.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07962: GBM Lookup Table has the wrong size.\n found: number expected: number
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07963: GBM Lookup Table is not a multiple of the block size.\n found: number expected: number
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07964: mismatch between GBM Lookup Table block and temporary GBM Lookup Table block for disk offset: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07965: Global_Metadata_Directory structure has incorrect _glut_fenum value\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07966: GBM Lookup Table file entry is not initialized.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07967: 'acfsutil meta' files and ACFS file system devices cannot be processed at the same time: string
-
Cause: An ACFS Checker attempt was rejected because a mix of 'acfsutil meta' metadata collector files and physical ACFS file system devices were specified on the command line.
- ACFS-07968: Remap_BitMap bit set for disk offset string has no corresponding remapped offset.
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07969: Remap_Table has incorrect _VolVolumeSize value.\n found: string, but expected to find: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-07970: communication error with ACFS kernel driver encountered during setup for online fsck
-
Cause: An attempt to run online fsck failed due to a communication error with the ACFS kernel driver. The accompanying messages provide detailed failure information.
- ACFS-07971: communication error with ACFS kernel driver encountered during cleanup for online fsck
-
Cause: An execution of online fsck did not completely correctly because a communication error with the ACFS kernel driver occurred during cleanup processing. The accompanying messages provided detailed failure information. As a result, cleanup of online fsck may be incomplete, which may cause failures in other ACFS operations. Manual cleanup of online fsck should undertaken as soon as possible to ensure continued correct operation.
- ACFS-07972: unable to unlink online fsck Copy-On-Write (COW) file: string
-
Cause: An execution of online fsck did not complete correctly because unlinking the online fsck COW file failed. The accompanying messages provide detailed failure information.
- ACFS-07973: online fsck Copy-On-Write (COW) file string not accessible on all nodes
-
Cause: An attempt to run online fsck for an ACFS file system failed because one or more nodes with the ACFS file system mounted were unable to access the indicated online fsck COW file.
- ACFS-07974: online fsck already active on the specified ACFS file system
-
Cause: An attempt to run online fsck for an ACFS file system was rejected because it appeared an instance of online fsck was already active on the ACFS file system.
- ACFS-07975: online fsck already active on another ACFS file system
-
Cause: An attempt to run online fsck for an ACFS file system was rejected because it appeared an instance of online fsck was already active on another ACFS file system within the same cluster. More than one instance of online fsck is not allowed within the same cluster.
- ACFS-07976: network communication error encountered during setup for online fsck
-
Cause: An attempt to run online fsck for an ACFS file system failed because a network communication error was encountered between the nodes that have the ACFS file system mounted.
- ACFS-07977: network communication error encountered during cleanup for online fsck
-
Cause: An execution of online fsck did not complete correctly because a network communication error occurred during cleanup processing between the nodes that have the ACFS file system mounted. As a result, cleanup of online fsck may be incomplete, which may cause failures in other ACFS operations. Manual cleanup of online fsck should be undertaken as soon as possible to ensure continued correct operation.
- ACFS-07978: I/O error encountered accessing online fsck Copy-On-Write (COW) file
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because online fsck encountered an I/O error while accessing the online fsck COW file.
- ACFS-07979: unexpected error number from ACFS kernel driver encountered during setup for online fsck
-
Cause: An attempt to run online fsck for an ACFS file system failed because of an unexpected error reported from the ACFS kernel driver.
- ACFS-07980: unexpected error number from ACFS kernel driver encountered during cleanup for online fsck
-
Cause: An execution of online fsck did not complete correctly because an unexpected error during cleanup processing was reported from the ACFS kernel driver. As a result, cleanup of online fsck may be incomplete, which may cause failures in other ACFS operations. Manual cleanup of online fsck should be undertaken as soon as soon as possible to ensure continued correct operation.
- ACFS-07981: failed to copy global ACFS metadata to online fsck Copy-On-Write (COW) file
-
Cause: An attempt to run online fsck for an ACFS file system failed because online fsck could not copy global ACFS metadata to the online fsck COW file.
- ACFS-07982: incorrect kernel state number for online fsck encountered during setup for online fsck
-
Cause: An attempt to run online fsck for an ACFS file system failed because the state data for online fsck maintained in the ACFS kernel driver was inconsistent. This is an internal error.
- ACFS-07983: incorrect kernel state number for online fsck encountered during cleanup for online fsck
-
Cause: An execution of online fsck did not complete correctly because the state data for online fsck maintained in the ACFS kernel driver was inconsistent during cleanup processing. This is an internal error.
- ACFS-07984: online fsck aborted because file system mounted on a new node
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because the ACFS file system was mounted on a new node while online fsck was running.
- ACFS-07985: communication error with ACFS kernel driver encountered while querying runtime status for online fsck
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because a query to the ACFS kernel driver for the runtime status for online fsck encountered a communcation error. The accompanying messages provide detailed failure information.
- ACFS-07986: online fsck Copy-On-Write (COW) file is full
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because the online fsck COW file ran out of space.
- ACFS-07987: unknown runtime error number encountered during online fsck
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because an unknown runtime error was encountered.
- ACFS-07988: network communication error encountered during online fsck
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because a network communication error was encountered between the nodes that have ACFS file ssytem mounted.
- ACFS-07990: unexpected non-empty volume logs encountered during online fsck
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because non-empty volume logs were encountered unexpectedly.
- ACFS-07991: The length of the online fsck Copy-On-Write (COW) file path exceeds number.
-
Cause: An attempt to run online fsck was rejected because the specified online fsck COW file path exceeded the maximum length displayed in the message.
- ACFS-07999: unexpected ACFS Checker/Fixer assert: "string", string: string: number
-
Cause: An unexpected situation has occurred.
- ACFS-08000: unable to create online fsck Copy-On-Write (COW) file: string
-
Cause: An attempt to run online fsck was rejected because an error occurred while creating the indicated COW file. The accompanying messages provide detailed failure information.
- ACFS-08001: online fsck Copy-On-Write (COW) file path is not on an ACFS file system
-
Cause: An attempt to run online fsck was rejected because the specified online fsck COW file path is not on an ACFS file system.
- ACFS-08002: _NextDeferredListLink on Deferred_Delete_Storage_List references a snapshot that is not valid\n _NextDeferredListLink: string\n snapshot: string (identifier: number)\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08003: Deferred_Delete_Storage_List has invalid file identifier for _PrevDeferredListLink:\n found: string expected: string\nfor structure:\n string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08004: unable to process Deferred_Delete_Storage_List data for structure:\n%(1)
-
Cause: File system checking has identified metadata inconsistencies. The accompanying messages provide further details.
- ACFS-08005: Deferred_Delete_Storage_List incorrectly contains an entry for a read only snapshot:\n file identifier: string\n snapshot: string (identifier: number)\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08006: _NextDeferredListLink on Deferred_Delete_Storage_List references a file identifier that exceeds the maximum value supported for this file system\n _NextDeferredListLink: string\n file identifier: string maximum: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08007: string has determined that there is a loop within a Deferred_Delete_Storage_List\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08008: Deferred_Delete_Storage_List structure for accelerator volume has invalid values:\n _PrevDeferredListLink: string\n _NextDeferredListLink: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08009: Deferred_Delete_Storage_List for snapshot: string (identifier: number) incorrectly contains an entry for a File_Entry_Table: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08010: Deferred_Delete_Storage_List entry contains an invalid _DRSLSequenceNumber\n found: string\n maximum: string\nfor file:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08011: _NextDeferredListLink on Deferred_Delete_Storage_List references a snapshot that does not exist\n _NextDeferredListLink: string\n snapshot identifier: number\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08012: Deferred_Delete_Storage_List has invalid file identifier for_NextDeferredListLink: string\n snapshot identifier: number\n found: string minimum: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08013: Deferred_Delete_Storage_List contains an entry that was previously referenced by a directory or other ACFS structure\n _NextDeferredListLink: string\n file identifier: string\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08016: multiple invalid snap_map_tuples found; number found: number
-
Cause: File system checking has identified the metadata inconsistency reported in the message. The number of instances is indicated here in lieu of flooding the output by displaying message ACFS-07414 for each occurrence.
- ACFS-08017: multiple snap_map_tuples with (0,0) found where a non-zero value was expected; number found: number
-
Cause: File system checking has identified the metadata inconsistency reported in the message. The number of instances is indicated here in lieu of flooding the output by displaying message ACFS-07448 for each occurrence.
- ACFS-08018: allocated but unused storage of number MB found
-
Cause: File system checking has identified unreferenced snapshot storage that could be freed.
- ACFS-08019: online fsck already active on the local node
-
Cause: An attempt to run online fsck for an ACFS file system was rejected because it appeared an instance of online fsck was already active on the local node.
- ACFS-08020: size of the online fsck Copy-On-Write (COW) file must be at least number megabytes
-
Cause: An attempt to run online fsck was rejected because the specified online fsck COW file size was smaller than the minimum size displayed in the message.
- ACFS-08021: online fsck flags string must be specified with the string flag
-
Cause: An attempt to run online fsck was rejected because insufficient online fsck flags were specified.
- ACFS-08022: failed to create online fsck Copy-On-Write (COW) file due to insufficient free storage
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because the ACFS file system containing the online fsck COW file did not have sufficient free storage for the full online fsck COW file.
- ACFS-08023: failed to create online fsck Copy-On-Write (COW) file
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because the online fsck Copy-On-Write (COW) file could not be created successfully.
- ACFS-08024: online fsck is unsupported by the loaded ACFS driver version
-
Cause: An attempt to run online fsck for an ACFS file system was rejected because the loaded ACFS driver version does not support online fsck.
- ACFS-08025: online fsck could not read on-disk superblocks
-
Cause: An attempt to run online fsck for an ACFS file system failed because the on-disk superblocks could not be read.
- ACFS-08026: online fsck found invalid on-disk superblocks
-
Cause: An attempt to run online fsck for an ACFS file system failed because the on-disk superblocks were found to be invalid.
- ACFS-08027: online fsck Copy-On-Write (COW) file cannot be within the ACFS file system undergoing online fsck
-
Cause: An attempt to run online fsck for an ACFS file system was rejected because the online fsck Copy-On-Write (COW) file was placed on the ACFS file system undergoing online fsck.
- ACFS-08028: online fsck encountered unexpected partial read
-
Cause: An attempt to run online fsck for an ACFS file system failed due to an unexpected read error.
- ACFS-08029: The ACFS Checker failed because it was supplied an unexpanded acfsutil meta output file.\n The file needs to be exapnded using\n acfsutil meta -e string -f string.expanded
-
Cause: The ACFS Checker did not know how to read an unexpanded acfsutil meta output file.
- ACFS-08030: Failed to write metadata collector record header (Flags:0xnumber, VolID:number, Offset:number, Size:number)\n Write size:number\n Actual written:number
-
Cause: The ACFS Checker failed to write a record header to the metadata collector file.
- ACFS-08031: Failed to write metadata collector record body (Flags:0xnumber, VolID:number, Offset:number, Size:number)\n Write size:number\n Actual written:number
-
Cause: The ACFS Checker failed to write a record body to the metadata collector file.
- ACFS-08032: could not disable compression for online fsck Copy-On-Write (COW) file
-
Cause: An attempt to run online fsck for an ACFS file system failed because compression could not be disabled for the online fsck Copy-On-Write (COW) file.
- ACFS-08033: online fsck aborted to avoid file system deadlock
-
Cause: An attempt to run online fsck for an ACFS file system was aborted to avoid a deadlock within the file system.
- ACFS-08034: online fsck failed to fix metadata due to communication error with ACFS kernel driver
-
Cause: An attempt by online fsck to fix file system metadata failed due to a communication error with the ACFS kernel driver. The accompanying messages provide detailed failure information.
- ACFS-08035: unexpected error number from ACFS kernel driver encountered while fixing metadata via online fsck
-
Cause: An attempt by online fsck to fix file system metadata failed due to an unexpected error reported from the ACFS kernel driver.
- ACFS-08036: unable to stop online fsck
-
Cause: An unmount operation was unable to stop an online fsck operation that had been using the unmounting filesystem to store a Copy-On-Write (COW) file.
- ACFS-08037: online fsck aborted because the file system containing the Copy-On-Write (COW) file was unmounted on one or more nodes
-
Cause: An attempt to run online fsck for an ACFS file system was aborted because the ACFS file system containing the Copy-On-Write (COW) file was unmounted on one or more nodes.
- ACFS-08038: online fsck could not start due to insufficient space in file system
-
Cause: An attempt to run online fsck for an ACFS file system failed because the ACFS file system is full.
- ACFS-08039: online fsck could not start due to insufficient memory
-
Cause: An attempt to run online fsck for an ACFS file system failed because there was insufficient memory on one of the nodes with the ACFS file system mounted.
- ACFS-08040: online fsck could not clean up due to insufficient memory
-
Cause: An execution of online fsck for an ACFS file system did not complete correctly because there was insufficient memory on one of the nodes with the ACFS file system mounted.
- ACFS-08041: online fsck failed to create internal structures
-
Cause: An attempt to run online fsck for an ACFS file system failed due to errors while creating internal structures.
- ACFS-08043: Could not determine the file size for: string
-
Cause: The ACFS Checker failed to get the specified file's size.
- ACFS-08044: Failed to write metadata collector log message to string
-
Cause: The ACFS Checker failed to write the log message to the specified log file.
- ACFS-08045: online fsck could not create special work directory
-
Cause: An attempt to run online fsck for an ACFS file system failed because it could not create a special work directory required for online fsck execution.
- ACFS-08046: allocated but unused storage of number MB found
-
Cause: File system checking has identified unreferenced fshare storage that could be freed.
- ACFS-08047: RefCnt Table has an invalid counts for number of entries: string
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08048: unable to determine default location for online fsck Copy-On-Write (COW) file because the cluster is in rolling migration
-
Cause: Due to rolling upgrade from older kernel versions, the location for the online fsck Copy-On-Write (COW) file must be specified and must be placed in a separate ACFS file system from the ACFS file system undergoing online fsck.
- ACFS-08049: A valid ACFS mount point is required
-
Cause: A valid ACFS mount point was not entered.
- ACFS-08050: acfsdbg command line had 2 conflicting Volume IDs: string vs string
-
Cause: The user specified acfsdbg command has 2 different Volume IDs.
- ACFS-08051: acfsdbg command field does not support a Volume ID prefix: string
-
Cause: The user specified acfsdbg command field does not allow a Volume ID prefix.
- ACFS-08052: Global_Metadata_Directory structure has incorrect _nimap_fenum value\n found zero but expected to find non-zero value\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-08053: Global_Metadata_Directory structure has incorrect _accel_nimap_fenum value\n found zero but expected to find non-zero value\nfor structure:\nstring
-
Cause: File system checking has identified the metadata inconsistency reported in the message.
- ACFS-09004: CreateProcess of acfsmountvol failed, string
-
Cause: The 'advmutil mount' command failed because a required process could not be created. The accompanying messages provide detailed failure information.
- ACFS-09005: Error running string
-
Cause: The 'advmutil mount' command failed because a required process could not be executed. The accompanying messages provide detailed failure information.
- ACFS-09006: Error opening volume string
-
Cause: The advmutil command failed because the indicated file could not be created. The accompanying messages provide detailed failure information.
- ACFS-09009: Error closing volume string
-
Cause: The 'advmutil mount' or 'advmutil list' command encountered an error
- ACFS-09010: Error locking volume string
-
Cause: The 'advmutil dismount' command failed while attempting to lock the indicated volume. The accompanying messages provide detailed failure information.
- ACFS-09011: Error dismounting file system on volume string
-
Cause: The 'advmutil dismount' command failed. The accompanying messages provide detailed failure information.
- ACFS-09012: Error opening the Windows Registry
-
Cause: The 'advmutil list' command failed while opening the Windows Registry. This is an internal error.
- ACFS-09013: Error reading the Windows Registry
-
Cause: The 'advmutil list' command failed while reading the Windows Registry. This is an internal error.
- ACFS-09015: The volume string was not found. Verify the diskgroup is mounted and the volume is enabled.
-
Cause: The 'advmutil mount' command failed because the indicated ADVM volume was not found.
- ACFS-09016: Error mounting volume string on drive string
-
Cause: The 'advmutil mount' command failed to mount the specified volume. The accompanying messages provide detailed failure information.
- ACFS-09018: Error broadcasting mount of volume string on drive string
-
Cause: The 'advmutil mount' command failed because it was unable to broadcast device change information to other devices in the system. The accompanying messages provide detailed failure information.
- ACFS-09019: Error opening volume on string
-
Cause: The 'advmutil dismount' command failed to open the indicated file. The accompanying messages provide detailed failure information.
- ACFS-09020: Error dismounting string
-
Cause: An 'advmutil dismount' operation failed to remove a symbolic link. The accompanying messages provide detailed failure information.
- ACFS-09021: Error broadcasting dismount of string
-
Cause: The 'advmutil dismount' command failed because it was unable to broadcast device change information to other devices in the system. The accompanying messages provide detailed failure information.
- ACFS-09025: Failed to update the Windows Registry for volume string on drive string
-
Cause: An attempt to store data in the Windows registry failed. The accompanying messages provide detailed failure information.
- ACFS-09027: Error deleting the drive letter assignment string
-
Cause: An 'advmutil dismount' command failed because the specified drive letter could not be removed from a volume assignment. The accompanying messages provide detailed failure information.
- ACFS-09028: Assignment for drive letter string not found
-
Cause: An 'advmutil dismount' command failed because the indicated drive letter could not be found.
- ACFS-09030: Error unassigning drive letter string from volume string
-
Cause: An advmutil dismount failed because it could not unassign a drive letter. The accompanying messages provide detailed failure information.
- ACFS-09034: Error taking string offline
-
Cause: An 'advmutil dismount' command failed to offline the specified mount point.
- ACFS-09035: Error unlocking string
-
Cause: An 'advmutil dismount' command failed because it could not unlock the specified file system. The accompanying messages provide detailed failure information.
- ACFS-09036: Error bringing string online
-
Cause: An 'advmutil mount' command failed because it could not bring the specified file system online. The accompanying messages provide detailed failure information.
- ACFS-09037: Error reading reparse point string
-
Cause: An 'advmutil dismount' command failed because it could not read the specified reparse point. The accompanying messages provide detailed failure information.
- ACFS-09100: Creating volume 'string' in diskgroup 'string'.
-
Cause: Informational
- ACFS-09101: Failed to create volume 'string' in diskgroup 'string'.
-
Cause: The volume was unable to be created in the diskgroup. Possible Causes: 1) ASM is not running. 2) User is not part of the ASMADMIN group. 3) An ASM specific error occurred.
- ACFS-09102: Unable to verify creation of ACFS Oracle database Home.
-
Cause: A command was given to ASM to create the specified volume and no errors were detected. However, post creation checks failed to find that the volume that was created and/or enabled.
- ACFS-09103: Enabling volume 'string' on diskgroup 'string'.
-
Cause: Informational
- ACFS-09104: Enable of volume 'string' failed.
-
Cause: ASM was instructed to enable the specified volume and failed.
- ACFS-09105: Volume 'string' not found in 'string'.
-
Cause: The specified volume does not exist.
- ACFS-09106: Diskgroup 'string' not found.
-
Cause: The specified diskgroup does not exist.
- ACFS-09107: ASM mounting diskgroup 'string'.
-
Cause: Informational
- ACFS-09108: ASM mount of diskgroup 'string' failed.
-
Cause: ASM found the specified diskgroup but could not mount it.
- ACFS-09109: string driver failed to load.
-
Cause: The driver failed to load.
- ACFS-09110: Offline mount point 'string' was dismounted for recovery.
-
Cause: Informational. The mount point referenced was fenced due to an underlying volume failure. In this case, the mount point was successfully dismounted for recovery.
- ACFS-09111: Offline mount point 'string' was recovered.
-
Cause: Informational - the mount point referenced was fenced due to an underlying volume failure. In this case, the mount point was successfully remounted, which has renabled IO to the file system.
- ACFS-09112: The following process IDs have open references on mount point 'string':
-
Cause: During shutdown of the CRS stack, it was determined that a process had files open on the mount point in the process of being dismounted. This prevents the dismount from succeeding.
- ACFS-09113: These processes will now be terminated.
-
Cause: Informational
- ACFS-09114: completed
-
Cause: Informational
- ACFS-09115: The command 'string' returned an unexpected value.
-
Cause: This is an internal error.
- ACFS-09116: Offline mount point 'string' was not recovered.
-
Cause: An inaccessible mount point could not be restored to working condition.
- ACFS-09117: Manual intervention is required.
-
Cause: Informational, from previous errors.
- ACFS-09118: Driver string in use - cannot unload.
-
Cause: This may be seen during 'crsctl stop crs', 'acfsload stop', or 'acfsroot uninstall'. Applications (possibly ASM) have open references on the driver.
- ACFS-09119: Driver string failed to unload.
-
Cause: An unknown error has occurred when trying to unload the driver.
- ACFS-09120: The 'string' machine architecture not supported.
-
Cause: ADVM/ACFS device drivers have not yet been ported to this CPU type or OS. This occurs when the customer manually tries to load the drivers on an architecture or system OS type that ACFS is not supported, such as VMS.
- ACFS-09121: Failed to detect control device 'string'.
-
Cause: ADVM/ACFS device drivers have been started but the devices that should have been created have not been.
- ACFS-09122: ADVM device not determined from mount point 'string'.
-
Cause: This is an internal error.
- ACFS-09123: 'string' command not found.
-
Cause: A required component of ACFS is missing. This could be an incomplete install, removal of files from the system after install, or an unknown cause.
- ACFS-09124: string driver failed to detach from the system driver stack.
-
Cause: The ACFS driver is being used by one or more mounted file systems.
- ACFS-09125: ADVM/ACFS is not supported on this OS: 'string'
-
Cause: ADVM/ACFS device drivers have not been ported to this OS.
- ACFS-09126: Attempting to terminate the program 'string' with OS process ID 'string'.
-
Cause: The process was using an ACFS file system, which was being forcibly unmounted. A kill signal was sent to allow the unmount to proceed.
- ACFS-09127: Not all ADVM/ACFS drivers have been loaded.
-
Cause: ADVM/ACFS device drivers have been started but not all of them are detected as running.
- ACFS-09128: unknown query type 'string'
-
Cause: This is an internal error.
- ACFS-09129: ADVM/ACFS not installed
-
Cause: No ADVM/ACFS drivers or commands have been found on the system. All ADVM and ACFS actions will be disabled.
- ACFS-09130: Root access required
-
Cause: The user this command is executing as does not have sufficient privileges to run this command.
- ACFS-09135: string installation aborted.
-
Cause: Informational
- ACFS-09136: PID string could not be killed.
-
Cause: Failed to kill a Process ID during a force unmount of a file system.
- ACFS-09137: Failed to set group on directory 'string'.
-
Cause: The group of the directory could not be changed.
- ACFS-09138: command 'string' completed with an error: string
-
Cause: 'acfsutil' did not successfully run.
- ACFS-09139: Attempting recovery of offline mount point 'string'
-
Cause: An ACFS mount point reported by the 'acfsutil' command was not accessible.
- ACFS-09140: Unable to determine the correct drivers for this version of Windows: ID:string Major:string Minor:string Product Type:string
-
Cause: Error. ACFS is not supported on this Windows Version.
- ACFS-09149: unable to determine device mount status - unsupported OS name 'string'
-
Cause: The standard method to determine mount state of a device was unavailable. It is possible that ADVM/ACFS is not supported on the OS.
- ACFS-09150: Unexpected output from 'acfsutil info fs': 'string'.
-
Cause: Informational
- ACFS-09151: Ignoring request to mount due to existence of "oracle_nomounts" file: string
-
Cause: "An "oracle_nomounts" file was present, causing file system mount processing to be skipped during a CRS resource operation."
- ACFS-09152: Program 'string' with OS process ID 'string' will not be terminated.
-
Cause: The process is using an ACFS file system which is being forcibly unmounted but it will not be terminated because it is a system critical process.
- ACFS-09153: Program 'string' with OS process ID 'string' is using mount point 'string'.
-
Cause: The process is using the mount point.
- ACFS-09154: Loading 'string' driver.
-
Cause: Informational.
- ACFS-09155: Checking for existing 'string' driver installation.
-
Cause: Informational.
- ACFS-09156: Detecting control device 'string'.
-
Cause: Informational.
- ACFS-09157: Detecting driver 'string'.
-
Cause: Informational.
- ACFS-09158: Configuration file 'string' in the /boot directory does not exist.
-
Cause: A populated /boot directory, which contains static files required to install kernel modules, was not detected on the system.
- ACFS-09160: Can not use the silent and verbose options at the same time.
-
Cause: The -s and -v options were used in the command. These options are mutually exclusive.
- ACFS-09161: acfsroot install: Install ADVM/ACFS components.
-
Cause: Informational.
- ACFS-09162: acfsroot uninstall: Uninstall ADVM/ACFS components.
-
Cause: Informational.
- ACFS-09163: acfsroot version_check: Check ADVM/ACFS version.
-
Cause: Informational.
- ACFS-09164: acfsroot enable: Enable ADVM/ACFS CRS resources.
-
Cause: Informational.
- ACFS-09165: acfsroot disable: Disable ADVM/ACFS CRS resources.
-
Cause: Informational.
- ACFS-09166: string [-h] [-s | -v]
-
Cause: Syntax error or help [-h] option was passed.
- ACFS-09167: ADVM/ACFS is not installed or loaded. Run 'acfsroot install'.
-
Cause: An operation was requested that requires ADVM/ACFS to be running.
- ACFS-09168: The CRS query "string" cannot be parsed.
-
Cause: This is an internal error.
- ACFS-09169: The CRS attribute value specification "string" is invalid.
-
Cause: This is an internal error.
- ACFS-09170: The file system's CRS resource name "string" is invalid.
-
Cause: This is an internal error.
- ACFS-09171: The CRS resource for the file system on device string cannot be retrieved
-
Cause: Informational
- ACFS-09172: The CRS resource for the file system on device string cannot be registered
-
Cause: Informational
- ACFS-09173: The srvctl command line "string" failed to execute. (number)
-
Cause: This is an internal error.
- ACFS-09174: unable to communicate with CRS
-
Cause: The application failed to communicate with CRS.
- ACFS-09175: Invalid trace level. Valid values for trace level are 0, 1 or 2.
-
Cause: An invalid trace level was provided.
- ACFS-09176: Entering 'string'
-
Cause: Informational.
- ACFS-09177: Return from 'string'
-
Cause: Informational.
- ACFS-09178: Return code = string
-
Cause: Informational.
- ACFS-09179: Command executed: 'string', output = 'string'
-
Cause: Informational.
- ACFS-09180: Sub-command is 'string'
-
Cause: Informational.
- ACFS-09181: Kernel version is 'string'
-
Cause: Informational.
- ACFS-09182: Variable 'string' has value 'string'
-
Cause: Informational.
- ACFS-09183: Query = 'string'
-
Cause: Informational.
- ACFS-09184: string [-h] [-s | -v | -t <0,1,2>]
-
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
- ACFS-09185: string [-h] [-s | -v | -t <0,1,2>] [-l directory]
-
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
- ACFS-09186: Usage: acfsroot uninstall [-h] [-s | -v | -t <0,1,2>]
-
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
- ACFS-09187: Usage: acfsroot version_check [-h] [-t <0,1,2>] [-l location]
-
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
- ACFS-09188: cannot use the trace option with the silent or verbose options
-
Cause: Conflicting options were specified.
- ACFS-09189: [-t <0,1,2> ] - trace level
-
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
- ACFS-09190: User group 'string' does not exist.
-
Cause: The group name is required to create ADVM/ACFS devices with the correct attributes. The group name could not be found in the /etc/group file nor in the various remote services like LDAP, AD, NIS/Yellow Pages, DNS, etc.
- ACFS-09191: Usage: acfsroot version_check [-h] [-t <0,1,2>]
-
Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
- ACFS-09192: unknown installation mode: string
-
Cause: An attempt to execute the 'acfsroot install' command failed because an unknown mode was specified.
- ACFS-09193: Use of the -m flag is not supported in this OS.
-
Cause: An attempt was made to install ACFS with the -m flag in an operating system that did not support Oracle Database Appliance modes.
- ACFS-09194: unable to query the WMI service to identify the Windows OS Version
-
Cause: A requested management operation failed because an attempt to obtain the current Windows OS version from the Windows Managment Instrumentation (WMI) Service in order to determine whether ACFS/ADVM drivers were supported was not successful.
- ACFS-09195: Unable to access the specified Cluster Manifest File: string
-
Cause: An attempt to access the specified Cluster Manifest File failed.
- ACFS-09200: Supported
-
Cause: ADVM/ACFS device drivers have been ported to this OS or CPU type.
- ACFS-09201: Not Supported
-
Cause: ADVM/ACFS device drivers have not yet been ported to this OS or CPU type.
- ACFS-09203: true
-
Cause: ADVM/ACFS device drivers were installed/loaded.
- ACFS-09204: false
-
Cause: ADVM/ACFS device drivers were not installed/loaded.
- ACFS-09205: usage: string [-h] [-orahome <home_path>] {installed | loaded | version | supported | validate} [-s]
-
Cause: Syntax error or help [-h] option was passed.
- ACFS-09206: usage: string [-orahome <ORACLE_HOME>] {installed | loaded | version | supported} [-s]
-
Cause: Syntax error.
- ACFS-09207: The user this command is executing as does not have permission to execute Perl in 'string'.
-
Cause: Perl permissions are read/write/execute owner (0700). The user this command is executing as is not the owner of the perl binary.
- ACFS-09208: Enter the location of the db home for this database to '-orahome'.
-
Cause: Perl permissions are read/write/execute owner (0700). The user this command is executing as is not the owner of the perl binary.
- ACFS-09210: The ADVM/ACFS drivers are supported but have not been verified on this Operating System version.
-
Cause: The drivers have not been explicitly tested on this operating system version but are expected to work properly.
- ACFS-09211: usage: string [-h] [-orahome <home_path>] {installed | loaded | version [-v]| supported [-v]} [-s]
-
Cause: Syntax error or help [-h] option was passed.
- ACFS-09213: Configuration file 'string' in the /boot directory does not exist or cannot be read.
-
Cause: An attempt to check for compatible kernel was unable to read required /boot configuration data.
- ACFS-09225: Failed to start OKS persistent logging.
-
Cause: The drivers were successfully loaded but Oracle Kernel Services (OKS) persistent logging failed to start.
- ACFS-09226: ADVM/ACFS drivers not correct for this OS - cannot load.
-
Cause: The device drivers installed are not compatible with the currently running operating system
- ACFS-09250: Unable to get the ASM administrator user name from the ASM process.
-
Cause: ASM processes have not been found running on this system. This will prevent the requested action from being completed.
- ACFS-09251: Mount point 'string' unmounted.
-
Cause: Informational.
- ACFS-09252: The following process IDs have open references on mount point 'string':
-
Cause: Informational.
- ACFS-09253: Failed to unmount mount point 'string'. Mount point likely in use.
-
Cause: Other processes have outstanding open references on the mount point.
- ACFS-09254: Manual intervention is required.
-
Cause: Follow up message to ACFS-9253.
- ACFS-09255: Creating 'string' mount point.
-
Cause: Informational.
- ACFS-09256: Failed to create mountpoint 'string'.
-
Cause: The mount point may already exist, the user executing the command may have insufficient permission, or a system specific error may have occurred.
- ACFS-09257: Mounting device 'string' on mount point 'string'.
-
Cause: Informational.
- ACFS-09258: Failed to mount device 'string' on mount point 'string'.
-
Cause: The mount point may be in use, the user executing this command may have insufficient permissions, or another system specific error may have occurred.
- ACFS-09259: Mount point 'string' already has a device mounted on it.
-
Cause: There is already a device mounted on this mount point.
- ACFS-09260: Failed to connect to the ASM instance.
-
Cause: ASM connection attempt failed.
- ACFS-09261: Invalid _ORA_NAME format.
-
Cause: This is an internal error.
- ACFS-09262: Invalid sub-command 'string'.
-
Cause: This is an internal error or the user attempted to run the script manually with an incorrect sub-command.
- ACFS-09263: Valid sub-commands are 'start', 'stop', 'check', and 'clean'.
-
Cause: This results in an incorrect usage of the command.
- ACFS-09264: Mount point 'string' is not mounted.
-
Cause: Informational.
- ACFS-09274: Resource 'string' is not online.
-
Cause: Informational.
- ACFS-09275: The clean failed to unmount the required mountpoint(s) - re-trying.
-
Cause: Informational. A file system could not be unmounted. This could be due to new process being started just before the unmount.
- ACFS-09289: string not set in environment.
-
Cause: The referenced environment variable was not set. This makes it impossible to continue with the requested action.
- ACFS-09290: Waiting for ASM to shutdown.
-
Cause: The resource cannot be terminated while ASM is running.
- ACFS-09291: Waiting for the Windows 'sc stop string' command to complete.
-
Cause: Informational. System activity is preventing the driver from stopping.
- ACFS-09292: Warning: A newer version of ACFS software is available in Oracle home string.
-
Cause: A version check prompted by user request or a maintenance operation determined that updated software is available in the indicated Oracle home.
- ACFS-09293: Kernel and command versions do not match.
-
Cause: A requested version check or a system monitor has found that the installed tools are out of sync with the installed kernel modules. This may cause interoperability issues.
- ACFS-09295: failed to open file string
-
Cause: A requested action failed to complete because the indicated file could not be opened.
- ACFS-09300: ADVM/ACFS distribution files found.
-
Cause: Informational.
- ACFS-09301: ADVM/ACFS installation cannot proceed:
-
Cause: Previous errors have caused the installation to reach a point where it cannot continue.
- ACFS-09303: No installation files found for OS kernel version string.
-
Cause: If '-l' (distribution directory) was specified, the directory may not be valid.
- ACFS-09304: Installation cannot proceed: Failed to unload ADVM/ACFS drivers.
-
Cause: Applications (possibly ASM) have open references on the drivers.
- ACFS-09305: ADVM/ACFS installation cannot proceed:
-
Cause: Informational.
- ACFS-09306: Failed to uninstall previous installation.
-
Cause: Could not remove ADVM/ACFS commands and or drivers.
- ACFS-09307: Installing requested ADVM/ACFS software.
-
Cause: Informational.
- ACFS-09308: Loading installed ADVM/ACFS drivers.
-
Cause: Informational.
- ACFS-09309: ADVM/ACFS installation correctness verified.
-
Cause: Informational.
- ACFS-09310: ADVM/ACFS installation failed.
-
Cause: A previous error caused this installation to fail.
- ACFS-09311: not all components were detected after the installation.
-
Cause: ADVM/ACFS commands and drivers were found in the installation area but did not get placed in their assigned locations.
- ACFS-09312: Existing ADVM/ACFS installation detected.
-
Cause: Informational.
- ACFS-09313: No ADVM/ACFS installation detected.
-
Cause: An attempt was made to un-install ADVM/ACFS components that did not exist on the system.
- ACFS-09314: Removing previous ADVM/ACFS installation.
-
Cause: Informational.
- ACFS-09315: Previous ADVM/ACFS components successfully removed.
-
Cause: Informational.
- ACFS-09316: Valid ADVM/ACFS distribution media detected at: 'string'
-
Cause: Informational.
- ACFS-09317: No ADVM/ACFS distribution media detected at location: 'string'
-
Cause: If -l (location) is used, the directory specified may be invalid.
- ACFS-09318: ORACLE_HOME is not set.
-
Cause: This is an internal error.
- ACFS-09319: Unknown OS kernel version 'string' detected.
-
Cause: This is an internal error.
- ACFS-09320: Missing file: 'string'.
-
Cause: A required command or driver is not found on the installation media (pre install) or system (post install).
- ACFS-09321: Creating udev for ADVM/ACFS.
-
Cause: Informational.
- ACFS-09322: completed
-
Cause: Informational.
- ACFS-09323: Creating module dependencies - this may take some time.
-
Cause: Informational.
- ACFS-09324: Alternate drivers installed.
-
Cause: Informational.
- ACFS-09327: Verifying ADVM/ACFS devices.
-
Cause: Informational.
- ACFS-09328: unknown query type 'string'.
-
Cause: This is an internal error.
- ACFS-09329: Failed to uninstall driver: 'string'.
-
Cause: Acfsinstall failed to uninstall the driver.
- ACFS-09330: Binary 'string' not installed.
-
Cause: A component that should have been installed was not installed.
- ACFS-09339: The environment variable ORACLE_HOME is not set.
-
Cause: This is an internal error.
- ACFS-09340: failed to install string driver.
-
Cause: Acfsinstall failed to install the driver.
- ACFS-09341: Binary 'string' not found.
-
Cause: One of the binaries that make up the ACFS package is missing.
- ACFS-09343: Unable to retrieve OS kernel version from module string.
-
Cause: Running modinfo against the usm driver failed.
- ACFS-09344: Missing directory: 'string'.
-
Cause: A required directory is not found on the system.
- ACFS-09345: Unable to create directory: 'string'.
-
Cause: Creation of a required directory failed.
- ACFS-09346: Unable to install file: 'string'.
-
Cause: Copying to the given destination failed.
- ACFS-09347: Unable to set permission bits (string) on: 'string'.
-
Cause: Setting the given permission bits failed.
- ACFS-09348: Unable to remove 'string'.
-
Cause: A previously installed file was unable to be removed.
- ACFS-09349: Unable to configure driver 'string'.
-
Cause: A driver was installed but add_drv failed to write a configuration file.
- ACFS-09350: Failed to create a symbolic link from 'string' to 'string'.
-
Cause: Creating a symbolic link failed.
- ACFS-09351: Unable to remove devlink entry for 'string'.
-
Cause: An entry for the driver was found in /etc/devlink.tab but it was not possible to remove the entry.
- ACFS-09352: Unable to write to 'string'.
-
Cause: A file required modifications but it was not possible to write to it.
- ACFS-09353: Unable to unconfigure string.
-
Cause: A call to rem_drv failed.
- ACFS-09354: Unable to create symlink: 'string'.
-
Cause: Ensure that a file with the same name does not already exist and the user has permission.
- ACFS-09355: Performing AIX setup failed with error code 'string'.
-
Cause: Running AIX initial setup has failed.
- ACFS-09356: Saving the AIX ODM changes for 'string' failed with error code 'string'.
-
Cause: Running the AIX savebase command failed.
- ACFS-09357: Getting the ASMADMIN group failed with error code 'string'.
-
Cause: Previous installation steps may have failed.
- ACFS-09358: Adding the AIX ODM entry for 'string' failed with error code 'string'.
-
Cause: Running the AIX odmadd command failed.
- ACFS-09360: The command aixsetup failed with error code 'string'.
-
Cause: Running the aixsetup script failed.
- ACFS-09361: Removing device 'string' failed with error code 'string'.
-
Cause: Running the device's undefine method failed.
- ACFS-09362: Warning: deleting the AIX ODM entry for 'string' failed with error code 'string'.
-
Cause: Running the odmdelete command failed.
- ACFS-09363: Opening the file /etc/vfs for read failed.
-
Cause: The /etc/vfs file is not readable.
- ACFS-09364: Opening the file /etc/vfs for append failed.
-
Cause: The /etc/vfs file is not writable.
- ACFS-09365: The directory 'string' is not being removed.
-
Cause: The directory was scheduled to be uninstalled, but it contained files that were not installed by acfsroot.
- ACFS-09366: Relative path for mount point 'string' is not supported.
-
Cause: Mount point was provided as a relative path.
- ACFS-09381: Modification of ADVM/ACFS drivers resource failed.
-
Cause: An attempt to modify the ACFS drivers resource resulted in an error.
- ACFS-09382: Modification of ADVM/ACFS drivers resource succeeded.
-
Cause: Informational.
- ACFS-09383: ADVM/ACFS uninstall cannot proceed
-
Cause: ADVM/ACFS uninstall cannot proceed due to an error. This message is accompanied by other message(s) providing details on the error.
- ACFS-09384: Invalid OS kernel variation 'string'.
-
Cause: The command found an OS kernel variation (e.g., "el5", etc) that it did not recognize as a valid ADVM/ACFS supported kernel.
- ACFS-09385: Usage: acfsroot version_check [-h] [-l location]
-
Cause: Syntax error or help [-h] option was passed.
- ACFS-09388: An absolute path name must be specified for the alternate location.
-
Cause: A relative path name to the distribution files was specified.
- ACFS-09389: ORACLE_HOME is not set to the location of the Grid Infrastructure home.
-
Cause: The ORACLE_HOME environment variable was not set correctly.
- ACFS-09390: The command 'string' returned unexpected output that may be important for system configuration:
-
Cause: One of the operating system commands used to configure the system returned an unexpected error. This message is accompanied by other message(s) providing details of the error.
- ACFS-09391: Checking for existing ADVM/ACFS installation.
-
Cause: Informational.
- ACFS-09392: Validating ADVM/ACFS installation files for operating system.
-
Cause: Informational.
- ACFS-09393: Verifying ASM Administrator setup.
-
Cause: Informational.
- ACFS-09394: The installed driver string has a build date of string which does not match the loaded kernel module build date of string.
-
Cause: The most likely cause is that an upgrade or patch procedure failed to unload the kernel module.
- ACFS-09395: Environment variable ODMDIR is not set, unable to proceed with system configuration.
-
Cause: Environment variable ODMDIR was not set.
- ACFS-09396: Environment variable ODMDIR specifies a nonexistent path, unable to proceed with system configuration.
-
Cause: Environment variable ODMDIR specified a nonexistent path.
- ACFS-09397: Modification of ADVM/ACFS registry resource failed.
-
Cause: An attempt to modify the ACFS registry resource resulted in an error.
- ACFS-09398: Modification of ADVM/ACFS registry resource succeeded.
-
Cause: Informational.
- ACFS-09399: Calling 'acfsroot install' to install compatible ADVM/ACFS drivers.
-
Cause: Informational.
- ACFS-09400: Could not open the Service Control Manager.
-
Cause: You do not have administrator access.
- ACFS-09401: Failed to install the driver.
-
Cause: The specified driver could not be installed.
- ACFS-09402: The driver file path is too long.
-
Cause: The path to the driver exceeded system limits.
- ACFS-09403: The driver can be either installed or removed, not both.
-
Cause: The /i and the /u switches are mutually exclusive.
- ACFS-09404: Specify either /i (install) or /u (uninstall).
-
Cause: Either /i to install or /u to uninstall the driver is required.
- ACFS-09405: Only one driver can be installed at a time.
-
Cause: Multiple drivers were specified with the /i option.
- ACFS-09406: Specify either /a (ADVM) or /o (ACFS) or /l (OKS).
-
Cause: The driver to be installed or uninstalled was not specified.
- ACFS-09407: Could not find driver "string" in the current directory.
-
Cause: The driver could not be found in the directory specified.
- ACFS-09408: The current directory is %"s".
-
Cause: Informational.
- ACFS-09409: CreateService failed (ERROR_SERVICE_EXISTS).
-
Cause: The driver service already exists.
- ACFS-09410: CreateService failed.
-
Cause: The driver service could not be created.
- ACFS-09411: CreateService succeeded.
-
Cause: Informational.
- ACFS-09412: The driver was installed successfully.
-
Cause: Informational.
- ACFS-09413: RegCreateKeyEx failed.
-
Cause: Failed to create a Windows registry key.
- ACFS-09414: RegSetValueEx (TypesSupported) failed.
-
Cause: Failed to set the Windows registry key.
- ACFS-09415: RegSetValueEx (EventMessageFile) failed.
-
Cause: Failed to set the Windows registry key.
- ACFS-09416: OpenService failed.
-
Cause: Could not start the driver.
- ACFS-09417: The driver was started successfully.
-
Cause: Informational.
- ACFS-09418: StartService failed (SERVICE_ALREADY_RUNNING).
-
Cause: Informational.
- ACFS-09419: StartService failed.
-
Cause: The driver failed to start.
- ACFS-09420: The driver is not currently installed on this node.
-
Cause: The driver is not installed to start.
- ACFS-09421: The driver is already installed on this node.
-
Cause: An attempt was made to install a driver that is already installed.
- ACFS-09422: The driver was removed successfully.
-
Cause: Informational.
- ACFS-09423: Failure trying to remove the driver, DeleteService failed.\n The driver service is pending deletion or is in an invalid state.
-
Cause: The driver could not be removed.
- ACFS-09424: The driver was stopped successfully.
-
Cause: Informational.
- ACFS-09425: The driver could not be stopped: StopService failed.
-
Cause: The driver could not be stopped.
- ACFS-09426: Unable to set the file attributes for file string.
-
Cause: The file attributes for the oject file could not be set.
- ACFS-09427: Failed to unload ADVM/ACFS drivers. A system reboot is recommended.
-
Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to an unanticipated condition or configuration. The operating system state did not allow the driver to be unloaded successfully.
- ACFS-09428: Failed to load ADVM/ACFS drivers. A system reboot is recommended.
-
Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to an unanticipated condition or configuration. The operating system state did not allow the driver to be unloaded successfully.
- ACFS-09429: Failed to install ADVM/ACFS files.
-
Cause: An unexpected condition has been detected. The files were previously verified to exist.
- ACFS-09430: ADVM/ACFS is not supported on this OS configuration: 'string'
-
Cause: Attempting to install or configure ADVM/ACFS failed because ADVM/ACFS device drivers have not been ported to this OS configuration.
- ACFS-09441: /i Install the driver
-
Cause: Syntax error.
- ACFS-09442: /u Uninstall the driver
-
Cause: Syntax error.
- ACFS-09443: /a Perform the operation for the ADVM driver
-
Cause: Syntax error.
- ACFS-09444: /o Perform the operation for the ACFS driver
-
Cause: Syntax error.
- ACFS-09445: /l Perform the operation for the Oracle Kernel Services (OKS) driver
-
Cause: Syntax error.
- ACFS-09446: path Path to the driver. If not specified,\n defaults to oracleadvm.sys, oracleacfs.sys, or\n oracleoks.sys in the current directory\n
-
Cause: Syntax error.
- ACFS-09450: Examples:
-
Cause: Informational.
- ACFS-09451: string /i /a (Install the ADVM driver from the current directory)
-
Cause: Informational.
- ACFS-09452: string /u /o (Uninstall the ACFS driver)
-
Cause: Informational.
- ACFS-09453: string /i /o c:\drivers\oracleacfs.sys (Install ACFS with the specified file)
-
Cause: Informational.
- ACFS-09454: Unable to delete the driver file string after stopping driver.
-
Cause: A call to the Windows DeleteFile function to delete the driver file failed.
- ACFS-09455: Unable to copy driver file string to the path string.
-
Cause: Could not copy the driver file to the specified directory because the Windows CopyFile function failed.
- ACFS-09456: An attempt to stop the driver string failed.
-
Cause: The driver could not be properly stopped; it is in an invalid state.
- ACFS-09457: The driver file does not match the driver chosen to install.
-
Cause: The driver file is not consistent with the driver option used.
- ACFS-09458: The Windows 'string' service is in an invalid state. The new driver cannot be installed.
-
Cause: An attempt to install the new driver failed because the existing service could not be stopped properly.
- ACFS-09459: ADVM/ACFS is not supported on this OS version: 'string'
-
Cause: Attempting to install or configure ADVM/ACFS failed because ADVM/ACFS device drivers have not been ported to this OS version.
- ACFS-09460: Missing symbols: 'string'
-
Cause: Informational.
- ACFS-09500: Location of Oracle Home is 'string' as determined from the internal configuration data
-
Cause: Informational.
- ACFS-09501: Location of Oracle Home is 'string' as determined from the ORACLE_HOME environment variable
-
Cause: Informational.
- ACFS-09502: Location of Oracle Home is 'string' as determined from the location of the Oracle library files
-
Cause: Informational.
- ACFS-09503: ADVM and ACFS driver media location is 'string'
-
Cause: Informational.
- ACFS-09504: Copying file 'string' to the path 'string'
-
Cause: Informational.
- ACFS-09505: Using acfsutil executable from location: 'string'
-
Cause: Informational.
- ACFS-09506: The files 'string' and 'string' are the same, not copying.
-
Cause: Informational. The file was not copied because the target and source point to the same file.
- ACFS-09507: Searching the alternative location: 'string'
-
Cause: Informational. The installation files were not found in the specified location. A likely path containing that location will be searched.
- ACFS-09508: ACFS installation aborted (component string).
-
Cause: Installation was aborted due to an error.
- ACFS-09509: ORACLE_BASE is not set.
-
Cause: This is an internal error.
- ACFS-09510: Disabling ACFS driver load due to lack of Spectre V2 retpoline mitigation support in driver (string).
-
Cause: The install failed because of kernel module incompatibility. The indicated kernel module is not compatible with the installed kernel.
- ACFS-09511: Warning: installing drivers with Spectre V2 retpoline mitigation capability, however, the system kernel is not retpoline capable.
-
Cause: The install failed because of a kernel module incompatibility. The installed kernel does not include 'retpoline' support.
- ACFS-09512: WARNING - Kernel does not have retpoline enabled.
-
Cause: ACFS install aborted due to lack of Spectre V2 retpoline mitigation.
- ACFS-09522: invalid compression operation string
-
Cause: An attempted compression operation was rejected because the specified command syntax was invalid.
- ACFS-09523: Invalid compression algorithm specified. The only valid choice is 'lzo'.
-
Cause: An attempted compression operation was rejected because the specification of the compression algorithm was invalid. The only algorithm currently supported is 'lzo'.
- ACFS-09524: unable to modify volume compression configuration on the local node
-
Cause: A request to modify the compression configuration of the volume failed. This message is accompanied by other messages providing details on the error.
- ACFS-09525: Only regular files may be compressed.
-
Cause: An attempted compression operation was rejected because the specified pathname did not specify a regular file.
- ACFS-09526: unable to obtain file compression information
-
Cause: An attempt to read the compression information for the file failed. This message is accompanied by other messages providing details on the error.
- ACFS-09535: The requested compression configuration operation failed on a remote node.
-
Cause: An attempt to change the compression configuration for the volume failed on a remote node in the cluster. The probable cause is a lack of necessary OS resources.
- ACFS-09536: The Oracle ADVM compatibility attribute for the disk group is less than the required version 12.2 for 'acfsutil compress' commands.
-
Cause: The 'acfsutil compress' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-09539: 'acfsutil compress' commands are not supported on this OS configuration: 'string'
-
Cause: The 'acfsutil compress' command was rejected because the current version of the OS does not support compression.
- ACFS-09542: The command was not attempted because asynchronous compression is very active on file 'string' .
-
Cause: The 'acfsutil defrag file' command was unable to make progress because the file was busy being modified by the asynchronous compression mechanism.
- ACFS-09544: Invalid files or directories found: 'string'
-
Cause: During verification of the directory from which ACFS installs kernel modules (usm), unexpected files or directories were found.
- ACFS-09545: Verification error: kernel module 'string' is incompatible with the installed kernel version 'string'. It is compatible with kernel version 'string'.
-
Cause: An attempted command failed because of kernel module incompatibility. The version of the indicated kernel module is not compatible with the installed kernel.
- ACFS-09546: Incorrect permissions for file 'string'. Expected: (user=string, group=string, mode=string), Found: (user=string, group=string, mode=string)
-
Cause: An attempt to install ACFS drivers failed because the indicated permissions were incorrect on the indicated file.
- ACFS-09550: An error occurred while retrieving the kernel and command versions.
-
Cause: An attempt to retrieve the ACFS driver version information failed because an error occurred when acfsdriverstate command invoked the command 'acfsutil version -v'.
- ACFS-09551: Command file '/sbin/weak-modules' does not exist or it is not an executable.
-
Cause: An attempt to check Kernel Application Binary Interface (KABI) compatibility failed because the command '/sbin/weak-modules' could not be found, or the current user did not have permission to execute it. This indicates a problem with the Linux installation.
- ACFS-09552: Command '/sbin/weak-modules' returned a potential compatibility issue. For more details execute the command 'string'.
-
Cause: The command '/sbin/weak-modules' found incompatibilities between the running kernel and the ACFS/ADVM drivers.
- ACFS-09553: Operating System: string
-
Cause: Informational.
- ACFS-09554: Machine Architecture: string
-
Cause: Informational.
- ACFS-09555: Operating system name and information: string
-
Cause: Informational.
- ACFS-09556: Release package: string
-
Cause: Informational.
- ACFS-09557: Version: string
-
Cause: Informational.
- ACFS-09558: Variable _ORA_USM_NOT_SUPPORTED is defined: string
-
Cause: Informational.
- ACFS-09559: Running in a local container: string
-
Cause: Informational.
- ACFS-09560: Configuration file string in the /boot directory is accessible.
-
Cause: Informational.
- ACFS-09561: USM Drivers are KABI Compatible.
-
Cause: Informational.
- ACFS-09562: Install Path: string
-
Cause: Informational.
- ACFS-09563: storage interest tracking: ENABLED
-
Cause: Informational.
- ACFS-09564: storage interest tracking: DISABLED
-
Cause: Informational.
- ACFS-09565: storage interest tracking: ENABLED
-
Cause: Informational.
- ACFS-09566: storage interest tracking: DISABLED
-
Cause: Informational.
- ACFS-09600: Usage: string [-h] {-nfsv4lock} {-volume <enabled_volume_device>} [-force]
-
Cause: Informational.
- ACFS-09601: Usage: string [-h] {-nfsv4lock}
-
Cause: Informational.
- ACFS-09602: Installation cannot proceed: path 'string' is mounted or it is a symlink.
-
Cause: An attempt to validate the path found that the indicated path was mounted or was a symlink.
- ACFS-09603: The script will do the following actions:
-
Cause: Informational.
- ACFS-09604: - Update the operating system startup procedure so that NFS does not automatically start.
-
Cause: Informational.
- ACFS-09605: Management of the NFS daemons will be moved to Oracle Clusterware.
-
Cause: Informational.
- ACFS-09606: - Format the volume: string.
-
Cause: Informational.
- ACFS-09607: - Create an ACFS resource for the file system.
-
Cause: Informational.
- ACFS-09608: - Mount the ACFS file system on 'string'.
-
Cause: Informational.
- ACFS-09609: Continue the installation? [1=yes,2=no]:
-
Cause: Informational.
- ACFS-09610: Error - the ACFS resource for the specified file system is already in use.
-
Cause: An attempt to use the specified volume found that it was in use by an ACFS file system resource.
- ACFS-09611: Starting NFS Service.
-
Cause: Informational.
- ACFS-09612: Stopping NFS Service.
-
Cause: Informational.
- ACFS-09613: Restarting NFS Service.
-
Cause: Informational.
- ACFS-09614: Formatting the volume device.
-
Cause: Informational.
- ACFS-09615: NFS_PATH is not supported.
-
Cause: Informational.
- ACFS-09620: 'acfsutil scrub' is not implemented.
-
Cause: An attempt to invoke the command 'acfsutil scrub' was rejected because the version of acfsutil that was used did not include 'scrub' functionality.
- ACFS-09660: Data has been lost in the filesystem.
-
Cause: The ACFS Scrubber determined that data has been lost in one or more files in the file system being scrubbed. This may result in ACFS data needing to be restored from backup. This could be the result of a storage problem, a configuration issue or a software bug.
- ACFS-09670: Failure to initialize the ACFS Scrubber.
-
Cause: An attempt to initialize the ACFS scrubber resulted in an internal error.
- ACFS-09671: Invalid trace value specified. Must be between number (terse) and number (verbose).
-
Cause: An attempt to initialize the trace level failed because an invalid value was specified.
- ACFS-09672: Invalid I/O load specified. Must be between number (lowest) and number (highest).
-
Cause: An attempt to initialize the I/O load failed because an invalid value was specified.
- ACFS-09673: Invalid file extent logging value specified. Must be between 0 and 3.
-
Cause: An attempt to initialize the file extent logging level failed because an invalid value was specified.
- ACFS-09674: The filesystem is offline.
-
Cause: An attempt to scrub the contents of the filesystem was unsuccessful because the filesystem was offline.
- ACFS-09675: The ACFS Scrubber was interrupted.
-
Cause: An interrupt signal was received by the Scrubber to abort scrubbing.
- ACFS-09676: | NO DATA |
-
Cause: No data is being printed in this field because the ACFS Scrubber is running as a background job.
- ACFS-09801: Failure to access Oracle Cluster Registry (OCR).
-
Cause: An attempt to access the Oracle Cluster Registry encountered an internal error.
- ACFS-09802: Failure to initialize the credentials context.
-
Cause: An attempt to initialize the Oracle Cluster Registry credentials context encountered an internal error.
- ACFS-09803: Failure to initialize the credentials domain for the 'string' cluster.
-
Cause: An attempt to create the Oracle Cluster Registry credentials domain for the indicated cluster encountered an internal error.
- ACFS-09804: Failure to create the credentials for the 'string' cluster.
-
Cause: An attempt to create the credentials for the indicated cluster encountered an internal error.
- ACFS-09805: Failure to export the credentials for the 'string' cluster.
-
Cause: Unable to export the credentials for the indicated cluster to the specified Cluster Manifest File.
- ACFS-09807: Could not find the 'string' credential domain.
-
Cause: The ACFSREMOTE credential domain was not found in the Oracle Cluster Registry (OCR).
- ACFS-09809: No Member Clusters have been registered.
-
Cause: An attempt to list the registered clusters returned no results because no Member Clusters have been registered.
- ACFS-09810: No credentials were found for the 'string' cluster name.
-
Cause: An attempt to list the credentials for the indicated cluster failed as it does not exist in the ACFSREMOTE domain.
- ACFS-09812: Unable to obtain the credential set for the 'string' cluster.
-
Cause: At attempt to get the credential set for the specified cluster encountered an internal error.
- ACFS-09813: Unable to add a new credential pair to the credential set of the 'string' cluster.
-
Cause: An attempt to add the new credentials for the specified cluster encountered an internal error.
- ACFS-09814: Unable to set the member cluster version.
-
Cause: An attempt to write the cluster version to the Oracle Cluster Registry (OCR) encountered an internal error.
- ACFS-09816: Unable to determine the version of member cluster 'string'.
-
Cause: An attempt to read the cluster version for the indicated cluster from the Oracle Cluster Registry (OCR) encountered an internal error.
- ACFS-09821: Unable to access the specified Cluster Manifest File.
-
Cause: An attempt to read the Cluster Manifest File provided failed. ACFS Remote Member Cluster registration requires a Cluster Manifest File with valid ASM credentials.
- ACFS-09822: The provided cluster name 'string' does not match the name of the Cluster Manifest File's cluster source 'string'.
-
Cause: There was a mismatch in the name provided and the name of the cluster in the Cluster Manifest File.
- ACFS-09823: Unable to find the ASM attributes section in the provided Cluster Manifest File.
-
Cause: The ASM_attributes section was not found in the Cluster Manifest File provided.
- ACFS-09824: Unable to find the cluster global unique ID in the provided Cluster Manifest File.
-
Cause: The cluster global unique ID for the specified cluster was not found in the Cluster Manifest File provided.
- ACFS-09825: Unable to find the cluster name in the provided Cluster Manifest File.
-
Cause: The cluster name for the specified cluster was not found in the Cluster Manifest File provided.
- ACFS-09826: Unable to import the credentials from the specified file.
-
Cause: An attempt to import the credentials from the Member Cluster Data File failed.
- ACFS-09827: ACFS Remote credentials were not found in the provided Cluster Manifest File.
-
Cause: The ACFS Remote section was not found in the provided Cluster Manifest File.
- ACFS-09828: Command not permitted on cluster class 'string'.
-
Cause: An attempt to execute the command 'acfsutil cluster credential' with the specified options was rejected because the local cluster was of the indicated class. With the options specified this command may be executed only from a node in a Domain Services Cluster.
- ACFS-09829: unable to retrieve the current cluster class
-
Cause: An attempt to execute 'acfsutil cluster credential' failed because the cluster class could not be obtained from the OCR. Possibly the OCR is unavailable or this may be an internal error.
- ACFS-09830: The version string provided is invalid.
-
Cause: The expected version string input was not of a valid format.
- ACFS-09831: Creation of ACFS Remote credentials is not supported for cluster version string. The minimum version is string
-
Cause: The ACFS Remote credentials could not be created because this functionality requires a minimum cluster version of 12.2.0.2.0.
- ACFS-09849: Configuration error: iscsid.service is not running.
-
Cause: 'systemctl status iscsid' returned inactive.
- ACFS-09890: Unable to delete Oracle Cluster Registry subkey 'string' error: string
-
Cause: An attempt to delete an advmutil transport or session failed because an attempt to delete the indicated Oracle Cluster Registry subkey failed with the indicated error.
- ACFS-09891: Unable to open Oracle Cluster Registry subkey 'string' error: string
-
Cause: An attempt to open an advmutil transport or session failed because an attempt to open the indicated Oracle Cluster Registry subkey failed with the indicated error.
- ACFS-09892: Unable to set Oracle Cluster Registry subkey 'string' in 'string' error: string
-
Cause: An attempt to set an advmutil transport or session failed because an attempt to set the indicated Oracle Cluster Registry subkey failed with the indicated error.
- ACFS-09893: Unable to enumerate Oracle Cluster Registry subkey 'string' error: string
-
Cause: An attempt to enumerate an advmutil transport or session failed because an attempt to enumerate the indicated Oracle Cluster Registry subkey failed with the indicated error.
- ACFS-09894: Invalid Oracle Cluster Registry subkey 'string' in path 'string. error: string'
-
Cause: An attempt to access an advmutil transport or session failed because an attempt to access the indicated Oracle Cluster Registry subkey failed with the indicated error.
- ACFS-09895: Unable to create Oracle Cluster Registry subkey 'string' error: string
-
Cause: An attempt to create an advmutil transport or session failed because an attempt to create the indicated Oracle Cluster Registry subkey failed with the indicated error.
- ACFS-09896: Unable to retrieve Oracle Cluster Registry subkey value 'string' error: string
-
Cause: An attempt to retrieve an advmutil transport or session failed because an attempt to retrieve the indicated Oracle Cluster Registry subkey failed with the indicated error.
- ACFS-09897: unable to retrieve the ASM Administrator name
-
Cause: An attempt to retrieve the ASM Administrator name from the ADVM control device failed.
- ACFS-10101: Authentication failed.
-
Cause: The specified ACFS Security administrator password was wrong.
- ACFS-10120: ACFS Encryption not initialized.
-
Cause: ACFS Encryption was not initialized.
- ACFS-10149: Realm description cannot exceed number characters
-
Cause: Realm description cannot exceed 1023 characters
- ACFS-10150: Realm description not specified within double quotation marks
-
Cause: Invalid description specified for realm.
- ACFS-10151: Unmatched single quote or double quote.
-
Cause: Matching quote was not found.
- ACFS-10152: Realm name cannot exceed number characters.
-
Cause: Realm name length exceeded 255 characters.
- ACFS-10153: Realm 'string' not found on mount point 'string'.
-
Cause: Realm was not found on mount point.
- ACFS-10154: Failed to create realm 'string' on mount point 'string'.
-
Cause: Internal error.
- ACFS-10155: Realm 'string' created.
-
Cause: Realm was created.
- ACFS-10156: Failed to destroy realm 'string' on mount point 'string'.
-
Cause: Internal error.
- ACFS-10157: Realm 'string' destroyed.
-
Cause: Realm was destroyed.
- ACFS-10158: Improper value specified for -l option.
-
Cause: Invalid argument format was specified for -l option.
- ACFS-10159: The command requires at least one of the options -u, -G, -l, -f, or -e.
-
Cause: None of the options -u, -G, -l, -f, or -e were specified with this command.
- ACFS-10160: Failed to add user 'string' to the realm 'string'.
-
Cause: Internal error.
- ACFS-10161: Added user 'string' to realm 'string'.
-
Cause: User was added to realm.
- ACFS-10162: Failed to add group 'string' to realm 'string'.
-
Cause: Internal error.
- ACFS-10163: Added group 'string' to the realm 'string'.
-
Cause: Group was added to the realm.
- ACFS-10164: Failed to add filter 'string:string' to the realm 'string'.
-
Cause: Internal error.
- ACFS-10165: Added filter 'string:string' to the realm 'string'.
-
Cause: Filter was added to the realm.
- ACFS-10166: Failed to add 'string' to the realm 'string'.
-
Cause: Internal error.
- ACFS-10167: Added 'string' to the realm 'string'.
-
Cause: Pathname was added to the realm.
- ACFS-10168: Failed to turn encryption ON for realm 'string'.
-
Cause: Internal error.
- ACFS-10169: Encryption turned ON for realm 'string'.
-
Cause: Encryption was turned ON for realm.
- ACFS-10170: Failed to delete user 'string' from realm 'string'.
-
Cause: Internal error.
- ACFS-10171: Deleted user 'string' from realm 'string'.
-
Cause: User was deleted from realm.
- ACFS-10172: Failed to delete group 'string' from the realm 'string'.
-
Cause: Internal error.
- ACFS-10173: Deleted group 'string' from realm 'string'.
-
Cause: Group was deleted from realm.
- ACFS-10174: Failed to delete filter 'string:string' from the realm 'string'.
-
Cause: Internal error.
- ACFS-10175: Deleted filter 'string:string' from realm 'string'.
-
Cause: Filter was deleted from realm.
- ACFS-10176: Failed to delete 'string' from realm 'string'.
-
Cause: Internal error.
- ACFS-10177: Deleted 'string' from realm 'string'.
-
Cause: Pathname was deleted from realm.
- ACFS-10178: Failed to turn encryption OFF for realm 'string'.
-
Cause: Internal error.
- ACFS-10179: Encryption turned OFF for realm 'string'.
-
Cause: Encryption was turned OFF for realm.
- ACFS-10180: Failed to get realm files or directories for realm 'string'.
-
Cause: Internal error.
- ACFS-10181: Failed to get groups for realm 'string'.
-
Cause: Internal error.
- ACFS-10182: Failed to get users for realm 'string'.
-
Cause: Internal error.
- ACFS-10183: Failed to get filters for realm 'string'.
-
Cause: Internal error.
- ACFS-10184: Failed to get realm encryption attributes of realm 'string'.
-
Cause: Internal error.
- ACFS-10185: '-e' requires both '-a' and '-k'.
-
Cause: At least one of the options -a or -k is missing with -e option.
- ACFS-10186: Realm 'string' already exists on mount point 'string'.
-
Cause: Realm was already found on mount point.
- ACFS-10187: Failed to get all realms on mount point 'string'.
-
Cause: Internal error.
- ACFS-10188: Attributes of realm 'string' retrieved.
-
Cause: Realm attributes were retrieved.
- ACFS-10189: Failed to update attributes of realm 'string'.
-
Cause: Internal error.
- ACFS-10190: Updated attributes of realm 'string'.
-
Cause: Updated realm attributes.
- ACFS-10195: None of the options -a, -d, are specified with the edit command.
-
Cause: An attempt to execute the command 'ruleset edit' was rejected because specifying one of -a or -d was mandatory.
- ACFS-10204: The rule 'string' will not be added or deleted.
-
Cause: An attempt to execute the command 'ruleset edit' was rejected because the indicated rule name was specified with both the -a and the -d option.
- ACFS-10205: The option -f should be specified at the end after all other options.
-
Cause: An attempt to edit the realm was rejected because -f was not supplied as the last argument of the command.
- ACFS-10206: File or directory 'string' does not belong to an ACFS file system
-
Cause: A File or directory specified in 'acfsutil sec realm add/delete' command did not belong to an ACFS file system.
- ACFS-10221: Rule name cannot exceed number characters.
-
Cause: Rule name length exceeded 255 characters.
- ACFS-10223: Invalid rule type is specified.
-
Cause: Invalid rule type was provided on the command line with '-t'.
- ACFS-10224: Rule type 'username', 'application' or 'hostname' must have only one rule value.
-
Cause: An incorrect number of arguments were provided with rule type 'username', 'application' or 'hostname'.
- ACFS-10225: Rule type 'time' must have both start time and end time separated by a comma.
-
Cause: Either the start time or end time was not provided.
- ACFS-10226: '-o' requires either 'ALLOW' or 'DENY'.
-
Cause: A valid rule option was not provided.
- ACFS-10227: Failed to perform rule create operation on 'string'.
-
Cause: Internal error.
- ACFS-10228: Rule 'string' is created.
-
Cause: Rule was created.
- ACFS-10229: Rule 'string' not found.
-
Cause: Rule was not found.
- ACFS-10230: Failed to perform rule edit operation on 'string'.
-
Cause: Internal error.
- ACFS-10231: Rule 'string' updated.
-
Cause: Rule was updated.
- ACFS-10232: Failed to destroy rule 'string'.
-
Cause: Internal error
- ACFS-10233: Rule 'string' destroyed.
-
Cause: Rule was destroyed.
- ACFS-10234: Failed to get rule 'string' information.
-
Cause: Internal error.
- ACFS-10235: Rule 'string' already exists.
-
Cause: Rule was already found on mount point.
- ACFS-10236: Time format string must be HH:MM:SS.
-
Cause: The time format provided was not formatted as 'HH:MM: SS', where HH translates to hours, MM to minutes and SS to seconds.
- ACFS-10237: Rule type 'string' specified does not match the actual type 'string' of rule 'string'
-
Cause: The rule type specified did not match the actual rule typed.
- ACFS-10238: Failed to get all rules on mount point 'string'.
-
Cause: Internal error.
- ACFS-10239: Failed to get information for rule 'string'.
-
Cause: Internal error.
- ACFS-10240: Cannot destroy rule 'string'. The rule is in use by one or more rule sets.
-
Cause: The rule was being used in one or more rule set(s) in the file system.
- ACFS-10241: Rule set name cannot exceed number characters.
-
Cause: Rule set name length exceeded 255 characters.
- ACFS-10242: '-o' requires either ALL_TRUE or ANY_TRUE.
-
Cause: The rule set option was not set to either ALL_TRUE or ANY_TRUE.
- ACFS-10243: Failed to create rule set 'string' on mount point 'string'.
-
Cause: Internal error
- ACFS-10244: Rule set 'string' is created.
-
Cause: Rule set was created.
- ACFS-10245: Rule set 'string' not found on mount point 'string'.
-
Cause: Rule set was not found on mount point.
- ACFS-10246: Failed to add rule 'string' to the rule set 'string'.
-
Cause: Internal error.
- ACFS-10247: Added rule 'string' to the rule set 'string'.
-
Cause: Rule was added to the rule set.
- ACFS-10248: Failed to delete rule 'string' from the rule set 'string'.
-
Cause: Internal error.
- ACFS-10249: Deleted rule 'string' from rule set 'string'.
-
Cause: Rule was deleted from the rule set.
- ACFS-10250: Failed to destroy rule set 'string' on mount point 'string'.
-
Cause: Internal error.
- ACFS-10251: Rule set 'string' destroyed.
-
Cause: Rule set was destroyed.
- ACFS-10252: Failed to get rules for rule set 'string'.
-
Cause: Internal error.
- ACFS-10253: Failed to get list of command rules.
-
Cause: Internal error.
- ACFS-10254: Rule set 'string' already exists.
-
Cause: Rule set was already found on mount point.
- ACFS-10255: Rule 'string' already exists in rule set 'string'.
-
Cause: Rule was already part of rule set.
- ACFS-10256: Rule 'string' is not found in rule set 'string'.
-
Cause: Rule was not found in the rule set.
- ACFS-10257: Failed to get all rule sets on mount point 'string'.
-
Cause: Internal error.
- ACFS-10258: Failed to get information for rule set 'string'.
-
Cause: Internal error.
- ACFS-10259: Invalid command rule 'string'.
-
Cause: Invalid command rule was specified.
- ACFS-10260: File object 'string' and the realm 'string' should be in the same file system.
-
Cause: File object was not in the same file system as that of the realm.
- ACFS-10261: Cannot destroy rule set 'string'. The rule set is in use by one or more realms.
-
Cause: The rule set is being used in filter(s) that are part of one or more realms in the file system.
- ACFS-10262: Application path name for rule type 'application' cannot exceed 'number' characters.
-
Cause: Application path name for rule type 'application' exceeded 511 characters
- ACFS-10263: Host name for rule type 'hostname' cannot exceed 'number' characters.
-
Cause: Host name for rule type 'hostname' exceeded 255 characters.
- ACFS-10264: Invalid value for rule type 'string' as the given path name 'string' is a symbolic link
-
Cause: Path name provided for rule type 'application' was a symbolic link. Symbolic links are not supported for rule type 'application'.
- ACFS-10271: Encryption algorithm can be only 'AES'.
-
Cause: The encryption algorithm provided was not 'AES'.
- ACFS-10272: Key length must be either 128, 192, or 256.
-
Cause: The key length specified with '-k' was not 128, 192 or 256.
- ACFS-10273: Failed to set the encryption parameter on realm 'string'.
-
Cause: Internal error.
- ACFS-10274: Failed to update rule set option.
-
Cause: Internal error.
- ACFS-10275: Failed to get rule sets for mount point 'string'.
-
Cause: Internal error.
- ACFS-10276: Rule set 'string' option updated to 'string'.
-
Cause: Rule set option updated.
- ACFS-10277: '-e' requires either ON or OFF.
-
Cause: The realm encryption status specified with '-e' was not 'on' or 'off'
- ACFS-10278: Encryption parameters are not set on the file system, realm encryption is unavailable.
-
Cause: The encryption parameters were not set on the file system.
- ACFS-10284: Failed to get security information for 'string'.
-
Cause: Internal error.
- ACFS-10285: Pathname 'string' does not exist.
-
Cause: Specified pathname was not found.
- ACFS-10286: User 'string' does not exist.
-
Cause: User was not found.
- ACFS-10287: Group 'string' does not exist.
-
Cause: Group was not found
- ACFS-10288: User 'string' already added to the realm 'string'.
-
Cause: User was already added to the realm.
- ACFS-10289: Group 'string' already added to the realm 'string'.
-
Cause: Group was already added to the realm
- ACFS-10290: Realm filter 'string' already added to the realm 'string'.
-
Cause: Filter was already added to the realm.
- ACFS-10291: Pathname 'string' already added to the realm 'string'.
-
Cause: Pathname was already added to the realm.
- ACFS-10292: User 'string' is not part of the realm 'string'.
-
Cause: User was not part of the realm.
- ACFS-10293: Group 'string' is not part of the realm 'string'.
-
Cause: Group was not part of the realm.
- ACFS-10294: Pathname 'string' is not part of the realm 'string'.
-
Cause: Pathname was not part of the realm.
- ACFS-10295: Realm filter 'string' is not part of the realm 'string'.
-
Cause: Filter was not part of the realm.
- ACFS-10296: Realm filter 'string:string' could not be added to the realm 'string'.
-
Cause: The filter was not added because the filter with command rule 'ALL' was already part of the realm.
- ACFS-10297: Realm filter 'ALL' could not be added since another filter exists in realm 'string'.
-
Cause: Filter 'ALL' was not added because another filter existed in the realm .
- ACFS-10298: User name cannot exceed number characters.
-
Cause: User name length exceeded 64 characters.
- ACFS-10299: Group name cannot exceed number characters.
-
Cause: Group name length exceeded 64 characters.
- ACFS-10322: System realm 'SYSTEM_SecurityMetadata' created.
-
Cause: System realm 'SYSTEM_SecurityMetadata' was created.
- ACFS-10323: System realm 'SYSTEM_Logs' created.
-
Cause: System realm 'SYSTEM_Logs' was created.
- ACFS-10324: Rulesets cannot be cloned before cloning rules on mount point 'string'.
-
Cause: Rule sets were not cloned because some rules were not present on mount point.
- ACFS-10342: System realm 'SYSTEM_BackupOperators' created.
-
Cause: System realm 'SYSTEM_BackupOperators' was created.
- ACFS-10350: Incorrect password was entered in all attempts to open the encryption key store. Encrypted files will not be available.
-
Cause: Incorrect password was entered in all attempts to open the encryption key store during the mount command.
- ACFS-10355: System realm 'SYSTEM_Antivirus' created.
-
Cause: System realm 'SYSTEM_Antivirus' was created.
- ACFS-10356: waiting for the operation to complete...
-
Cause: Informational.
- ACFS-10357: System realm 'SYSTEM_Audit' created.
-
Cause: Informational.
- ACFS-10359: Failed to create system realm 'string'
-
Cause: An attempt to create a realm with the specified name was rejected because the specified name was a system realm name. System realms get created as the result of some ACFS Security operations and cannot be explicitly created by the ACFS Security Administrator.
- ACFS-10360: Failed to create system ruleset 'string'
-
Cause: An attempt to create a ruleset with the specified name was rejected because the specified name was a system ruleset name. System rulesets get created as the result of some ACFS Security operations and cannot be explicitly created by the ACFS Security Administrator.
- ACFS-10361: Failed to create system rule 'string'
-
Cause: An attempt to create a rule with the specified name was rejected because the specified name was a system rule name. System rules get created as the result of some ACFS Security operations and cannot be explicitly created by the ACFS Security Administrator.
- ACFS-10400: Encryption is set on mount point 'string'.
-
Cause: Encryption was set on mount point.
- ACFS-10401: Failed to set encryption parameters on mount point 'string'.
-
Cause: Internal error.
- ACFS-10402: Encryption turned 'string' on 'string'.
-
Cause: Encryption was turned either ON or OFF on the pathname.
- ACFS-10403: Failed to turn encryption 'string' on 'string'.
-
Cause: Internal error.
- ACFS-10405: Failed to get encryption information on 'string'.
-
Cause: Internal error.
- ACFS-10406: Re-key operation is complete on 'string'.
-
Cause: Re-key operation was complete on the pathname.
- ACFS-10407: Failed to perform re-key operation on 'string'.
-
Cause: Internal error.
- ACFS-10410: encryption is already disabled on the file system
-
Cause: Encryption was already disabled on the file system.
- ACFS-10411: encryption is already enabled on the file system
-
Cause: Encryption was already enabled on the file system.
- ACFS-10412: Encryption parameters were not provided, using default algorithm (string) and key length (number).
-
Cause: Encryption parameters were not provided.
- ACFS-10413: The ADVM compatibility attribute for the diskgroup must be set to version 11.2.0.2.0 to allow the acfsutil encryption and security commands.
-
Cause: The ADVM compatibility attribute has not been upgraded to version 11.2.0.2.0 or beyond.
- ACFS-10414: Encryption has been initialized for the cluster.
-
Cause: An administrator initialized encryption for the cluster.
- ACFS-10415: File system level encryption is on, file level encryption operations are not allowed
-
Cause: A file level encryption operation was attempted while file system level encryption was enabled. File level encryption operations are not allowed when file system level encryption is turned on.
- ACFS-10416: File is realm secured\n
-
Cause: An encryption operation was attempted on a realm secured file and no action was performed. A realm secured file can only be encrypted and decrypted by changing the encryption parameters of containing realm(s) or by deleting the file from all realms.
- ACFS-10419: Skipping directory 'string' because it does not belong to the file system mounted on 'string'
-
Cause: The directory does not belong to the specified mounted ACFS file system.
- ACFS-10420: Encryption parameters specified for realm 'string' match existing settings.
-
Cause: An attempt to set encryption parameters for a realm specified values the same as those already set.
- ACFS-10421: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to allow acfsutil encryption commands.
-
Cause: An adminstrator attempted an encryption set or volume level rekey operation, but the ADVM compatibility attribute had not been upgraded to a supported version.
- ACFS-10422: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to allow 'acfsutil sec' commands.
-
Cause: A security adminstrator attempted an ACFS Security operation, but the ADVM compatibility attribute had not been upgraded to a supported version.
- ACFS-10423: This encryption operation is not allowed on a standby file system.
-
Cause: An encryption operation that is not allowed on a standby file system was attempted. The following acfsutil encryption commands are not allowed on a standby file system: 'encr set', 'encr on', 'encr off', and 'encr rekey'.
- ACFS-10424: This ACFS Security operation is not allowed on a standby file system.
-
Cause: An ACFS Security operation that is not allowed on a standby file system was attempted. The following acfsutil security commands are not allowed on a standby file system: 'sec prepare', 'sec save/load/enable/disable', 'sec realm create/destroy/clone/add/delete', 'sec rule create/destroy/clone/edit', and 'sec ruleset create/destroy/clone/edit'
- ACFS-10450: Unauthorized encryption operation attempted on 'string'.
-
Cause: A user attempted an encryption operation on the given file and the operation was denied.
- ACFS-10451: File level encryption operation attempted on realm secured file 'string'.
-
Cause: A user attempted to perform a file level encryption command on a realm secured file and the operation was denied.
- ACFS-10452: Failed to decrypt 'string'.
-
Cause: Internal error.
- ACFS-10453: Unable to get encryption parameters for the file system mounted on 'string'.
-
Cause: Internal error.
- ACFS-10454: File system level encryption turned on for mount point 'string'.
-
Cause: A system administrator enabled file system level encryption.
- ACFS-10455: New volume encryption key generated for mount point 'string'.
-
Cause: A system administrator updated the volume encryption key for the mount point. The file encryption keys for all encrypted files on the file system were re-encrypted using the new volume encryption key.
- ACFS-10456: New file encryption key generated for file 'string'.
-
Cause: A system administrator updated the volume encryption key for the file. The data in the file was re-encrypted using the new key.
- ACFS-10457: New file encryption keys generated for all files in directory 'string'.
-
Cause: A system administrator updated the volume encryption key for the files in the given directory. The file contents were re-encrypted using the new key.
- ACFS-10458: Encryption turned off for path 'string'.
-
Cause: A user successfully decrypted a file or directory.
- ACFS-10459: Encryption turned off for directory 'string' and its contents.
-
Cause: A user successfully decrypted a directory and its contents.
- ACFS-10460: File system level encryption turned off for mount point 'string'.
-
Cause: A system administrator disabled file system level encryption.
- ACFS-10461: Encryption turned on for path 'string'.
-
Cause: A user successfully encrypted a file or directory.
- ACFS-10462: Encryption turned on for directory 'string' and its contents.
-
Cause: A user successfully encrypted a directory and its contents.
- ACFS-10463: Skipping file 'string' because it does not belong to the file system mounted on 'string'
-
Cause: The file does not belong to the specified mounted ACFS file system.
- ACFS-10464: ACFS Encryption operations are not allowed on files of this type.
-
Cause: An attempt was made to encrypt, decrypt, or rekey a file of one of the following Oracle file types: data, control, online redo log, archive log, backup, incremental backup, or flashback.
- ACFS-10465: FS-level encryption parameters have been set to:
-
Cause: Informational.
- ACFS-10466: Using user-provided parameters: algorithm string, key length number bytes
-
Cause: Informational.
- ACFS-10467: Using FS-level parameters: algorithm string, key length number bytes
-
Cause: Informational.
- ACFS-10468: Encryption has been enabled on mount point 'string'.
-
Cause: Informational.
- ACFS-10469: Rekeying file/directory 'string'...
-
Cause: Informational.
- ACFS-10470: Encrypting file/directory 'string'...
-
Cause: Informational.
- ACFS-10471: Path: string
-
Cause: Informational.
- ACFS-10472: Re-encrypting FEK for mount point 'string'...
-
Cause: Informational.
- ACFS-10473: Re-encrypting FEK for file/directory 'string'...
-
Cause: Informational.
- ACFS-10475: Failed to rekey file/directory 'string'.
-
Cause: An unexpected error occured while attempting to rekey the indicated file. This is an internal error.
- ACFS-10476: Algorithm AES number-bit, Key length number bytes
-
Cause: Informational.
- ACFS-10477: Decrypting file/directory 'string'...
-
Cause: Informational.
- ACFS-10478: Encryption has been disabled on mount point 'string'.
-
Cause: Informational.
- ACFS-10479: File is larger than 128M, cannot encrypt, decrypt or rekey.
-
Cause: An attempt was made to encrypt, decrypt or rekey a file larger than 128M in size.
- ACFS-10500: Pathname cannot exceed number characters.
-
Cause: Pathname length exceeds 255 characters.
- ACFS-10541: Wallet 'string' creation failed [error : number string].
-
Cause: An attempt to create the indicated wallet failed with the indicated error. This is an internal error.
- ACFS-10542: Wallet 'string' save failed [error : number string].
-
Cause: An attempt to save the indicated wallet failed with the indicated error. This is an internal error.
- ACFS-10543: Wallet 'string' open failed [error : number string].
-
Cause: An attempt to open the indicated wallet failed with the indicated error. This is an internal error.
- ACFS-10548: Wallet initialization failed [error : number string].
-
Cause: An attempt to initialize the wallet failed with the indicated error. This is an internal error.
- ACFS-10549: Wallet termination failed [error : number string].
-
Cause: An attempt to terminate the wallet failed with the indicated error. This is an internal error.
- ACFS-10550: Security wallet created.
-
Cause: Security wallet was created.
- ACFS-10551: Security wallet creation failed.
-
Cause: An attempt to create the security wallet failed with the indicated error. This is an internal error.
- ACFS-10552: Security wallet save failed.
-
Cause: An attempt to save the security wallet failed with the indicated error. This is an internal error.
- ACFS-10553: Security wallet open failed.
-
Cause: An attempt to open the security wallet failed with the indicated error. This is an internal error.
- ACFS-10557: Security wallet could not be owned by 'string'.
-
Cause: An attempt to change the ownership of the security wallet failed. This is an internal error.
- ACFS-10559: Insufficient privileges to switch to %0!s '%1!s'.
-
Cause: An attempt to change the user or group membership privilege for a process failed because the user who was executing the command did not have sufficient privileges.
- ACFS-10564: Incorrect password for encryption key store.
-
Cause: An incorrect password was entered while opening the encryption key store.
- ACFS-10565: Encryption key store created.
-
Cause: Encryption key store was created.
- ACFS-10566: Encryption key store creation failed.
-
Cause: An attempt to create the encryption key store failed with the indicated error. This is an internal error.
- ACFS-10567: Encryption key store save failed.
-
Cause: An attempt to save the encryption key store failed. This is an internal error.
- ACFS-10568: Encryption key store open failed.
-
Cause: An attempt to open the encryption key store failed. This is an internal error.
- ACFS-10569: Encryption key store delete succeeded.
-
Cause: Encryption key store was deleted.
- ACFS-10573: Encryption key store not found.
-
Cause: Encryption key store did not exist.
- ACFS-10574: ACFS encryption already initialized, cannot reinitialize.
-
Cause: 'acfsutil encr init'can has already been executed and the encryption key store already existed.
- ACFS-10575: Incorrect encryption key store.
-
Cause: The encryption key store may have been deleted and re-created.
- ACFS-10576: Incorrect encryption key, new volume encryption key not created.
-
Cause: The encryption key store may have been deleted and re-created.
- ACFS-10577: Encryption parameters not set.
-
Cause: A command that requires encryption parameters to be set first was run before encryption parameters were set on the file system.
- ACFS-10578: Unable to communicate new encryption settings to cluster members.
-
Cause: Internal error.
- ACFS-10579: Key store is not valid for encryption.
-
Cause: The encryption key store was either not created using 'acfsutil encr init' or it was corrupted.
- ACFS-10580: Internal API error : [number : string].
-
Cause: Internal error occurred.
- ACFS-10581: Internal API error : [string].
-
Cause: Internal error occurred.
- ACFS-10582: Internal API error : [number : string string].
-
Cause: Internal error occurred.
- ACFS-10583: Internal API error : [string, number].
-
Cause: Internal error occurred.
- ACFS-10585: Ioctl 'string' failed in 'string' with error number.
-
Cause: Internal error occurred.
- ACFS-10586: Internal error.
-
Cause: Internal error occurred.
- ACFS-10588: Internal error : WLT number.
-
Cause: Internal error occurred.
- ACFS-10589: Internal error : BSF number.
-
Cause: Internal error occurred.
- ACFS-10590: Internal error : XML number.
-
Cause: Internal error occurred.
- ACFS-10591: Internal error : TSP number.
-
Cause: Internal error occurred.
- ACFS-10592: Internal error : IOC number.
-
Cause: Internal error occurred.
- ACFS-10593: Internal error : UGP number.
-
Cause: Internal error occurred.
- ACFS-10594: Internal error : OCR number : string.
-
Cause: Internal error occurred.
- ACFS-10596: Unable to get the hostname for the current node.
-
Cause: The current user does not have access to the requested information.
- ACFS-10597: The user 'string' and the group 'string' do not belong to the same domain.
-
Cause: The user and the group were not part of the same domain.
- ACFS-10598: Unable to retrieve domain name information for 'string'.
-
Cause: Unable to retrieve domain name information.
- ACFS-10599: Current user does not have system administrative privileges to initialize ACFS security.
-
Cause: The user was not part of system administrators group.
- ACFS-10600: Failed to store first security administrator 'string' in wallet.
-
Cause: Internal error.
- ACFS-10601: Failed to update first security administrator 'string' information.
-
Cause: Internal error.
- ACFS-10602: Passwords do not match.
-
Cause: Verification of the password did not succeed.
- ACFS-10603: Security administrator group already set in wallet.
-
Cause: Security administrator group was already set in wallet.
- ACFS-10604: Security administrator group not set in wallet.
-
Cause: Internal error.
- ACFS-10606: User 'string' is not a security administrator.
-
Cause: User was not a security administrator.
- ACFS-10607: User 'string' is not member of security administrator group.
-
Cause: User was not a member of security administrator's group.
- ACFS-10609: Administrator update in driver failed.
-
Cause: Internal error
- ACFS-10610: Failed to get current user information.
-
Cause: Internal error.
- ACFS-10611: Failed to assign user 'string' as security administrator.
-
Cause: Internal error
- ACFS-10612: Failed to remove user 'string' from security administrator(s) list.
-
Cause: Internal error
- ACFS-10613: Failed to change ACFS Security administrator password for current user.
-
Cause: Internal error
- ACFS-10614: Security administrator 'string' already added.
-
Cause: User was already a security administrator.
- ACFS-10615: User 'string' is not a security administrator.
-
Cause: User was not a security administrator.
- ACFS-10616: Incorrect ACFS Security administrator password.
-
Cause: The password supplied was incorrect.
- ACFS-10617: Password cannot exceed number characters.
-
Cause: The password entered exceeded the maximum allowed characters.
- ACFS-10618: Security administrator 'string' could not be added.
-
Cause: Security administrator was not added.
- ACFS-10619: Security administrator 'string' added.
-
Cause: Security administrator was added.
- ACFS-10620: Security administrator 'string' could not be removed.
-
Cause: Security administrator was not removed.
- ACFS-10621: Removal of the last security administrator 'string' is not allowed.
-
Cause: The security administrator was not removed being the only security administrator in this system.
- ACFS-10622: Security administrator 'string' removed.
-
Cause: Security administrator was removed.
- ACFS-10623: ACFS security already initialized, cannot reinitialize.
-
Cause: ACFS security was already initialized and could not be reinitialized.
- ACFS-10624: User 'string' is not member of the group 'string'.
-
Cause: The user was not member of the group.
- ACFS-10625: Failed to prepare file system for security operations on mount point 'string'.
-
Cause: Internal error.
- ACFS-10626: Mount point 'string' is already prepared for security.
-
Cause: Mount point was already prepared for security. Prepare should be executed only once for an ACFS formatted file system that is mounted.
- ACFS-10627: Mount point 'string' is now prepared for security operations.
-
Cause: " Mount point was prepared for security operations.
- ACFS-10629: Failed to enable security on mount point 'string'.
-
Cause: Internal error.
- ACFS-10630: Security is already enabled on mount point 'string'.
-
Cause: Security was already enabled on mount point.
- ACFS-10631: Security is now enabled on mount point 'string'.
-
Cause: Security was enabled on mount point.
- ACFS-10632: Security is already disabled on mount point 'string'.
-
Cause: Security was already disabled on mount point.
- ACFS-10633: Security is now disabled on mount point 'string'.
-
Cause: Security was disabled on mount point.
- ACFS-10634: Failed to disable security on mount point 'string'.
-
Cause: Internal error.
- ACFS-10635: Failed to get security administrator group.
-
Cause: Internal error.
- ACFS-10636: Security administrator group retrieved.
-
Cause: Security administrators group was retrieved.
- ACFS-10637: File system is not prepared for ACFS security on mount point 'string'.
-
Cause: File system was not prepared for security operations on mount point.
- ACFS-10638: Backup and log directories created.
-
Cause: Backup and log directories were created.
- ACFS-10639: Failed to create directory 'string' on mount point 'string'.
-
Cause: Internal error.
- ACFS-10640: Failed to create log directory on mount point 'string'.
-
Cause: Internal error.
- ACFS-10641: Failed to create backup directory on mount point 'string'.
-
Cause: Internal error.
- ACFS-10643: Security is already enabled on realm 'string'.
-
Cause: Security was already enabled on realm.
- ACFS-10644: Security is already disabled on realm 'string'.
-
Cause: Security was already disabled on realm.
- ACFS-10645: Failed to set owner of file 'string' to 'string'.
-
Cause: Current user is not owner of the file.
- ACFS-10646: Failed to create secbackup.xml file on mount point 'string'.
-
Cause: Internal error.
- ACFS-10647: Current user does not have system administrative privileges to initialize ACFS encryption.
-
Cause: The user was not part of system administrators group.
- ACFS-10648: ACFS security already initialized, recovery failed.
-
Cause: Previous execution of 'acfsutil sec init' had failed. Recovery actions also failed in the subsequent execution of 'acfsutil sec init'.
- ACFS-10649: ACFS encryption already initialized, recovery failed.
-
Cause: Previous execution of 'acfsutil encr init' had failed. Recovery actions also failed in the subsequent execution of 'acfsutil encr init'.
- ACFS-10650: Invalid file name 'string' for ACFS security metadata.
-
Cause: The file was invalid for saving or loading ACFS security metadata.
- ACFS-10651: Failed to save ACFS security metadata of mount point 'string'.
-
Cause: Internal error
- ACFS-10652: Saved ACFS security metadata of mount point 'string'.
-
Cause: ACFS security metadata of mount point '%s' was saved.
- ACFS-10653: Failed to save ACFS security string metadata of mount point 'string'.
-
Cause: Internal error.
- ACFS-10654: Directory '.Security' does not exist on mount point 'string'.
-
Cause: Mount point was not prepared for ACFS security.
- ACFS-10655: Failed to get hostname.
-
Cause: Internal error.
- ACFS-10656: Failed to get timestamp.
-
Cause: Internal error.
- ACFS-10657: Absolute and relative pathnames are not allowed with '-p' option.
-
Cause: Filename was provided with absolute or relative path.
- ACFS-10658: ACFS Security has been initialized on the cluster with user 'string' as the initial Security Administrator and 'string' as the Security Administrator group.
-
Cause: An administrator initialized ACFS Security on the cluster.
- ACFS-10659: Cannot destroy realm 'string' because it is a system-created realm.
-
Cause: A request to destroy a system-created realm was denied because that operation is not allowed.
- ACFS-10660: Current user does not have required OS privileges to set ACFS encryption parameters.
-
Cause: Current user does not have root or administrator privileges to run 'acfsutil encr set'.
- ACFS-10661: Current user does not have required OS privileges to rekey the ACFS encryption parameters.
-
Cause: Current user does not have root or administrator privileges to run 'acfsutil encr rekey'.
- ACFS-10662: Current user 'string' does not have security administrator privileges.
-
Cause: A command requiring Security Administrator privileges was issued but the user is not in the Security Administrators group.
- ACFS-10663: User name 'string' is not a fully qualified name.
-
Cause: Fully qualified name was not specified. The supplied user name was not prefixed with a Windows Server Domain name.
- ACFS-10664: Group name 'string' is not a fully qualified name.
-
Cause: Fully qualified name was not specified.The supplied group name was not prefixed with a Windows Server Domain name.
- ACFS-10665: Group 'string' is a local group and not a Windows Server Domain group.
-
Cause: Specified group was not a Windows Server Domain group.
- ACFS-10666: User 'string' is a local user and not a Windows Server Domain user.
-
Cause: Specified user was not a Windows Server Domain user.
- ACFS-10667: Windows Server Domain 'string' does not exist.
-
Cause: Failed to get Windows Server Domain controller for the domain either because of not access to domain or domain does not exist.
- ACFS-10675: Failed to load ACFS security metadata on mount point 'string'.
-
Cause: Internal error.
- ACFS-10676: Loaded ACFS security metadata on mount point 'string'.
-
Cause: ACFS security metadata was loaded on mount point.
- ACFS-10677: Failed to load string on mount point 'string'.
-
Cause: Internal error.
- ACFS-10679: Unable to resolve the user id 'string'.
-
Cause: The user was not found on the system.
- ACFS-10680: XDK version not compatible.
-
Cause: Oracle XDK version was incompatible.
- ACFS-10681: ACFS kernel version is not compatible. The kernel version on the system is 'string' while the expected kernel version is 'string' or above.
-
Cause: ACFS kernel version was incompatible.
- ACFS-10682: Kernel major version is not compatible.
-
Cause: Kernel major version was incompatible.
- ACFS-10683: Kernel release version is not compatible.
-
Cause: Kernel release version was incompatible.
- ACFS-10684: Kernel update version is not compatible.
-
Cause: Kernel update version was incompatible.
- ACFS-10685: Kernel port update version is not compatible.
-
Cause: Kernel port version was incompatible.
- ACFS-10686: Kernel patch version is not compatible.
-
Cause: Kernel patch version was incompatible.
- ACFS-10687: Kernel one off version is not compatible.
-
Cause: Kernel one off version was incompatible.
- ACFS-10688: Unable to resolve the group id 'string'.
-
Cause: The OS group ID could not be resolved to a name. Usually this occurs because the OS group has been removed.
- ACFS-10689: Failed to update security administrators information in the driver, some of the subsequent commands may fail.
-
Cause: Updating driver security administrator data failed during mount. The mount completes, but subsequent security commands may be affected. This is an internal error.
- ACFS-10690: Cannot edit groups in realm 'string'.
-
Cause: No changes were made to the groups in the realm as the operation is not allowed.
- ACFS-10691: Changed ACFS Security administrator password for current user.
-
Cause: Informational.
- ACFS-10700: Failed to store volume encryption key.
-
Cause: Internal error.
- ACFS-10701: Failed to get volume encryption key.
-
Cause: Internal error.
- ACFS-10702: Snapshots exist for the file system mounted on 'string'. New encryption parameters will not apply to files in these snapshots.
-
Cause: One or more snapshots existed for the file system when this encryption operation was done. The new encryption parameters set by this command will apply only to new files created in the file system and not to existing files in any snapshots. Note that none of the encryption commands affect files in any snapshots. Any snapshots created after the command was run will use the new encryption parameters.
- ACFS-10703: Snapshots exist for the file system mounted on 'string'. Encryption status of files in these snapshots will not change.
-
Cause: One or more snapshots existed for the file system when this encryption operation was done. The operation did not modify file data in any snapshots on the file system, so this data may still be available on disk unencrypted. Note that none of the encryption commands affect files in any snapshots.
- ACFS-10704: Snapshots exist for the file system mounted on 'string'. Encryption keys of files in these snapshots will not be rekeyed.
-
Cause: One or more snapshots existed for the file system when this encryption operation was done. The operation did not rekey FEKs of files in any snapshots of the file system, so the FEKs of these files will continue to remain encrypted with the old parameters. Note that none of the encryption commands affect files in any snapshots.
- ACFS-10705: Cannot perform encryption operation because volume encryption keys for the file system mounted at 'string' are not available.
-
Cause: The encryption operation failed because the required volume encryption keys for the file system were not available to the ACFS file system driver. This could happen because an incorrect key store password was supplied during mount or because of some other error during mount.
- ACFS-10706: Cannot perform encryption operation because an encryption undo operation is in progress.
-
Cause: The encryption operation failed because the system administrator was running encryption undo ('acfsutil encr set -u') on the file system. It is also possible that a previous encryption undo operation had not completed cleanly.
- ACFS-10707: Cannot perform encryption undo operation because file system level encryption is on.
-
Cause: The encryption undo operation failed because file system level encryption was on.
- ACFS-10708: An earlier key store migrate operation did not complete. Provide the same password as the one used in the previous attempt.
-
Cause: An earlier run of 'acfsutil keystore migrate' command did not complete.
- ACFS-10709: Existing ACFS encryption key store is already password-protected.
-
Cause: Informational.
- ACFS-10710: Existing ACFS encryption key store is already not password-protected.
-
Cause: Informational.
- ACFS-10711: Recovery of ACFS encryption key store completed successfully.
-
Cause: Informational.
- ACFS-10712: ACFS encryption key store migration to password-protected key store completed successfully.
-
Cause: Informational.
- ACFS-10713: ACFS encryption key store migration to password-free key store completed successfully.
-
Cause: Informational.
- ACFS-10714: The environment variable OKV_HOME is not set.
-
Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV_HOME environment variable was not set.
- ACFS-10715: failed to find the PKCS library in path 'string'
-
Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the PKCS library was not found in '$OKV_HOME/lib'.
- ACFS-10716: failed to load the PKCS library
-
Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV PKCS library could not be loaded from '$OKV_HOME/lib'.
- ACFS-10717: failed to find Oracle Key Vault (OKV) client configuration file
-
Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV client configuration file, okvclient.ora, was not found in '$OKV_HOME/conf'.
- ACFS-10718: failed to login to OKV server
-
Cause: A login attempt to Oracle Key Vault (OKV) server failed.
- ACFS-10719: failed to store encryption keys in file system wallet
-
Cause: Internal error.
- ACFS-10720: Key store must be either SSO, PKCS, or OKV.
-
Cause: An attempt to store an encryption key was rejected because the specified key store was not one of: SSO, PKCS or OKV.
- ACFS-10721: failed to save encryption keys, file system wallet already exists in directory 'string'
-
Cause: An attempt to create a new wallet and save encryption keys in it failed because the wallet already existed in the said location.
- ACFS-10725: Failed to start encryption logging on mount point 'string'.
-
Cause: Internal error.
- ACFS-10726: Failed to start security logging on mount point 'string'.
-
Cause: Internal error.
- ACFS-10727: Failed to start global security and encryption logging.
-
Cause: Global security and encryption logging services could not be started. The log file for this node will not be updated.
- ACFS-10728: ACFS encryption logging directory not found on mount point 'string'.
-
Cause: The ACFS encryption logging directory '<mount_point>/.Security/encryption/logs/' could not be opened.
- ACFS-10729: ACFS security logging directory not found on mount point 'string'.
-
Cause: The ACFS security logging directory '<mount_point>/.Security/realm/logs/' could not be opened.
- ACFS-10730: ACFS security and encryption logging directory not found in CRS_HOME.
-
Cause: The ACFS security and encryption logging directory '<CRS_HOME>/log/<host_name>/acfssec' could not be opened.
- ACFS-10731: Could not get local host name, ACFS encryption logging will not be available on mount point 'string'.
-
Cause: The local host name could not be determined, ACFS encryption logs for this host in '<mount_point>/.Security/encryption/logs/' will not be written.
- ACFS-10732: Could not get local host name, ACFS security logging will not be available on mount point 'string'.
-
Cause: The local host name could not be determined, ACFS security logs for this host in '<mount_point>/.Security/realm/logs/' will not be written.
- ACFS-10733: Could not get local host name, ACFS security and encryption logging will not be available for this host
-
Cause: The local host name could not be determined, ACFS security and encryption logs for this host in '<CRS_HOME>/log/<host_name>/acfssec' will not be written.
- ACFS-10751: Realm_Metadata file has invalid realm record\nfor file:\nstring
-
Cause: A realm record of the indicated Realm_Metadata file was invalid.
- ACFS-10753: Realm_Metadata file has no valid realm records\nfor file:\nstring
-
Cause: The indicated Realm_Metadata file did not contain any valid valid realm records.
- ACFS-10755: Realm_Metadata file contains invalid realm record data\nfor file:\nstring
-
Cause: The indicated Realm_Metadata file contained at least one invalid realm record. Refer to the accompanying message(s) for more information on the problem.
- ACFS-10756: Realm_Metadata file _Private structure is invalid for:\nfor file:\nstring
-
Cause: The _Private structure of the indicated Realm_Metadata file was invalid. Refer to the accompanying message(s) for more information on the problem.
- ACFS-10757: Realm_Metadata file has invalid Hash_Table data\nfor file:\nstring
-
Cause: The Hash_Table of the indicated Realm_Metadata file contained inconsistent data. Refer to the accompanying message(s) for more information on the problem.
- ACFS-10760: Realm_Metadata file _Private structure has invalid _maxFree value\n found: number minimum: number\nfor structure:\nstring
-
Cause: The _maxFree property of the indicated _Private metadata structure was incorrect.
- ACFS-10761: Realm_Metadata file _Private structure has invalid _freeDataListTail value\n found: number minimum: number\nfor structure:\nstring
-
Cause: The _freeDataListTail property of the indicated _Private metadata structure was incorrect.
- ACFS-10762: Realm_Metadata file node not on _freeDataList\nfor file:\nstring
-
Cause: One or more of the _security_data nodes of the indicated Realm_Metadata file was not found on the free data node list. The _next property for one or more of the _security_data nodes was incorrect.
- ACFS-10764: Realm_Metadata file has invalid _security_record for _Administrator default\nfor file:\nstring
-
Cause: The default _Administrator _security_record of the indicated Security_Metadata file was invalid.
- ACFS-10766: Realm_Metadata file has no valid realm data records\nfor file:\nstring
-
Cause: The indicated Realm_Metadata file did not contain any valid valid realm data records.
- ACFS-10767: Realm_Metadata File Private structure has invalid _freeDataList value\n found: number maximum: number\nfor file:\nstring
-
Cause: The _freeDataList property of the _Private structure of the indicated Realm_Metadata file was incorrect. The _freeDataList value exceeded the maximum value for this Realm_Metadata file.
- ACFS-10768: Number of realms created on mount point 'string' has reached the limit number.
-
Cause: A request to create a realm was denied because the number of realms created on the mount point has reached the limit.
- ACFS-10769: Number of rulesets created on mount point 'string' has reached the limit number.
-
Cause: A request to create a ruleset was denied because the number of rulesets created on the mount point has reached the limit.
- ACFS-10770: Number of rules created on mount point 'string' has reached the limit number.
-
Cause: A request to create a rule was denied because the number of rules created on the mount point has reached the limit.
- ACFS-10771: Number of realms that file 'string' is part of has reached the limit number.
-
Cause: A request to add the file to a realm was denied because the number of realms that the file is part of has reached the limit.
- ACFS-10772: Security at the realm level will not be in effect until file system-level security is enabled.
-
Cause: Security is disabled at the file system level. When file system-level security is disabled, enabling realm-level security does not enable the authorization checks provided by the realm.
- ACFS-10773: Unable to lock ACFS Security wallet.
-
Cause: The ACFS Security wallet lock was not acquired.
- ACFS-10774: Unable to unlock ACFS Security wallet.
-
Cause: The ACFS Security wallet lock was not released.
- ACFS-10775: Cannot proceed as another instance of 'acfsutil' command is updating the security administrator information.
-
Cause: ACFS Security wallet is locked by another instance of 'acfsutil' command.
- ACFS-10776: Invalid 'acfsutil' version 'string'
-
Cause: Internal error.
- ACFS-10777: Unable to lock ACFS encryption key store.
-
Cause: The ACFS encryption key store lock could not be acquired.
- ACFS-10778: Unable to unlock ACFS encryption key store.
-
Cause: The ACFS encryption key store lock was not released.
- ACFS-10779: Cannot proceed as another instance of 'acfsutil' command is updating the encryption key store.
-
Cause: An acfsutil encryption request found the ACFS encryption key store locked by another instance of the acfsutil command.
- ACFS-10780: The file system mounted on 'string' has been prepared for ACFS Security, undo ACFS Security first.
-
Cause: ACFS Encryption cannot be undone when the file system has been prepared for ACFS Security.
- ACFS-10781: could not undo ACFS security or encryption for the file system mounted on path 'string' because of existing snapshots
-
Cause: An attempt to undo ACFS security or encryption for the indicated file system failed because there were existing snapshots (created by user or created as part of replication V2 being active) for the file system. ACFS security and encryption can only be undone for a file system with no snapshots. This message may be displayed before or after all files have been decrypted using the command 'acfsutil encr set -u'. In either case, the file system retains its encryption 'prepared' state and files can be encrypted without running 'acfsutil encr set' again.
- ACFS-10782: The file system mounted on 'string' has not been prepared for ACFS Security, nothing to be undone.
-
Cause: The file system was not prepared for ACFS Security.
- ACFS-10783: ACFS Encryption is not set on the file system mounted on 'string', nothing to be undone.
-
Cause: ACFS Encryption was not set on the file system.
- ACFS-10784: Could not destroy all realms, unable to undo ACFS Security.
-
Cause: All realms were not destroyed.
- ACFS-10785: Could not destroy all rules, unable to undo ACFS Security.
-
Cause: All rules were not destroyed.
- ACFS-10786: Could not destroy all rulesets, unable to undo ACFS Security.
-
Cause: All rulesets were not destroyed
- ACFS-10787: Failed to prepare ACFS Security on mount point 'string' as replication is active on this mount point.
-
Cause: Replication was active on the mount point. ACFS Replication and ACFS Security cannot co-exist on the same mount point.
- ACFS-10788: ACFS Security undo operation on mount point 'string' completed.
-
Cause: ACFS Security undo operation on the mount point was completed.
- ACFS-10789: Failed to undo ACFS Security on mount point 'string'.
-
Cause: Internal error.
- ACFS-10790: Failed to set ACFS Encryption on mount point 'string' as replication is active on this mount point.
-
Cause: Replication was active on the mount point. ACFS Replication and ACFS Encryption cannot co-exist on the same mount point.
- ACFS-10791: Failed to undo ACFS encryption on mount point 'string'.
-
Cause: Internal error.
- ACFS-10792: Cannot add filter 'string:string' to the cloned realm as the rule set 'string' does not exist on the mount point 'string'.
-
Cause: Filters could not be added to cloned realm because rule sets were not present on mount point.
- ACFS-10793: File objects cannot be added to cloned realm as file objects do not exist on destination mount point.
-
Cause: File objects could not be added to cloned realm because file objects were not present on destination mount point.
- ACFS-10794: File 'string' does not exist on mount point 'string'.
-
Cause: Information of file could not be obtained, because either file name specified is not correct or file does not exist on given mount point.
- ACFS-10795: Cannot load ACFS security meta data because the destination mount point 'string' already has some user-created rules, rule sets or realms.
-
Cause: ACFS security load was not done as the destination mount point had some user created rules, rule sets or realms.
- ACFS-10796: A prior failed encryption initialization cannot be recovered for this request because the prior initialization specified a password-protected key store.
-
Cause: A prior failed encryption initialization was not recovered for this request because the prior initialization specified a password-protected key store.
- ACFS-10797: A prior failed encryption initialization cannot be recovered for this request because the prior initialization specified a non-password-protected key store.
-
Cause: A prior failed encryption initialization was not recovered for this request because the prior initialization specified a non-password-protected key store.
- ACFS-10798: ACFS Encryption undo operation on mount point 'string' completed.
-
Cause: ACFS Encryption undo operation on the mount point was completed.
- ACFS-10799: For cloning realms with 'string' option, destination mount point must be same as source mount point.
-
Cause: Cloning of file system objects is not supported if destination mount point is different from source mount point.
- ACFS-10800: Failed to complete ACFS Security undo operation on mount point 'string'.
-
Cause: ACFS Security undo operation did not complete because some rules, rulesets, or realms exist for the given file system.
- ACFS-10801: failed to acquire a lock on ACFS security wallet
-
Cause: The ACFS security wallet could not be initialized because the lock on the wallet could not be obtained.
- ACFS-10802: unable to release the lock being held on the ACFS security wallet
-
Cause: After security initialization, the lock on ACFS security wallet could not be released.
- ACFS-10803: cannot proceed because another instance of 'acfsutil' command is updating the ACFS security wallet
-
Cause: An attempt to update the ACFS security wallet failed because the ACFS security wallet was locked by another instance of the acfsutil command.
- ACFS-10850: Password must have at least number characters.
-
Cause: The password was not long enough.
- ACFS-10851: Password must have at least one digit and letter in it.
-
Cause: The password did not have either a digit or a letter in it.
- ACFS-10901: Failed to add the read-only snapshot file 'string' to realm 'string'.
-
Cause: A file specified for addition to a security realm was a read-only snapshot file.
- ACFS-10902: Failed to add the read-write snapshot file 'string' to realm 'string'.
-
Cause: A file specified for addition to a security realm was a read-write snapshot file.
- ACFS-10903: Snapshot 'string' of mount point 'string' is not prepared for ACFS Security.
-
Cause: Snapshot was not prepared for security operations on mount point.
- ACFS-10914: Security is already enabled in snapshot 'string' of mount point 'string'.
-
Cause: Security was already enabled in snasphot of mount point.
- ACFS-10915: Security is already enabled on realm 'string' in snapshot 'string' of mount point 'string'
-
Cause: Security was already enabled on realm in snapshot.
- ACFS-10916: Security is now enabled in snapshot 'string' of mount point 'string'.
-
Cause: Security was enabled in snapshot of mount point.
- ACFS-10917: Failed to enable security in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10918: Security is already disabled in snapshot 'string' of mount point 'string'.
-
Cause: Security was already disabled in snapshot of mount point.
- ACFS-10919: Security is already disabled on realm 'string' in snapshot 'string' of mount point 'string'.
-
Cause: Security was already disabled on realm in snapshot.
- ACFS-10920: Failed to disable security in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10921: Realm 'string' not found in snapshot 'string' of mount point 'string'.
-
Cause: Realm was not found in snapshot of mount point.
- ACFS-10922: Failed to get security related information of snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10923: Failed to get users for realm 'string' in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10924: Failed to get groups for realm 'string' in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10925: Failed to get realm encryption attributes of realm 'string' in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10926: Attributes of realm 'string' in snapshot 'string' of mount point 'string' retrieved.
-
Cause: Attributes of realm in snapshot were retrieved.
- ACFS-10927: Failed to get all rules in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10928: Failed to get information of rule 'string' in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10929: Rule 'string' not found in snapshot 'string' of mount point 'string'.
-
Cause: Rule was not found in the snapshot.
- ACFS-10930: Failed to get all rule sets in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10931: Failed to get rules for rule set 'string' in snapshot 'string' of mount point 'string'.
-
Cause: Internal error.
- ACFS-10932: Rule set 'string' not found in snapshot 'string' of mount point 'string'.
-
Cause: Rule set was not found in snapshot of mount point.
- ACFS-10933: Failed to delete the read-only snapshot file 'string' from realm 'string'.
-
Cause: Security operations cannot be performed on a read-only snapshot file.
- ACFS-10934: Failed to delete the read-write snapshot file 'string' from realm 'string'.
-
Cause: Security operations cannot be performed on a read-write snapshot file.
- ACFS-10935: ACFS Security cannot be enabled or disabled because 'string' is a read-only snapshot
-
Cause: A request to enable or disable ACFS Security specified a read-only snapshot.
- ACFS-10936: ACFS Security is now disabled in snapshot 'string' of mount point 'string'.
-
Cause: Informational.
- ACFS-10937: ACFS Security is now enabled on realm 'string' in snapshot 'string' of mount point 'string'.
-
Cause: Informational.
- ACFS-10938: ACFS Security is now disabled on realm 'string' in snapshot 'string' of mount point 'string'.
-
Cause: Informational.
- ACFS-10939: ACFS Security is now enabled on realm 'string' in mount point 'string'.
-
Cause: Informational.
- ACFS-10940: ACFS Security is now disabled on realm 'string' in mount point 'string'.
-
Cause: Informational.
- ACFS-10941: Failed to create 'string' file on mount point 'string'
-
Cause: An attempt to create a file on the indicated mount point failed, most likely because the user lacked the requisite permission.
- ACFS-10942: Insufficient disk space on mount point 'string'
-
Cause: The requested operation failed because the file system was full.
- ACFS-10945: ACFS Auditing source 'string' is already enabled on mount point 'string'.
-
Cause: Informational.
- ACFS-10946: ACFS Auditing source 'string' is already disabled on mount point 'string'.
-
Cause: Informational.
- ACFS-10947: Audit trail on mount point 'string' is marked as read.
-
Cause: Informational.
- ACFS-10948: Audit trail on mount point 'string' is archived.
-
Cause: Informational.
- ACFS-10949: ACFS Auditing has been initialized on the cluster with 'string' as the Oracle ACFS auditor OS group and 'string' as the Oracle ACFS audit manager OS group.
-
Cause: Informational.
- ACFS-10950: Audit trail archive for mount point 'string' is purged.
-
Cause: Informational.
- ACFS-10951: Current user does not have system administrative privileges to initialize auditing.
-
Cause: The user was not part of system administrators group.
- ACFS-10952: Auditing already initialized; cannot reinitialize.
-
Cause: An attempt was made to initialize auditing after it was already initialized.
- ACFS-10953: Auditing is not initialized.
-
Cause: A command was issued which requires auditing to be intialized for the cluster, but auditing has not been initialized.
- ACFS-10954: Failed to enable auditing on mount point 'string'.
-
Cause: Internal error.
- ACFS-10955: Failed to disable auditing on mount point 'string'.
-
Cause: Internal error.
- ACFS-10956: Failed to enable auditing for realm 'string' on mount point 'string'.
-
Cause: Internal error.
- ACFS-10957: Failed to disable auditing for realm 'string' on mount point 'string'.
-
Cause: Internal error.
- ACFS-10958: Current user does not have privileges to run audit commands.
-
Cause: An attempt to execute an audit command was rejected because the attempting user was not a member of the audit managers group or the auditors group.
- ACFS-10960: Failed to get audit information for the mount point 'string'.
-
Cause: Internal error.
- ACFS-10961: Failed to get audit manager OS group.
-
Cause: Internal error.
- ACFS-10962: Failed to get auditor OS group.
-
Cause: Internal error.
- ACFS-10963: Auditing is not enabled on mount point 'string'.
-
Cause: A command was issued that requires auditing to be enabled at the file system level, but it is not enabled.
- ACFS-10964: Failed to archive audit trail on mount point 'string'.
-
Cause: Internal error.
- ACFS-10965: Failed to mark audit trail on mount point 'string' as read
-
Cause: Internal error.
- ACFS-10966: Audit trail on mount point 'string' is already marked as read.
-
Cause: Audit trail was already marked as read on mount point.
- ACFS-10967: Audit trail on mount point 'string' not found.
-
Cause: An 'acfsutil audit' command was issued but auditing has not been initialized.
- ACFS-10968: Failed to create audit trail XML file 'string' for mount point string.
-
Cause: Internal error.
- ACFS-10969: Failed to purge audit trail archive file for mount point 'string'.
-
Cause: Internal error.
- ACFS-10970: Failed to purge audit trail archive because it is not marked 'read' for mount point 'string'.
-
Cause: Audit trail was not yet marked as 'read' on mount point.
- ACFS-10971: Current user does not have privileges to run this audit command.
-
Cause: Command was executed as user who is not part of audit manager OS group.
- ACFS-10972: Failed to update audit managers and auditors group information in the driver; some of the subsequent audit related commands may fail.
-
Cause: Audit Managers and Auditors information was not communicated to the ACFS driver during mount. The mount command was successful but the subsequent audit commands will not work on this host until the problem is corrected.
- ACFS-10973: The ADVM compatibility attribute for the diskgroup must be set to version 'string' to enable auditing on mount point 'string'.
-
Cause: A security adminstrator or audit manager or administrator attempted to enable auditing, but the 'COMPATIBLE.ADVM' attribute for the disk group had not been upgraded to a supported version.
- ACFS-10974: Auditing cannot be enabled on mount point 'string', because ADVM compatibility is lower than 'string'.
-
Cause: A security adminstrator or system administrator attempted to enable auditing as part of 'acfsutil sec prepare' or 'acfsutil encr set' which was successful, but auditing could not be enabled because the 'compatible.advm attribute had not been upgraded to a supported version.
- ACFS-10975: Failed to get audit information for realm 'string' on mount point 'string'.
-
Cause: Internal error.
- ACFS-10976: Failed to create audit trail XML file because the old audit trail XML file exists for mount point 'string'.
-
Cause: A request to archive the audit trail found an existing audit trail XML file.
- ACFS-10977: Auditing is enabled for realm 'string' on mount point 'string'.
-
Cause: Informational.
- ACFS-10978: Auditing is disabled for realm 'string' on mount point 'string'.
-
Cause: Informational.
- ACFS-10979: Cannot proceed because file system is not prepared for ACFS Security.
-
Cause: An attempt to enable or disable audit on Security source failed because the file system was not prepare for ACFS Security.
- ACFS-10980: Cannot proceed because file system is not set for ACFS Encryption.
-
Cause: An attempt to enable or disable audit on Encryption source failed because the file system was not set for ACFS Encryption.
- ACFS-10998: ACFS Audit not initialized
-
Cause: ACFS Audit was not initilized.
- ACFS-10999: Audit trail archive file on mount point 'string' was not found.
-
Cause: An 'acfsutil audit read' command was issued but the audit trail backup file did not exist.
- ACFS-11000: ACFS Auditing is already initialized with different Audit Managers and Auditors group.
-
Cause: Values provided on the command line did not match those with which ACFS Auditing was initialized earlier.
- ACFS-11001: Error in parsing command line arguments.
-
Cause: There was a syntax error is the command line arguments.
- ACFS-11002: Error: a device name must be supplied with the -l option.
-
Cause: Either the -l option was not present in the command line or it had no argument.
- ACFS-11003: AIX ODM initialization failed, odmerr number
-
Cause: AIX ODM internal operation error.
- ACFS-11004: failed to lock AIX ODM database, odmerr number
-
Cause: The method could not lock the AIX ODM database.
- ACFS-11005: failed to look up AIX ODM PdDv object class, odmerr number
-
Cause: The user may lack required permission or the entry may not exist.
- ACFS-11006: failed to open AIX ODM CuDv object class, odmerr number
-
Cause: The user may lack required permission or the entry may not exist.
- ACFS-11007: failed to add to AIX ODM CuDv object class, odmerr number
-
Cause: An attempt to add the device's entry to the ODM CuDv object class failed.
- ACFS-11008: failed to close the AIX ODM CuDv object class, odmerr number
-
Cause: AIX ODM internal operation error.
- ACFS-11010: failed to look up AIX ODM CuDv object class, odmerr number
-
Cause: The user may lack required permission or the entry may not exist.
- ACFS-11015: failed to load kernel extension string, errno number (string)
-
Cause: Loading the kernel extension into the kernel failed.
- ACFS-11017: failed to configure kernel extension string, errno number (string)
-
Cause: Could not configure the device's driver in the kernel.
- ACFS-11018: failed to get a major number for device string
-
Cause: The method could not get a major number for the device.
- ACFS-11019: failed to get a minor number for device string
-
Cause: The method could not get a minor number for the device.
- ACFS-11022: failed to configure device string, errno number (string)
-
Cause: Attempt to configure the device's driver in the kernel got an error.
- ACFS-11024: failed to remove the old device file string, errno number (string)
-
Cause: The method failed to remove the device file.
- ACFS-11026: failed to create new device file string, errno number (string)
-
Cause: The user may not have permission or a file with the same name already exists.
- ACFS-11028: failed to set permission of the new device file string, errno number (string)
-
Cause: The method failed to set permission of the device special file.
- ACFS-11030: failed to set group of the new device file string, errno number (string)
-
Cause: The method failed to set the owning group of the device special file.
- ACFS-11031: failed to open the ASMADMIN group file, errno number (string)
-
Cause: The method could not open the file containing the group to own the device.
- ACFS-11032: failed to read from the ASMADMIN group file, errno number (string)
-
Cause: The method could not read the file containing the group to own the device.
- ACFS-11034: failed to set device state to AVAILABLE, odmerr number
-
Cause: The method could not change the device's state.
- ACFS-11036: No operation was performed because device state is string instead of DEFINED.
-
Cause: The method expected a DEFINED device state.
- ACFS-11038: failed to unconfigure kernel extension string, errno number (string)
-
Cause: The method could not unconfigure the kernel extension.
- ACFS-11040: failed to unload kernel extension string, errno number (string)
-
Cause: The method could not unload the extension from kernel.
- ACFS-11044: no minor number was returned for device string
-
Cause: The operating system did not return a device minor number as requested.
- ACFS-11046: failed to set device state to DEFINED, odmerr number
-
Cause: The method failed to change the device's state.
- ACFS-11050: failed to delete attributes of device string, odmerr number
-
Cause: The method failed to remove the device's attributes from the AIX ODM CuAt object class.
- ACFS-11052: failed to delete customized object of device string, odmerr number
-
Cause: The method failed to remove the device's entry from the AIX ODM CuDv object class.
- ACFS-11053: failed to release major number for device string
-
Cause: The method failed to release the device's major number.
- ACFS-11055: failed to remove device special file string, errno number (string)
-
Cause: The method failed to remove the device special file.
- ACFS-11060: failed to unload kernel extension string
-
Cause: Could not unload the extension from kernel.
- ACFS-11061: failed to look up the group id for group string
-
Cause: The named group probably does not exist.
- ACFS-11062: failed to create directory string, errno number (string)
-
Cause: The directory could not be created.
- ACFS-11063: failed to set permission on directory string, errno number (string)
-
Cause: The permission of the directory could not be changed.
- ACFS-11064: failed to set group on directory string, errno number (string)
-
Cause: The group of the directory could not be changed.
- ACFS-11065: invalid device minor number number
-
Cause: The device minor number being used is out of range.
- ACFS-11066: the ADVM driver is not loaded
-
Cause: The ADVM driver is expected to exist in the kernel but it does not.
- ACFS-11067: directory /dev/asm does not exist or is not accessible, errno number (string)
-
Cause: The ADVM driver probably has not been successfully loaded.
- ACFS-11068: The state of device string is unknown. No operation was performed.
-
Cause: Unknown.
- ACFS-11069: Error: device name is too long, exceeding 255 characters.
-
Cause: The chosen device name exceeds the limit of 255 characters.
- ACFS-11078: unable to obtain cluster information for local node
-
Cause: An internal ioctl operation to access cluster information failed. This message is accompanied by other messages providing details on the error.
- ACFS-11083: insufficient OS kernel resources to defragment file string
-
Cause: An attempted defragment operation failed due to insufficient kernel resources.
- ACFS-11084: no space left on the file system
-
Cause: A defragment request failed because the file system was full.
- ACFS-11085: insufficient privileges to defragment file string
-
Cause: The caller does not have sufficient privileges to perform the defragment command on the indicated file. Write access is required for 'acfsutil defrag file'. Read access is required for 'acfsutil defrag file -i'.
- ACFS-11086: The specified path string is not a regular file.
-
Cause: An attempted defragment operation was rejected because the specified pathname was not a regular file.
- ACFS-11087: The specified path string is not a directory.
-
Cause: An attempted defragment operation was rejected because the specified pathname was not a directory.
- ACFS-11088: caught interrupt; stop defragmenting file string
-
Cause: Informational.
- ACFS-11089: failed to read from or write to file string
-
Cause: During defragmentation processing for the indicated file, an attempt to read or write data to disk failed.
- ACFS-11090: failed to defragment file string
-
Cause: During defragmentation processing for the indicated file, an internal ioctl request failed. This message is accompanied by other messages providing details on the error.
- ACFS-11091: unable to rename snapshot string because it is replication-specific
-
Cause: An attempt to rename a snapshot failed because it specified a replication-specific snapshot.
- ACFS-11092: Snapshot name string already exists.
-
Cause: The snapshot rename operation failed because the newly designated snapshot name was in use by another snapshot.
- ACFS-11095: 'acfsutil defrag' command is not supported for the current ADVM compatibility version. Version string is required.
-
Cause: The 'acfsutil defrag' command was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-11104: insufficient OS kernel resources to perform the command string
-
Cause: An attempt to execute the command 'acfsutil volstate' failed due to insufficient kernel resources.
- ACFS-11105: insufficient privileges to perform the command string
-
Cause: The caller does not have sufficient privileges to perform the command on the indicated mountpoint. Write access is required for 'acfsutil volstate -s'. Write access is required for 'acfsutil volstate -c'.
- ACFS-11106: failed to perform the command string
-
Cause: While accessing the volume, an internal ioctl request failed. The accompanying messages provide detailed failure information.
- ACFS-11111: string
-
Cause: None
- ACFS-12002: reclaiming snap remaster released storage
-
Cause: The 'acfsutil snap remaster' command has replaced the master file system with the remastered snapshot, releasing all the master's unique storage. In addition, any other snapshots that existed on the volume have also been removed, releasing all their unique storage. This storage was being marked as available in the Global_BitMap.
- ACFS-12003: 'snap remaster' phase: number\n
-
Cause: The indicated 'snap remaster' conversion phase has started.
- ACFS-12004: \ninvoking ACFS Checker, which will check the remastered snapshot file system, and ACFS Fixer, which will reclaim released storage\n
-
Cause: The ACFS Checker and the ACFS Fixer were reclaiming the storage released when the original master file system and other snapshots were deleted.
- ACFS-12005: \nSnapshot 'string' has been remastered as the master file system.\n
-
Cause: The specified snapshot has been remastered as the master file system. The original master file system and all the other snapshots have been deleted.
- ACFS-12200: missing required snapshot name
-
Cause: A 'snap remaster' command was issued without a required argument.
- ACFS-12201: Volume signature 'string' is invalid for snap remastering.
-
Cause: The volume signature indicated the volume was not in a state where 'snap remaster' can be performed.
- ACFS-12202: Volume signature indicates 'snap remaster' in progress.\n Signature: 'string'\n Use 'acfsutil snap remaster stringc string'\n to complete the 'snap remaster'.
-
Cause: The volume signature indicated that 'snap remaster' was being run on this volume.
- ACFS-12203: Volume signature 'string' indicates 'snap remaster' can be performed.\n However, on-disk 'snap remaster' phase (number) indicates 'snap remaster' is in progress.
-
Cause: The requested 'snap remaster' failed to run because the on-disk information indicated that another 'snap remaster' was in progress.
- ACFS-12204: The snap remastering phase 'number' is invalid.\n Valid phase range from number to number.
-
Cause: The on-disk snap remastering conversion phase had an invalid value.
- ACFS-12205: Snap remaster request for snapshot 'string' declined.\n\n
-
Cause: The user responded negatively when prompted to confirm the snapshot remastering.
- ACFS-12206: failed to fetch the ACFS Global metadata directory
-
Cause: Snap remaster failed to read the file system's ACFS Global metadata directory. Refer to accompanying messages for more information on the problem.
- ACFS-12207: failed to access the remastered snapshot 'string' File Entry Table
-
Cause: The File Entry Table for the snapshot being remastered could not be read. Refer to accompanying messages for more information on the problem.
- ACFS-12208: failed to copy the current 'string' file entry into the remastered snapshot 'string' File Entry Table
-
Cause: Snap remaster failed to copy the indicated file entry into the remastered snapshot File Entry Table. Refer to accompanying messages for more information on the problem.
- ACFS-12209: failed to access on-disk structure 'string'
-
Cause: Snap remaster failed to access the indicated on-disk structure. Refer to accompanying messages for more information on the problem.
- ACFS-12210: failed to copy remastered snapshot 'string' current File Entry Table file entry to the beginning of the remastered snapshot File Entry Table
-
Cause: Snap remaster failed to copy the snapshot to be remastered's file entry into the snapshots File Entry Table. Refer to accompanying messages for more information on the problem.
- ACFS-12211: failed to snapshot metadata from the snapshot information table
-
Cause: Snap remaster failed to zero the snapshot metadata for all the other snapshots from the snapshot information table. Refer to accompanying messages for more information on the problem.
- ACFS-12212: failed to reset the snapshot map header to indicate number active snapshots
-
Cause: Snap remaster failed to set the snapshot map header to the indicated number of active snapshots. Refer to accompanying messages for more information on the problem.
- ACFS-12213: failed to erase the snapshot entries from the '.ACFSstringsnapsstring' directory
-
Cause: Snap remaster failed to remove the deleted snapshot names from the indicated directory. Refer to accompanying messages for more information on the problem.
- ACFS-12214: failed to remove the remastered snapshot metadata from the snapshot information table
-
Cause: Snap remaster failed to snapsnot information table metadata for the snapshot being remastered. Refer to accompanying messages for more information on the problem.
- ACFS-12215: failed to clear the snapshot storage allocation map
-
Cause: Snap remaster failed to remove the storage allocations for the deleted snapshots. Refer to accompanying messages for more information on the problem.
- ACFS-12216: failed to save the current per-node local directory metadata entries for reuse
-
Cause: Snap remaster failed to obtain the local directory metadata entries for each cluster node, so that this information could be used in the remastered snapshot. Refer to accompanying messages for more information on the problem.
- ACFS-12217: failed to initialize the locator block metadata and local directory block metadata inside the remastered snapshot
-
Cause: Snap remaster failed to initialize the remastered snapshot locator block metadata and the local directory block metadata using data from the original master. Refer to accompanying messages for more information on the problem.
- ACFS-12218: failed to initialize the global directory block inside the remastered snapshot
-
Cause: Snap remaster failed to initialize the remastered snapshot global directory block for the remastered snapshot. Refer to accompanying messages for more information on the problem.
- ACFS-12219: remastering snapshot 'string' failed
-
Cause: A 'snap remaster' command failed. Refer to accompanying messages for more information on the problem.
- ACFS-12220: The continue option failed because there was no incomplete remastered snapshot.
-
Cause: The snapshot remastering continue option was specified for a file system that was not an interrupted snapshot remastering.
- ACFS-12221: failed to allocate a number byte 'string' buffer
-
Cause: There was insufficient memory to allocate working structures.
- ACFS-12222: failed to read 'string' from disk\n offset string size number
-
Cause: Snap remaster failed to read the indicated data structure from the file system. Refer to accompanying messages for more information on the problem.
- ACFS-12223: failed to read 'string' file entry number from disk\n offset string size number
-
Cause: Snap remaster failed to read the indicated file entry metadata from the file system. Refer to accompanying messages for more information on the problem.
- ACFS-12224: Failed to change the on-disk File Entry Table starting location (_VolFETALPosition).
-
Cause: Snap remaster failed to write the new File Entry Table starting offset to the remastered file system. Refer to accompanying messages for more information on the problem.
- ACFS-12225: failed to initialize extent 'Up Header' offsets and mark deleted snapshot file entries as free
-
Cause: Snap remaster failed to change the file extent 'Up Header' offsets so they are pointing to the remastered File Entry Table and to change the state of deleted snapshot file entries to available for allocation as new files. Refer to accompanying messages for more information on the problem.
- ACFS-12226: failed to read the file entry for the master file system File Entry Table
-
Cause: Snap remaster failed to read the file entry for the master File Entry Table. Refer to accompanying messages for more information on the problem.
- ACFS-12227: unexpected mode string in string
-
Cause: The reported function detected the wrong mode.
- ACFS-12228: The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than number.number.
-
Cause: The snapshot remaster operation was rejected because the ADVM disk group compatibility had not been upgraded to the indicated version, which is required for that command.
- ACFS-12229: Replication must be terminated before the volume can be remastered.
-
Cause: A 'snap remaster' command was issued for a volume that was being replicated.
- ACFS-12230: failed to find the snapshot 'string'
-
Cause: The specified snapshot was not found.
- ACFS-12231: failed to initialize file ID number for access
-
Cause: Snap remaster failed to initialize data structures allowing access to the indicated file ID.
- ACFS-12232: failed to create a file access structure for file ID number
-
Cause: Snap remaster failed to create a structure for accessing the indicated file ID. Refer to accompanying messages for more information on the problem.
- ACFS-12233: failed to access the remastered File Entry Table using file ID number
-
Cause: Snap remaster failed to read the File Entry Table for the remastered snapshot. Refer to accompanying messages for more information on the problem.
- ACFS-12234: failed to access the Snap Map file entry at file ID: number
-
Cause: Snap remaster failed to read the file entry for the Snap Map using the indicated file ID. Refer to accompanying messages for more information on the problem.
- ACFS-12235: failed to access the 'string' file entry at file ID: number
-
Cause: Snap remaster failed read the file entry for the indicated metadata using the indicated file ID. Refer to accompanying messages for more information on the problem.
- ACFS-12236: failed to access the Global BitMap file entry at file ID: number
-
Cause: Snap remaster failed to read the file entry for the Global BitMap using the indicated file ID. Refer to accompanying messages for more information on the problem.
- ACFS-12237: failed to read the file extent map for file ID number
-
Cause: Snap remaster failed to read file storage allocation information for the file ID indicated file. Refer to accompanying messages for more information on the problem.
- ACFS-12238: metadata write failed\n offset string size number file ID number
-
Cause: An attempt to write metadata of the indicated file ID failed. Refer to accompanying messages for more information on the problem.
- ACFS-12239: metadata copy failed\n file offset string size number file ID number
-
Cause: An attempt to write copied metadata to the indicated file ID failed. Refer to accompanying messages for more information on the problem.
- ACFS-12240: initializing metadata failed\n file offset string size number file ID number
-
Cause: An attempt to write initialized metadata to the indicated file ID failed. Refer to accompanying messages for more information on the problem.
- ACFS-12241: updating metadata failed\n file offset string size number file ID number
-
Cause: An attempt to write updated metadata to the indicated file ID failed. Refer to accompanying messages for more information on the problem.
- ACFS-12242: failed to update the extent headers with the new file ID number for the moved file entry
-
Cause: An error occurred while attempting to update the file extent headers with the new file ID after the file's file entry was moved to the remastered File Entry Table. Refer to accompanying messages for more information on the problem.
- ACFS-12243: failed to access the Accelerator Global BitMap file entry at file ID: number
-
Cause: Snap remaster failed to read the indicated file entry for the Accelerator Global BitMap. Refer to accompanying messages for more information on the problem.
- ACFS-12244: failed to read the snap map using file ID number
-
Cause: Snap remaster failed to initialize the snap entry table with snap map entries from the indicated file ID. Refer to accompanying messages for more information on the problem.
- ACFS-12245: failed to update the file extent parent pointers for file ID: number
-
Cause: An error occurred while attempting to update the file extent parent pointer after the file's file entry was moved to the remastered File Entry Table. Refer to accompanying messages for more information on the problem.
- ACFS-12246: failed to release file ID number file entry
-
Cause: An error occurred while releasing the indicated file entry. Refer to accompanying messages for more information on the problem.
- ACFS-12247: failed to fetch the remastered snapshot Global directory metadata: file ID number
-
Cause: Snap remaster failed to read the Global directory metadata using the indicated file ID from the remastered File Entry Table. Refer to accompanying messages for more information on the problem.
- ACFS-12248: failed to rebuild directory 'string': file ID number
-
Cause: Snap remaster failed to reconstruct the indicated file system directory after deleted files were removed. Refer to accompanying messages for more information on the problem.
- ACFS-12249: failed to allocate storage from the Global BitMap file ID: number
-
Cause: Snap remaster failed to find free storage in the Global BitMap. Refer to accompanying messages for more information on the problem.
- ACFS-12250: failed to find an expected string data structure on an in-memory linked list
-
Cause: Snap remaster failed to find the indicated data structure.
- ACFS-12251: failed to add file ID number to the File Entry Table free list
-
Cause: Snap remaster failed to add the indicated file ID to the remastered File Entry Table list of available for reuse file entries. Refer to accompanying messages for more information on the problem.
- ACFS-12252: failed to add file ID number to the in-memory file entry cache
-
Cause: Snap remaster failed to read the indicated file ID and add it to the file entry cache for reuse in the remastered snapshot. Refer to accompanying messages for more information on the problem.
- ACFS-12253: failed to update file ID number storage
-
Cause: An error occurred while updating the indicated file entry's storage. Refer to accompanying messages for more information on the problem.
- ACFS-12254: failed to remove the file ID number storage
-
Cause: An error occurred while removing the indicated file entry's storage. Refer to accompanying messages for more information on the problem.
- ACFS-12255: failed to delete file names from directory 'string'
-
Cause: Snap remaster failed to delete the files in the indicated directory. Refer to accompanying messages for more information on the problem.
- ACFS-12256: failed to delete all the .ACFSstringreplstring subdirectories
-
Cause: Snap remaster failed to delete all the subdirectories in the indicated directory. Refer to accompanying messages for more information on the problem.
- ACFS-12257: Snapshot 'string' replication must be terminated before the volume can be remastered.
-
Cause: A 'snap remaster' command was issued for a volume that was was replicating snapshots.
- ACFS-12258: cannot find the ACFS Checker and Fixer utility: string
-
Cause: The 'snap remaster' back-end utility (the ACFS Checker and Fixer) could not be found.
- ACFS-12259: ACFS Checker and Fixer returned an error.
-
Cause: The 'snap remaster' back-end utility (ACFS Checker and Fixer) returned an error. Refer to accompanying messages for more information on the problem.
- ACFS-12260: ACFS Checker and Fixer failed to perform the 'snap remaster'\n command: string
-
Cause: The indicated ACFS Checker and Fixer command failed.
- ACFS-12261: Volume signature indicates 'snap remaster' was in progress.\n Signature: 'string'\n Use\n 'acfsutil snap remaster stringc string'\n to complete the 'snap remaster'.\n Or to reformat the volume, reissue string with the stringf option.
-
Cause: The volume signature indicates that 'snap remaster' was being run on this volume.
- ACFS-12262: 'snap remaster' rejected because this file system uses an accelerator volume.
-
Cause: 'snap remaster' command was issued for a file system with an accelerator volume.
- ACFS-12263: ACFS Plugins must be disabled before the file system can be remastered.
-
Cause: An 'acfsutil snap remaster' command was rejected because the specified file system had Oracle ACFS plug-ins enabled.
- ACFS-12264: ACFS Plugins are enabled on node: string.
-
Cause: An 'acfsutil snap remaster' command was rejected because the specified file system had Oracle ACFS plug-ins enabled on the indicated node.
- ACFS-12265: 'snap remaster' cannot be used on a file system with ACFS security.
-
Cause: An 'acfsutil snap remaster' command was rejected because the specified file system had Oracle ACFS security enabled.
- ACFS-12266: 'snap remaster' cannot be used on a file system with ACFS encryption.
-
Cause: An 'acfsutil snap remaster' command was rejected because the specified file system had Oracle ACFS encryption enabled.
- ACFS-12267: failed to clean the .ACFS directory tree
-
Cause: An attempt to remaster an Oracle ACFS snapshot failed to clean the .ACFS directory tree. The accompanying messages provide detailed failure information.
- ACFS-12268: failed to copy the .ACFS directory tree to the snapshot
-
Cause: An attempt to remaster an Oracle ACFS snapshot failed to copy the .ACFS directory tree to the snapshot. The accompanying messages provide detailed failure information.
- ACFS-12269: failed to update directory string
-
Cause: An attempt to remaster an Oracle ACFS snapshot failed to update the indicated directory. The accompanying messages provide detailed failure information.
- ACFS-12270: failed due to remapped metadata files from a prior file system shrink
-
Cause: An attempt to remaster an Oracle ACFS snapshot failed because the specified snapshot contains metadata files that were remapped as part of a prior file system shrink. Such files would prevent the remastered file system from mounting.
- ACFS-12271: Unable to obtain ftrace information for mount point 'string'.
-
Cause: An attempt to obtain ftrace information failed. The accompanying messages provide detailed failure information.
- ACFS-12274: failed to clear the snapshot storage interest tracking map
-
Cause: Snap remaster failed to remove the storage interest tracking Map for the deleted snapshots. Refer to accompanying messages for more information on the problem.
- ACFS-12275: failed to access the storage interest tracking map file entry for the string volume
-
Cause: Snap remaster failed to read the file entry for the storage interest tracking map on the indicated volume. Refer to accompanying messages for more information on the problem.
- ACFS-13000: unable to determine the cluster type
-
Cause: An 'advmutil' command failed to determine the type of cluster that contained the local server. The accompanying messages provide detailed failure information.
- ACFS-13001: insufficient privileges - ASM administrator group access required
-
Cause: A requested 'advmutil' command failed because the user did not have the required ASM Administrator privilege.
- ACFS-13002: Command is not supported on a cluster of the current type.
-
Cause: A requested 'advmutil export' or 'advmutil transport' command failed because the command could only be run on a Domain Services Cluster.
- ACFS-13016: A failure occurred while updating the currently active export list for cluster 'string'.
-
Cause: An 'advmutil export create' or 'advmutil export mapping' command failed because an error occurred when attempting to modify the currently active configuration for the indicated cluster. Accompanying messages provide further failure details.
- ACFS-13017: The update of active exports for cluster 'string' succeeded.
-
Cause: Informational.
- ACFS-13032: invalid combination of 'fileSize' and 'force' options
-
Cause: The 'advmutil export create' command was rejected because the 'fileSize' and 'force' options were both used on the command line.
- ACFS-13033: The 'force' option cannot be used if the backing store does not exist.
-
Cause: The 'advmutil export create' command was rejected because the 'force' option was specified and the backing store did not exist.
- ACFS-13034: insufficient file space - requested: string available: string
-
Cause: An 'advmutil export' or 'advmutil resize' command failed because writing the file required the indicated additional space when only the indicated space was available.
- ACFS-13035: missing exportName
-
Cause: An 'advmutil export' command was rejected because the exportName argument was not specified.
- ACFS-13036: The location 'string' exists but is not a directory.
-
Cause: An advmutil export command failed because the indicated location for the storage repository existed on disk and was not a directory.
- ACFS-13037: missing storageRepo
-
Cause: An advmutil export command was rejected because the storageRepo argument was not specified.
- ACFS-13038: The specified 'exportName' is longer than the maximum length number.
-
Cause: An advmutil export command was rejected because the exportName exceeded the indicated maximum length.
- ACFS-13039: The storageRepo/exportName 'string' exists but is not a file.
-
Cause: An 'advmutil export create' or advmutil transport create' command failed because it expected the location pointed to by the specified storageRepo and exportName to be a file or not to exist. The path pointed to an existing, on-disk, object that was not a file.
- ACFS-13040: missing clusterName
-
Cause: An 'advmutil export', 'advmutil transport', or 'advmutil resize' command was rejected because the clusterName was not specified.
- ACFS-13041: The export 'string' for cluster 'string' already exists as file path 'string'.
-
Cause: An 'advmutil export create' command failed because a file already existed on disk at the indicated location.
- ACFS-13042: unable to create file 'string'
-
Cause: An 'advmutil export create' or 'advmutil export resize' command failed to create or resize the indicated file in the specified storage repository.
- ACFS-13043: missing size option
-
Cause: An 'advmutil export create' or 'advmutil export resize' command was rejected because the size argument was not specified.
- ACFS-13044: Unable to determine the GUID for cluster 'string'.
-
Cause: The requested advmutil command failed because it was unable to determine the Globally Unique Identifier (GUID) for the indicated cluster name. The accompanying messages provide further failure details.
- ACFS-13047: Invalid file size string is smaller than the minimum supported file size string.
-
Cause: An 'advmutil export create' or 'advmutil export resize' was rejected because the indicated size is smaller than the indicated supported minimum file size.
- ACFS-13048: The file path for export name 'string' is longer than the maximum allowed 'number' characters.
-
Cause: An 'advmutil export create' command was rejected because the provided arguments for storageRepo, clusterName, and exportName resulted in a file path storageRepo/clusterGUID/exportName that was longer than the indicated maximum path length.
- ACFS-13049: The location 'string' is not a mounted ACFS file system.
-
Cause: An 'advmutil export create' command failed because the indicated location, specified as storageRepo, was not an ACFS file system.
- ACFS-13050: File 'string' does not exist.
-
Cause: An 'advmutil export resize' or 'advmutil transport create' command failed because the indicated file did not exist.
- ACFS-13052: Failed to create export 'string' for cluster 'string'.
-
Cause: An 'advmutil export create' command failed because the specified export could not be created. The accompanying messages provide further failure details.
- ACFS-13054: The specified export already exists in the Oracle Cluster Registry (OCR).
-
Cause: An 'advmutil export create' was rejected because the export already existed in the Oracle Cluster Registry (OCR).
- ACFS-13061: missing exportName or storageRepo
-
Cause: An 'advmutil export remove' command was rejected because both exportName and storageRepo must be specified on the command line, and one of them was not specified.
- ACFS-13062: File 'string' does not exist.
-
Cause: An 'advmutil export remove' or 'advmutil export list' command expected to find the indicated file, which did not exist.
- ACFS-13067: Unable to remove export 'string' from cluster 'string'.
-
Cause: An 'advmutil export remove' command failed because it could not remove the indicated export from the indicated cluster. The accompanying messages provide further failure details.
- ACFS-13068: unable to clear ACFS remote usage attribute for file 'string'
-
Cause: An attempt to remove the indicated file from usage in a specified storage repository failed because the ACFS Remote attribute could not be cleared. If the ACFS remote usage attribute is set, the file will not be deleted and its storage will not be removed as part of the export remove.
- ACFS-13069: unable to open backing store file 'string'
-
Cause: An attempt to remove the indicated ACFS remote backing storage file from usage in a specified storage repository failed because the file could not be opened to clear the ACFS remote attribute. Additional messages provide detailed failure information.
- ACFS-13076: Invalid options 'string' specified. Valid options are 'string'.
-
Cause: An 'advmutil export list' command was rejected because the indicated option was not valid.
- ACFS-13077: invalid group type 'string' specified
-
Cause: An 'advmutil export list' command was rejected because the specified group type was not a valid group type. Valid groups are 'clusterName', 'clusterGUID', and 'storageRepo'.
- ACFS-13078: unable to find the cluster name for the GUID 'string'
-
Cause: An 'advmutil export list' command failed because it was unable to determine the cluster name from the Globally Unique Identifier (GUID). The accompanying messages provide further failure details.
- ACFS-13079: more options specified than the maximum allowed: number
-
Cause: An 'advmutil export list command' was rejected because more options were specified than the indicated maximum.
- ACFS-13081: Export list failed.
-
Cause: An advmutil export list' command failed because the system call to retrieve the export information failed. The accompanying messages provide further failure details.
- ACFS-13083: unable to mark file 'string' for ACFS remote usage
-
Cause: An operation to mark the indicated file for ACFS Remote usage in a specified storage repository failed. This will not affect normal usage as a ACFS remote backing store, however with the ACFS remote attribute not set the file will not be protected from local modification.
- ACFS-13092: invalid file size or file size increment specified
-
Cause: An 'advmutil export size' command was rejected because an invalid file size or file size increment was specified.
- ACFS-13107: no available sequence number
-
Cause: An 'advmutil transport create' command failed because all of the available transport sequence numbers for the specified transport type were in use.
- ACFS-13109: Transport resource 'string' is in use by other transports.
-
Cause: An 'advmutil transport create' command was rejected because the indicated resource existed and was in use by other transports.
- ACFS-13110: Transport 'string' already exists on cluster 'string'.
-
Cause: An 'advmutil export create' command was rejected because the indicated transport already existed on the indicated cluster.
- ACFS-13115: missing transportID
-
Cause: An 'advmutil transport remove' command was rejected because the transportID argument was not specified."
- ACFS-13116: invalid transport ID 'string'
-
Cause: An 'advmutil transport remove' command was rejected because the indicated transport identifier was not specified in the form 'transportType.sequenceNumber'.
- ACFS-13117: The transport 'string.string' does not exist for cluster 'string'.
-
Cause: An 'advmutil transport remove' command failed because the transport did not exist for the indicated cluster name.
- ACFS-13119: No eligible exports were found.
-
Cause: No exports existed for the specified input criteria.
- ACFS-13130: Both clusterName and clusterGUID were specified on the command line.
-
Cause: An 'advmutil transport list' command was rejected because both the clusterName and the clusterGUID were specified on the command line.
- ACFS-13131: missing clusterName or clusterGUID
-
Cause: An 'advmutil transport list' command was rejected because a transportID was specified without also specifying a clusterGUID or a clusterName on the command line.
- ACFS-13132: missing transportID argument
-
Cause: An 'advmutil transport list' command was rejected because the verbose option was specified without specifying a transportID.
- ACFS-13133: No eligible transports were found.
-
Cause: No transports existed for the specified input criteria.
- ACFS-13150: unknown system call failure - 'ASDO_E_FAILURE'
-
Cause: The requested operation failed because of an unhandled kernel ioctl error. The accompanying messages provide further failure details.
- ACFS-13151: invalid user address passed to the 'oracleadvm' driver -'ASDO_E_FAULT'
-
Cause: The requested operation failed because the oracleadvm driver attempted to access an invalid user memory address.
- ACFS-13152: GUID for the cluster name not found - 'ASDO_E_GUID_NOT_FOUND'
-
Cause: The requested operation failed because it could not determine the Globally Unique IDentifier. Additional messages may accompany this to provide further failure details.
- ACFS-13153: invalid argument - 'ASDO_E_INVAL_ARG'
-
Cause: The requested operation failed because an invalid argument was passed to a system call.
- ACFS-13154: invalid system call opcode - 'ASDO_E_INVAL_TYPE'
-
Cause: The requested operation failed because an invalid opcode was passed to a system call.
- ACFS-13155: specified storage repository not mounted - 'ASDO_E_REPOMOUNT_NOT_FOUND'
-
Cause: The requested operation failed because the storage repository was not mounted.
- ACFS-13156: required file path not found - 'ASDO_E_PATH_NOT_FOUND'
-
Cause: The requested operation failed because the kernel could not find the required path.
- ACFS-13157: repository directory not found - 'ASDO_E_REPOPATH_NOT_FOUND'
-
Cause: The requested operation failed because the required repository directory was not found.
- ACFS-13158: insufficient memory - 'ASDO_E_NOMEM'
-
Cause: The operation failed because the 'oracleadvm' driver could not allocate sufficient kernel memory to perform the operation.
- ACFS-13159: device special file not found- 'ASDO_E_DSF_NOT_FOUND'
-
Cause: The operation failed because the 'oracleadvm' driver could not find the specified device special file in /dev/acfsr.
- ACFS-13170: export lsof ioctl failed
-
Cause: An 'advmutil export lsof' command failed because the system call to retrieve the export information failed. The accompanying messages provide further failure details.
- ACFS-13171: getCurNumExports ioctl failed
-
Cause: An 'advmutil export lsof' command failed because the system call to retrieve the export information failed. The accompanying messages provide detailed failure information.
- ACFS-13190: Command is not supported on a cluster of the current type.
-
Cause: An 'advmutil session list' command failed because the command could only be run on a Member Cluster.
- ACFS-13192: invalid sequence number number
-
Cause: An 'advmutil session list' command was rejected because the indicated sequence number was out-of-range.
- ACFS-13193: Node 'string' does not exist on this cluster.
-
Cause: An 'advmutil session list' command failed because the specified node was not a member of this cluster.
- ACFS-13194: invalid transport type 'string' specified
-
Cause: An 'advmutil session list' command was rejected because the indicated transport type specified on the command line was invalid.
- ACFS-13195: No eligible sessions were found.
-
Cause: No sessions exist for the specified input criteria.
- ACFS-13250: The resource name 'string' specified by resource id 'string' does not exist.
-
Cause: An 'advmutil transport create' command was rejected because the indicated resource identifier did not resolve to an existing transport resource.
- ACFS-13251: Resource ID may not be specified together with network number or host binding.
-
Cause: An 'advmutil transport create' command was rejected because the resource ID option was specified with the network number or host binding option (or both) on the command line.
- ACFS-13252: cannot create a CRS resource ('string') that already exists
-
Cause: An 'advmutil transport create' command failed because the command attempted to create a Cluster Ready Services (CRS) resource that already existed. This is an internal error.
- ACFS-13253: The 'bind' option must be specified on the command line.
-
Cause: An 'advmutil transport create' command was rejected because the 'bind' option was not specified on the command line.
- ACFS-13254: The binding VIP 'string' does not exist in the Domain Name System (DNS).
-
Cause: An 'advmutil transport create' command was rejected because the indicated binding VIP (host name or network address) was unknown.
- ACFS-13255: The supplied network number 'string' is invalid.
-
Cause: An 'advmutil transport create' command was rejected because the specified network number was not a positive digit.
- ACFS-13256: Entries specified on the command line already exist in the OCR.
-
Cause: An 'advmutil transport create' command was rejected because the bind host name or network address are already in the Oracle Cluster Registry (OCR).
- ACFS-13257: The specified network number 'string' does not exist in the Oracle Cluster Ready Services (CRS).
-
Cause: An 'advmutil transport create' command was rejected because an invalid network number was specified on the command line.
- ACFS-13258: Failed to retrieve 'string' for resource 'string': error number
-
Cause: An 'advmutil transport create' command failed because it could not retrieve the indicated item from the indicated resource. The accompanying messages provide detailed failure information.
- ACFS-13259: Waiting for competing advmutil process to finish.
-
Cause: The file /tmp/advmutil.lock was locked by a running advmutil process.
- ACFS-13300: Cannot query Cluster Ready Services (CRS) resource 'string'.
-
Cause: An 'advmutil transport' or 'advmutil export' command failed because it could not query the indicated resource. The accompanying messages provide detailed failure information.
- ACFS-13301: Invalid CRS attribute format detected in resource 'string'.
-
Cause: An Cluster Ready Services (CRS) resource start or stop dependency format error was detected. This is an internal error.
- ACFS-13302: Failed to get ACFS mount points from Cluster Ready Services (CRS).
-
Cause: An 'advmutil export create' or 'advmutil export remove' command failed because it could not query ACFS mount points. The accompanying messages provide detailed failure information.
- ACFS-13303: The Cluster Ready Services (CRS) cannot be initialized.
-
Cause: An 'advmutil transport' or 'advmutil export' command failed because the initialization of the Cluster Ready Services (CRS) failed. The accompanying messages provide detailed failure information.
- ACFS-13304: The bind host name or network address 'string' is already in use in the network.
-
Cause: An 'advmutil transport create' command was rejected because the indicated host name or network address specified on the command line was in use in the network and was therefore not generally available for the transport.
- ACFS-13305: Failed to start Cluster Ready Services (CRS) resource 'string'.
-
Cause: "An 'advmutil transport create' failed because the indicated Cluster Ready Services (CRS) resource failed to start. The accompanying messages provide detailed failure information.
- ACFS-13306: The Cluster Ready Services (CRS) resource 'string' cannot be updated.
-
Cause: An 'advmutil transport create' command failed because it was unable to update the indicated resource. The accompanying messages provide detailed failure information.
- ACFS-13307: Failed to retrieve the resource 'string' error 'number'.
-
Cause: An 'advmutil transport create' failed to cause it could not retrieve the indicated resource. The accompanying messages provide detailed failure information.
- ACFS-13308: Failed to retrieve the start/stop dependencies or state for resource 'string': error number
-
Cause: An 'advmutil transport create', 'advmutil export create', or 'advmutil export remove' command failed because it could not retrieve the current start or stop dependency or the resource state for the indicated resource. The accompanying messages provide detailed failure information.
- ACFS-13309: Failed to set the 'string' resource attribute for resource 'string': error number
-
Cause: An 'advmutil transport create' failed because it could not set the start and stop dependencies for the indicated resource. The accompanying messages provide detailed failure information.
- ACFS-13310: Failed to stop Oracle Ready Services (CRS) resource 'string'.
-
Cause: An 'advmutil transport remove' command failed because the indicated resource could not be stopped. The accompanying messages provide detailed failure information.
- ACFS-13311: Failed to delete Oracle Ready Services (CRS) resource 'string'.
-
Cause: An 'advmutil transport remove' command failed because the indicated resource could not be deleted. The accompanying messages provide detailed failure information.
- ACFS-13312: The Cluster Ready Services (CRS) resource 'string' does not exist.
-
Cause: An 'advmutil transport remove' command detected that an expected CRS resource did not exist.
- ACFS-13313: The transport identifier 'string' was not found in the Oracle Cluster Registry (OCR).
-
Cause: An 'advmutil export create' command failed because it could not find a transport identifier in the Oracle Cluster Registry (OCR).
- ACFS-13314: Failed to add start and stop dependencies to Cluster Ready Services (CRS) resource 'string'.
-
Cause: An 'advmutil transport create' command failed because it could not add start and stop dependencies to the indicated resource. The accompanying messages provide detailed failure information.
- ACFS-13315: failed to remove Cluster Ready Services (CRS) resource 'string'
-
Cause: An 'advmutil export remove' command failed to remove the indicated start and stop dependency from the applicable transport resource. The accompanying messages provide detailed failure information.
- ACFS-13316: failed to add cluster Ready Services (CRS) resource 'string'
-
Cause: An 'advmutil export create' command failed to add the indicated resource to the Cluster Ready Resources (CRS). The accompanying messages provide detailed failure information.
- ACFS-13317: Failed to create Cluster Ready Services (CRS) resource 'string': error 'number'.
-
Cause: An 'advmutil transport create' command failed to create the indicated resource. The accompanying messages provide detailed failure information.
- ACFS-13318: failed to find the file system resource name for the storage repository mount point 'string' for cluster 'string'
-
Cause: An 'advmutil export create' command failed because it could not find the resource name for the mount point of the indicated storage repository for the indicated cluster.
- ACFS-13319: Warning: Verify Cluster Ready Services (CRS) resource 'string' is started on all nodes
-
Cause: An 'advmutil export create' failed to start the indicated filesystem resource on all the cluster nodes.
- ACFS-13375: The export name 'string' contains non-alphanumeric characters.
-
Cause: An advmutil export command was rejected because the indicated export name contained non-alphanumeric characters.
- ACFS-13376: invalid size specification 'string'
-
Cause: An 'advmutil export create' or 'advmutil export resize' command was rejected because the indicated size specification was invalid. A valid size consists of a numeric value followed by 'K', 'M', 'G', 'T', 'P', or 'E'.
- ACFS-13377: The storage repository 'string' is compressed or has compressed files.
-
Cause: An 'advmutil export create' command was rejected because the indicated storage repository was compressed or contained compressed files.
- ACFS-13378: Specified network 'string' uses address family 'string', which is incompatible with the address family 'string' of the specified binding 'string'.
-
Cause: An 'advmutil transport create' was rejected because the address family of the indicated network (e.g., IPv4) did not match that of the indicated binding.