ACFSK-00004 to ACFSK-00099

3 ACFSK-00004 to ACFSK-00099

ACFSK-00004: The Security file for volume mounted at %2 cannot be created (error status %3), and so the volume cannot be used by this node.: Cause: This is not a simple disk-full condition.; Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00005: The Security file for volume %2 cannot be created (error status %3), and so the volume cannot be used by this node.: Cause: This is not a simple disk-full condition.; Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00006: The Security file for volume with device minor number %2 cannot be created (error status %3), and so the volume cannot be used by this node.: Cause: This is not a simple disk-full condition.; Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00007: The Security file for volume mounted at %2 cannot be created because the filesystem is full.: Cause: because the filesystem is full. The volume cannot be used by this node until the Security file is successfully created.; Action: Either expand the storage available for this ACFS volume using the "acfsutil size" command or reduce the space being used.
ACFSK-00008: The Security file for volume %2 cannot be created because the filesystem is full.: Cause: because the filesystem is full. The volume cannot be used by this node until the Security file is successfully created.; Action: Either expand the storage available for this ACFS volume using the "acfsutil size" command or reduce the space being used.
ACFSK-00009: The Security file for volume with device minor number %2 cannot be created because the filesystem is full.: Cause: because the filesystem is full. The volume cannot be used by this node until the Security file is successfully created.; Action: Either expand the storage available for this ACFS volume using the "acfsutil size" command or reduce the space being used.
ACFSK-00010: The Security file for volume mounted at %2 cannot be created due to insufficient memory.: Cause: probably due to insufficient memory, and so the filesystem cannot be used at this node.; Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00011: The Security file for volume %2 cannot be created due to insufficient memory.: Cause: probably due to insufficient memory, and so the filesystem cannot be used at this node.; Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00012: The Security file for volume with device minor number %2 cannot be created due to insufficient memory.: Cause: probably due to insufficient memory, and so the filesystem cannot be used at this node.; Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00013: The Security information for volume mounted at %2 file %3 is missing.: Cause: An ACL granting full access to Administrators has been associated with the file.; Action: Modify the ACL as required.
ACFSK-00014: The Security information for volume %2 file %3 is missing.: Cause: An ACL granting full access to Administrators has been associated with the file.; Action: Modify the ACL as required.
ACFSK-00015: The Security information for volume with device minor number %2 file %3 is missing.: Cause: An ACL granting full access to Administrators has been associated with the file.; Action: Modify the ACL as required.
ACFSK-00019: Volume %2 now OFFLINE. Internal ACFS Location %3 .: Cause: A problem accessing valid file system metadata was seen at a critical point during processing. All attempts to read or write files will fail on this node.; Action: unmount and remount the file system on this node. See the ACFS Administration Guide for more information about OFFLINE file systems.
ACFSK-00020: RECOVERY requested for volume %2 . Internal ACFS Location %3 .: Cause: ACFS has initiated recovery for the volume.; Action: n/a
ACFSK-00021: FSCK-NEEDED set for volume %2 . Internal ACFS Location %3 .: Cause: A problem has been detected with the file system metadata in the above volume.; Action: Normal operation can continue, but it is advisable to run fsck/acfschkdsk in the fixer mode on the file system as soon as it is feasible to do so. See the ACFS Administration Guide for more information about FSCK-NEEDED.
ACFSK-00022: Mount for volume at %2 succeeded but there was a previous metadata error.: Cause: Metadata error.; Action: Run fsck/acfschkdsk as soon as possible.
ACFSK-00023: Mount for volume %2 succeeded but there was a previous metadata error.: Cause: Metadata error.; Action: Run fsck/acfschkdsk as soon as possible.
ACFSK-00024: Mount for volume with device minor number %2 succeeded but there was a previous metadata error.: Cause: Metadata error.; Action: Run fsck/acfschkdsk as soon as possible.
ACFSK-00025: On the volume mounted at %2, file %3 is memory mapped for write on this node and another node is about to modify it.: Cause: Concurrent sharing is not supported for mmaped files. This may result in the file contents becoming inconsistent.; Action: Un-mmap the file.
ACFSK-00026: On the volume mounted at %2 file %3 is memory mapped for write on this node and another node is about to modify it.: Cause: Concurrent sharing is not supported for mmaped files. This may result in the file contents becoming inconsistent.; Action: Un-mmap the file.
ACFSK-00027: On the volume with device minor number %2 file %3 is memory mapped for write on this node and another node is about to modify it.: Cause: Concurrent sharing is not supported for mmaped files. This may result in the file contents becoming inconsistent.; Action: Un-mmap the file.
ACFSK-00028: An attempt to open a file reached the system limit for open ACFS files.: Cause: The number of open files was already at the system limit when an attempt was made to open another file.; Action: This limit can be increased by changing the AcfsMaxOpenFiles tuneable using the acfsutil command.
ACFSK-00029: Volume %2 is now offline: Cause: See preceding messages.; Action: See preceding messages.
ACFSK-00030: ASM Instance has Failed.: Cause: The ASM instance was either intentionally stopped or it failed.; Action: See ASM trace messages if this was not intentional. Restart ASM.
ACFSK-00032: Mount failed for device minor number %2 with status %3 .: Cause: Mount request failed with status indicated.; Action: Try to mount again. If it fails again, run the file system checker and try to mount again. If that fails, inform Oracle Support Services.
ACFSK-00033: Information pertaining to a metadata error has been saved in the file %2 .: Cause: A metadata error was detected and relevant data was saved for future examination.; Action: Display the file to learn which volume experienced the problem and then run acfschkdsk when it is feasible to do so. Include the contents of the mentioned file if reporting this problem to Oracle.
ACFSK-00034: In volume mounted at %2, snapshots for memory-mapped file with file identifier %2 are no longer valid.: Cause: ACFS was unable to obtain sufficient storage within the volume in order to maintain the validity of the snapshot versions of this file.; Action: To avoid further errors of this type, either expand the storage available for this ACFS volume or reduce the space being used. Run the command "acfsutil info id %3" to get the pathname of the file.
ACFSK-00035: In volume %2, snapshots for memory-mapped file with file identifier %3 are no longer valid.: Cause: ACFS was unable to obtain sufficient storage within the volume in order to maintain the validity of the snapshot versions of this file.; Action: To avoid further errors of this type, either expand the storage available for this ACFS volume or reduce the space being used. Run the command "acfsutil info id %3" to get the pathname of the file.
ACFSK-00036: In volume with device minor number %2, snapshots for memory-mapped file with file identifier %3 are no longer valid.: Cause: ACFS was unable to obtain sufficient storage within the volume in order to maintain the validity of the snapshot versions of this file.; Action: To avoid further errors of this type, either expand the storage available for this ACFS volume or reduce the space being used. Run the command "acfsutil info id %3" to get the pathname of the file.
ACFSK-00038: Module failed to load and start with status %2. Build information: %3 %4 %5: Cause: The operating system could not load the ACFS driver.; Action: Contact Oracle Support Services if the corrective action based on the status is not clear.
ACFSK-00040: Mount failed for device minor number %2 with status %3 . Error found in superblock.: Cause: ACFS does not recognize a valid ACFS superblock on the indicated device.; Action: If there should be a valid ACFS file system on the indicated device, run acfschkdsk to attempt to repair the superblock.
ACFSK-00041: Mount failed for device minor number %2 with status %3. Cluster membership is not established.: Cause: This node is not a member of the cluster.; Action: Ensure ASM is up and functional.
ACFSK-00042: Mount failed for device minor number %2 with status %3. Insufficient kernel resources to complete the mount.: Cause: The mount request failed due to a lack of operating system resources. This is likely to be a transient failure.; Action: Try to mount again. If it fails again, inform Oracle Support Services.
ACFSK-00044: Metadata validation error encountered on volume mounted at %2. A read retry succeeded for file identifier %3 starting disk offset %4.: Cause: ACFS detected a problem with the content of metadata read from the disk but reading again provided valid data.; Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00045: Metadata validation error encountered on volume %2. A read retry succeeded for file identifier %3 starting disk offset %4.: Cause: ACFS detected a problem with the content of metadata read from the disk but reading again provided valid data.; Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00046: Metadata validation error encountered on volume with device minor number %2. A read retry succeeded for file identifier %3 starting disk offset %4.: Cause: ACFS detected a problem with the content of metadata read from the disk but reading again provided valid data.; Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00047: Metadata validation error encountered on volume mounted at %2. A read retry failed for file identifier %3 starting disk offset %4.: Cause: ACFS detected a problem with the content of metadata read from the disk and reading again did not provide valid data.; Action: Run the file system checker as soon as possible.
ACFSK-00048: Metadata validation error encountered on volume %2. A read retry failed for file identifier %3 starting disk offset %4.: Cause: ACFS detected a problem with the content of metadata read from the disk and reading again did not provide valid data.; Action: Run the file system checker as soon as possible.
ACFSK-00049: Metadata validation error encountered on volume with device minor number %2. A read retry failed for file identifier %3 starting disk offset %4.: Cause: ACFS detected a problem with the content of metadata read from the disk and reading again did not provide valid data.; Action: Run the file system checker as soon as possible.
ACFSK-00052: Volume %2 (Major: %3, Minor: %4) mount failed. Volume is out of space.: Cause: Mount failed due to insufficient space available in the volume.; Action: Either expand the storage available for this ACFS volume using the "acfsutil size" command or reduce the space being used.
ACFSK-00053: Volume %2 (Major: %3, Minor: %4) mount failed. Volume version does not match the ACFS driver version.: Cause: The mount failed because the version of ACFS in the kernel is not compatible with the version of the volume stored on disk.; Action: If this file system was created with newer drivers, the ADVM compatibility was increased, and new features were used, then it is not possible to mount this file system with an older driver. Otherwise, ensure the correct drivers and tools are installed. Running fsck/acfschkdsk may provide further clues.
ACFSK-00054: Volume %2 (Major: %3, Minor: %4) mount failed with internal status code (%5).: Cause: The mount failed because ACFS detected an internal error.; Action: Verify that the version of ACFS being run is corect. If it is, inform Oracle Support Services.
ACFSK-00055: Volume %2 (Major: %3, Minor: %4) mount failed. Cluster membership is not established.: Cause: The mount failed because this node is not in a cluster.; Action: Ensure ASM is configured properly. Wait until the node has joined a cluster and try again.
ACFSK-00056: Volume %2 (Major: %3, Minor: %4) mount failed. Insufficient kernel resources to complete the mount.: Cause: The mount failed because of a resource problem, possibly temporary and probably kernel memory.; Action: Try the mount again. If it fails again, inform Oracle Support Services.
ACFSK-00057: Volume %2 (Major: %3, Minor: %4) mount failed. Error in superblock.: Cause: A problem has been detected in the superblock.; Action: Run fsck/acfschkdsk when possible and try to mount again. If it fails again, inform Oracle Support Services.
ACFSK-00061: An ACFS Assertion failed at %2 line %3.: Cause: An ACFS Assertion failed.; Action: See the next message from Oracle OKS which may contain the location of a file containing further information. Include the contents of this file if reporting the problem to Oracle
ACFSK-00062: An I/O error was encountered while invalidating a replication log record. Replication is being terminated for file system %2.: Cause: This leaves the primary and standby sites out of sync, so replication is being terminated for file system %2.; Action: n/a
ACFSK-00063: Acfs kernel extension configuration failed. Diagnostic codes: %2 %3 / %4 %5 / %6 .: Cause: An error was seen during Acfs configuration and/or initialization.; Action: Inform Oracle Support Services and provide the message displayed.
ACFSK-00064: Logging to the file %2 has stopped. Backup the log archive %3%4 to a new location if required, and then remove the log archive to restart logging.: Cause: Log file size limit reached while the log archive still exists.; Action: Backup the log archive to a new location if required, and then remove the log archive.
ACFSK-00065: Log file %2 has been archived at location %3%4.: Cause: The log file was archived since the file reached its specified size limit. Meanwhile, logging to the original file will continue.; Action: Backup the log archive to a new location if required, and then remove the log archive. Failing to do this before the log file fills again will result in loss of log data.
ACFSK-00066: An archive of the log file %2 exists at location %3%4.: Cause: Active log file is reaching its specified size limit and the log archive has not been removed. Logging will stop after active log file reaches its specified size limit and the log archive still has not been removed.; Action: Backup the log archive to a new location if required, and then remove the log archive. Failing to do this before the log file fills again will result in loss of log data.
ACFSK-00067: Logging to the file %2 has stopped. Backup the log archive %3%4 to a new location if required, and then remove the log archive to restart logging.: Cause: Log file size limit reached while the log archive still exists.; Action: Contact an ACFS Security Administrator to backup the log archive to a new location if required, and then remove the log archive.
ACFSK-00068: Log file %2 has been archived at location %3%4.: Cause: The log file was archived since the file reached its specified size limit. Meanwhile, logging to the original file will continue.; Action: Contact an ACFS Security Administrator to backup the log archive to a new location if required, and then remove the log archive. Failing to do this before the log file fills again will result in loss of log data.
ACFSK-00069: An archive of the log file %2 exists at location %3%4.: Cause: Active log file is reaching its specified size limit and the log archive has not been removed. Logging will stop after active log file reaches its specified size limit and the log archive still has not been removed.; Action: Contact an ACFS Security Administrator to backup the log archive to a new location if required, and then remove the log archive. Failing to do this before the log file fills again will result in loss of log data.
ACFSK-00070: %2 saw exception %3 .: Cause: An unexpected exception was detected.; Action: Inform Oracle Support Services and provide the message displayed.
ACFSK-00071: Volume encryption keys are not available for the file system mounted at %2, encrypted files will not be available.: Cause: Volume encryption keys (VEKs) were not available to the file system. Possible causes are: 1) The ACFS Encryption key store was missing. This is indicated by message ACFS-10573 during mount. 2) The ACFS Encryption key store was corrupted. 3) ACFS Encryption was configured to use a password-protected key store and an incorrect key store password was supplied when mounting the file system. 4) ACFS Encryption was configured to use a password-protected key store and the file system was mounted via the ACFS Mount Registry.; Action: Immediately unmount and remount the file system without using the ACFS Mount Registry, providing the correct password if required. If the problem persists, contact Oracle Support Services.
ACFSK-00072: A call to fcntl(2) F_SETFL has cleared O_DIRECT while I/O was active for the file with file identifier %2 in the volume %3. This is not allowed.: Cause: User-space code called fcntl and cleared the O_DIRECT open flag of a file being used for Direct I/O.; Action: Ensure that user-space code does not reset O_DIRECT when calling fcntl F_SETFL.
ACFSK-00073: ACFS _FCB hash size is %2.: Cause: Informational; Action: None
ACFSK-00074: ASSERTION FAILURE: %2 File: %3 Line: %4.: Cause: An internal ACFS assertion has failed.; Action: Contact Oracle Support.
ACFSK-00075: Oracle kernel distributed lock manager hash size is %2.: Cause: Informational.; Action: None
ACFSK-00076: Buffer cache size: %2MB in %3 buckets.: Cause: Informational.; Action: None
ACFSK-00077: WARNING: the OKS and ACFS drivers have different build information.: Cause: Warning - The ACFS label version should match the OKS label version.; Action: None
ACFSK-00078: ACFS build %2.: Cause: Informational.; Action: None
ACFSK-00079: ACFS contains fixes '%2'.: Cause: Informational.; Action: None
ACFSK-00080: OKS build %2.: Cause: Informational.; Action: None
ACFSK-00081: OKS contains fixes '%2'.: Cause: Informational.; Action: None
ACFSK-00082: The storage consumption statistics for snapshots of volume mounted at %2 is no longer accurate.: Cause: Informational.; Action: Running fsck/acfschkdsk will fix the snapshot statistics. These statistics are for reporting purposes only.
ACFSK-00083: Logging to the audit trail %2 has stopped. Backup the audit trail archive %3%4 to a new location if required, and then remove the audit trail archive to restart logging.: Cause: Audit trail size limit reached while the audit trail archive still exists.; Action: Backup the audit trail archive to a new location if required, and then remove the audit trail archive.
ACFSK-00084: Audit trail %2 has been archived at location %3%4.: Cause: The audit trail was archived since the file reached its specified size limit. Meanwhile, logging to the original audit trail will continue.; Action: Backup the audit trail archive to a new location if required, and then remove the audit trail archive using 'acfsutil audit purge' command. Failing to do this before the audit trail fills again will result in loss of log data.
ACFSK-00085: An archive of the audit trail %2 exists at location %3%4.: Cause: Active audit trail is reaching its specified size limit and the audit trail archive has not been removed. Auditing will stop after active audit trail reaches its specified size limit and the audit trail archive still has not been removed.; Action: Backup the audit trail archive to a new location if required, and then remove the audit trail archive. Failing to do this before the audit trail fills again will result in loss of audit trail data.
ACFSK-00086: Metadata validation error encountered on volume mounted at %2. A read retry on mirror %3 succeeded for file identifier %4 starting disk offset %5.: Cause: ACFS detected a problem with the content of metadata read from the disk, but retrying using the mirror cited in the message provided; Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00087: Metadata validation error encountered on volume %2. A read retry on mirror %3 succeeded for file identifier %4 starting disk offset %5.: Cause: ACFS detected a problem with the content of metadata read from the disk, but retrying using the mirror cited in the message provided; Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00088: Metadata validation error encountered on volume with device minor number %2. A read retry on mirror %3 succeeded for file identifier %3 starting disk offset %4.: Cause: ACFS detected a problem with the content of metadata read from the disk, but retrying using the mirror cited in the message provided; Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00089: failed to free storage from a deleted large file on the volume mounted at string; will continue to attempt to free the storage: Cause: ACFS failed to free the space from a deleted large file because the filesystem had no free storage.; Action: Remove smaller files, a directory, or a snapshot to free some blocks, or run 'fsck -a' to return the space from the large file.
ACFSK-00090: failed to free storage from a deleted large file on volume string; will continue to attempt to free the storage: Cause: ACFS failed to free the space from a deleted large file because the filesystem had no free storage.; Action: Remove smaller files, a directory, or a snapshot to free some blocks, or run 'fsck -a' to return the space from the large file.
ACFSK-00091: failed to free storage from a deleted large file on the volume with device minor number string; will continue to attempt to free the storage: Cause: ACFS failed to free the space from a deleted large file because the filesystem had no free storage.; Action: Remove smaller files, a directory, or a snapshot to free some blocks, or run 'fsck -a' to return the space from the large file.
ACFSK-00092: a compressed database file of Oracle file type %2 has blocksize %3 but was opened specifying %4: Cause: An existing compressed Database file was opened specifying a DB Blocksize different from what was expected. Data access will be prevented until this condition is fixed.; Action: Verify that the DB blocksize configured is correct and change it if necessary.
ACFSK-00093: The storage consumption statistics for snapshot %2 (ID %3) of volume mounted at %4 are no longer accurate.: Cause: The mechanism used to report the storage statistics was interrupted.; Action: No action is necessary because these statistics are reporting purpose only. If accuracy is desired run fsck/acfschkdsk to fix the snapshot statistics.
ACFSK-00094: The amount of disk storage from compressed files that should be freed has reached the maximum allowed for the volume mounted at path %2. Expect a temporary slow down in writing new data.: Cause: ACFS needs to catch up on freeing storage no longer needed for compressed files.; Action: No action required. Writes will be unthrottled once ACFS has caught up on freeing storage.
ACFSK-00095: Direct IO(s) to a compressed file were converted to Cached IO due to bad alignment or length. The file has ACFS identifier %2 and is on the file system mounted at path %3 (device %4). Call %5 File Type %6 Data1 %7 Data2 %8: Cause: An application attempted to issue a Direct IO to a compressed file that did not meet the expected alignment and length requirements.; Action: No action required but please note that this can result in poor performance.
ACFSK-00096: Unaligned direct IO writes to compressed database rejected. The file has ACFS identifier %2 and is on the file system mounted at path %3 (device %4). Call %5 File Type %6: Cause: Attempted direct IO writes to a compressed database datafile were rejected because they were not aligned with the Compression Unit size of the file and would have caused corruption.; Action: If the configured database block size is not equal to the Compression Unit size then recreate the file with a block size supported by ACFS. If the database block size is equal to the Compression Unit size, contact Oracle Support Services.
ACFSK-00097: Unsupported block size (2K bytes) for database file. The file has ACFS identifier %2 and is on the file system mounted at path %3 (device %4).: Cause: An attempt to open a database file that was configured with a 2K byte block size was rejected because ACFS does not support a block size of 2K.; Action: If attempting to create a new database file, use a block size supported by ACFS. If attempting to use an existing file, recreate it in the database with a block size supported by ACFS.
ACFSK-00098: Unsupported block size (4K bytes) for compressed database file. The file has ACFS identifier %2 and is on the file system mounted at path %3 (device %4).: Cause: An attempt to open a compressed database file that was configured with a 4K byte block size was rejected because ACFS does not support a block size of 4K for compressed database files.; Action: If attempting to create a new compressed database file, use a block size supported by ACFS. If attempting to use an existing file, recreate it in the database with a block size supported by ACFS.
ACFSK-00099: Access to an ACFS-compressed database file is not allowed. The file has ACFS identifier %2 and is on the file system mounted at path %3 (device %4).: Cause: An attempt to start the database using an ACFS-compressed database file was rejected because ACFS did not support compressed database files.; Action: Ensure that the database file is not ACFS-compressed before using it.