19.0 FILESYS - File System Messages

The following includes messages from the FILESYS.NLM.

FILESYS-X-5: Enable TTS requested by user name on station number.

Source: FILESYS.NLM
Explanation: The user indicated in the message issued an ENABLE Transaction Tracking System™ (TTS™) request.

FILESYS-X-14: Allow unowned files to be extended.

Source: FILESYS.NLM
Possible Cause: The server does not have enough memory to mount the volume.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-129: AUDIT event number = number. Invalid volume number = number.

Source: FILESYS.NLM
Explanation: An invalid volume number was used during a call to audit the event indicated in the message.
Possible Cause: An internal program error occurred.
Action: Reboot the server. If the problem persists, contact a Novell® support provider.

FILESYS-X-131: Memory for auditing cannot be allocated. Volume name is being dismounted.

Source: FILESYS.NLM
Possible Cause: The operating system ran out of memory when it tried to start up auditing while mounting a volume.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-132: Error writing to the audit file for volume: name.

Source: FILESYS.NLM
Explanation: The operating system encountered an error when trying to write to the audit file.
Possible Cause: The file system might be failing.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-133: The audit file for volume name is full.

Source: FILESYS.NLM
Possible Cause: The operating system filled up the audit file when it wrote an audit record.
Action: Use AUDITCON to reset the audit file, or increase the maximum size of the audit file.

FILESYS-X-137: Unable to open file NET$ACCT.DAT to add audit record.

Source: FILESYS.NLM
Explanation: A disk I/O has failed.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-151: The AUDIT configuration file cannot be opened. Press enter to continue.

Source: FILESYS.NLM
Explanation: The operating system failed when trying to open the AUDIT configuration file.
Action: Restart the server. If the problem persists, contact a Novell support provider.

FILESYS-X-158: Internal compression error: file `name’ volume number intermediate size number. Offset totals from intermediate file generation (number) and intermediate file processing (number) mismatch invalidating intermediate file.

Source: FILESYS.NLM
Possible Cause: This error resulted from an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The totals from processing the original file do not match the totals from processing the intermediate file. This would only be caused by insufficient memory or by a disk returning corrupted data. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.
Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.

FILESYS-X-159: Internal compression error: file `name’ volume number intermediate size number. Data encode counts from intermediate file generation (encode_count) and intermediate file processing (encode_count) mismatch invalidating intermediate file.

Source: FILESYS.NLM
Explanation: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.
Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.

FILESYS-X-160: Internal compression error: file name volume number intermediate size number. Length/Offset encode counts from intermediate file generation (number) and intermediate file processing (number) mismatch invalidating intermediate file.

Source: FILESYS.NLM
Possible Cause: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The codes in the intermediate file do not match those found in the file being compressed. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.
Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.

FILESYS-X-161: Internal compression error: file name volume number intermediate size number. Large length/offset encode counts from intermediate file generation (number) and intermediate file processing (number) mismatch invalidating intermediate file.

Source: FILESYS.NLM
Possible Cause: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The codes in the intermediate file do not match those found in the file being compressed. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.
Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.

FILESYS-X-164: Internal compression error: file name volume number size size. Shannon Tree depth exceeded 32 generating bit codes uncontainable in a single LONG.

Source: FILESYS.NLM
Possible Cause: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The totals from processing the original file do not match the totals from processing the intermediate file. This would only be caused by a memory hit or a disk returning faulty data. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.
Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.

FILESYS-X-165: Internal compression error: file name volume number size size. The projected size of the compressed file (byte_size) did not match the byte size of the compressed file (byte_size).

Source: FILESYS.NLM
Possible Cause: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The totals from processing the original file do not match the totals from processing the intermediate file. This would only be caused by a memory hit or a disk returning faulty data. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.
Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.

FILESYS-X-168: Compression: Invalid length or offset.

Source: FILESYS.NLM
Possible Cause: An I/O error has occurred during file compression. The disk drive or disk hardware might be starting to malfunction. The file that was being compressed will remain uncompressed and the system will try again later to compress it.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-170: Error writing to the extended directory space.

Source: FILESYS.NLM
Explanation: The operating system was trying to write extended directory information to disk. When it tried to write the information, it got a disk error. The information was not written to the disk and will be lost. The information which was lost might have been extended attribute data.
Possible Cause: This error might have been caused by a hard disk or channel failure. The disk might have other data integrity problems.
Action: Use the warning message that preceded this message to determine the actual cause and solution of the problem. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-171: Error writing to file (filename not accessible) data stream number. Write was requested by the SERVER.

Source: FILESYS.NLM
Explanation: A write error has prevented the operating system from correctly writing file data to the disk. Hot Fix was not able to redirect the data to a new block. The data stream number indicates the name space stream (0=DOS or Macintosh* data fork, 1=Macintosh resource fork). The data was not written to disk and will be lost.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-172: Error writing to file (filename not accessible) data stream number. Write was requested by user name on station number.

Source: FILESYS.NLM
Explanation: A write error has prevented the operating system from correctly writing file data to the disk. Hot Fix was not able to redirect the data to a new block. The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork). The data was not written to disk and will be lost.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-173: Error writing to file name data stream number. Write was requested by the SERVER. File path path.

Source: FILESYS.NLM
Explanation: A write error occurred on the system while writing data to disk. Hot Fix was not able to redirect the data to a new block. The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork).
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-174: Error writing to file name data stream number. Write was requested by user name on station number. File path server/volume.

Source: FILESYS.NLM
Explanation: A write error occurred on the system, while writing file data to disk. Hot Fix was not able to redirect the data to another block on the disk. The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork). The data was not written to disk and will be lost.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Possible Cause: The designated file was lost or corrupted.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-175: File read error at offset offset data stream number. Error getting filename. Read was requested by the SERVER.

Source: FILESYS.NLM
Explanation: The server was processing a file-read request. When the server tried to read the disk block with the file data, a disk-read error occurred. Some data was lost that could cause the user’s applications to fail on reading data from files.

The operating system was unable to determine the name of the file where the read error occurred because it received additional errors when it tried to read directory blocks to generate the filename.

The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork.)

Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-176: File read error at offset offset data stream number. Error getting filename. Read was requested by user name on station number.

Source: FILESYS.NLM
Explanation: The system cannot read the file from disk. Some data was lost that could cause the user’s applications to fail on reading data from files.

The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork.)

Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-177: Error reading file name. Offset offset data stream number. Read was requested by the SERVER. File path path.

Source: FILESYS.NLM
Explanation: The operating system was processing a request to read data from a file, and it encountered an error while reading the data. The file read request will fail, possibly causing the applications that were requesting the read to fail.

The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork).

Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-178: Error reading file name. Offset offset data stream number. Read was requested by user name on station number. File path path.

Source: FILESYS.NLM
Explanation: When the operating system tried to read existing data from disk, it got a disk read error. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-179: File write pre-read error. Offset offset data stream number. Error getting filename. Read was requested by the SERVER.

Source: FILESYS.NLM
Explanation: When the operating system tried to write data to an existing file, it got an error in trying to read existing data from the disk. The new data could not be written to the disk and will be lost. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.

This error might have been caused by a hard disk or channel failure. The disk might have other data integrity problems.

Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-180: File write preread error. Offset offset data stream number. Error getting filename. Read was requested by user name on station number.

Source: FILESYS.NLM
Explanation: When the operating system tried to write data to an existing file, it got an error in trying to read existing data from the disk. The new data could not be written to the disk and will be lost. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.

This error might have been caused by a hard disk or channel failure. The disk might have other data integrity problems.

Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-181: File name write preread error. Offset offset data stream number. Read was requested by the SERVER. File path path.

Source: FILESYS.NLM
Explanation: When the operating system tried to write data to an existing file, it got an error in trying to read existing data from the disk. The new data could not be written to the disk and will be lost. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-182: File name write pre-read error. Offset offset data stream number. Read was requested by user name on station number. File path path.

Source: FILESYS.NLM
Explanation: When the operating system tried to write data to an existing file, it got an error in trying to read existing data from the disk. The new data could not be written to the disk and will be lost. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-184: Error expanding server\volume directory due to disk write errors.

Source: FILESYS.NLM
Explanation: The system encountered a disk error while it was trying to allocate a block on the disk. The station making the request will not be able to create the new file or directory.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-185: Error expanding server\volume directory because directory size limit was exceeded.

Source: FILESYS.NLM
Explanation: The system needs to allocate another directory block on the volume, but the maximum number of directory blocks has been reached. The server limits the amount of disk space used for the directory table to between 5% and 50% of the total space on a volume. This is controlled by the server parameter, Maximum Percent Of Volume Used By Directory, and it defaults to 13% of the disk space. The system allocates new directory blocks when a new directory is created, or when a new file is added to an existing directory, and it did not have any entries left to track the new file.
Action: See Resolving Server Disk Space Problems and Managing the NetWare Server in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-186: Error expanding server\volume directory because no more disk space is available.

Source: FILESYS.NLM
Possible Cause: The system needs to allocate another directory block on the volume, but the volume is out of disk space. The system tries to allocate new directory blocks when a new directory is created or when a new file is added to an existing directory, but in this instance it did not have any entries left to track the new file.
Action: See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-187: Error expanding server\volume directory because no more memory is available for tables.

Source: FILESYS.NLM
Possible Cause: The system needs to allocate another directory block on the volume, and it needs to expand the tables that it uses to track the directory within memory. When the system tried to expand the memory directory tables, there was not enough memory available to allocate the additional directory block. The station making the request will not be able to create the new file or directory.
Action: Increase the memory available to the server. See Resolving Server Memory Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-188: Server\volume directory size is getting too large for available memory. If the directory grows much larger, you may need to add more memory to the file server.

Source: FILESYS.NLM
Possible Cause: The size of the volume directory table has increased since the volume was mounted. The next time this volume is mounted, more memory will be used for the directory tables because a larger hash table will be created. The system has determined that the amount of memory available in the server is very low, and there might not be enough memory available to mount this volume again.
Action: See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-189: Error writing FAT table for volume server\volume.

Source: FILESYS.NLM
Explanation: A write error has prevented the operating system from recording changes made to the File Allocation Table (FAT). The FAT tracks what disk blocks are allocated and free; it also records what disk blocks are grouped together to store a file’s data. The server will still have the correct FAT information in memory, and it still can access the volume correctly. However, when you try to mount this volume the next time, the FAT information on disk will be incorrect, and the volume probably will not mount.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-190: Error writing to the directory on server\volume.

Source: FILESYS.NLM
Explanation: A write error prevented the server from writing updated directory table information to a directory block. The updated directory information was not recorded on the disk. When the directory block is flushed from the directory cache, the server will not be able to read the information from the disk.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-191: Error reading one copy of the directory on server\volume.

Source: FILESYS.NLM
Explanation: The server maintains two copies of the directory on each volume. An error occurred while the server was reading from one copy of the directory. The server was able to read the other copy, and it found the needed information.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: Run VREPAIR when this error first appears. If both directory copies become corrupted, VREPAIR cannot fix the problem. The possibility of losing data increases significantly when the system uses only one of the mirrored directories.

FILESYS-X-192: Error reading both copies of the directory on server\volume.

Source: FILESYS.NLM
Explanation: The system was trying to read a directory block from disk, but both the primary and secondary copies were inaccessible. Because the system could not read the directory information, it will not be able to process the request that needed this information.

If this error occurs during the mount process, the volume will not mount because the system is not able to properly access and update the volume directory information. The volume tables could become damaged. Data on the volume could be lost, requiring it to be restored from backup copies.

Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

See Resolving Volume Mounting Problems Caused by the Name Space Module in the NW6.5 SP8: Traditional File System Administration Guide.

FILESYS-X-193: Error writing to a newly allocated directory block on server\volume.

Source: FILESYS.NLM
Explanation: A write error prevented the server from allocating a new directory block and writing the directory information to the disk. When this directory block is flushed from the directory cache, the server will not be able to read the data from disk when it is needed again.
Possible Cause: A hard disk or channel failure occurred. The disk could have other data integrity problems.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-194: User name connection number attempted to extend the length of a file with no owner. Filename: name.

Source: FILESYS.NLM
Explanation: A file needed to be extended; however, because the file had no owner, the operation was aborted.
Action: Delete the file, or assign the file an owner.

FILESYS-X-231: Insufficient RAM to compress file.

Source: FILESYS.NLM
Explanation: The compression system could not allocate enough memory to compress the file.
Possible Cause: The server could be congested.
Action: No immediate action is required. The file will remain uncompressed; the system will try to compress it later.
Possible Cause: The server might not have enough memory to compress a file.
Action: If the message occurs even during periods of low network traffic, the server probably needs more memory. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-232: Disk I/O error compressing file.

Source: FILESYS.NLM
Possible Cause: A bad I/O has occurred during file compression. The disk drive or disk hardware might be starting to malfunction. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-234: Insufficient disk space to decompress file filename for station number.

Source: FILESYS.NLM
Explanation: The disk space required for the decompressed file is not available, so the file cannot be decompressed.
Possible Cause: Disk restrictions for the user, volume, or directory could have been assigned, or the volume could be full. The system will try again later to compress the file.
Action: See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-235: Compressed file filename being decompressed for station number uses unknown compression format.

Source: FILESYS.NLM
Possible Cause: Each compressed file has a value indicating which compression format it is in. If NetWare® opens a file and does not recognize the compression format, it cannot decompress the file. This file could be corrupted, or it could be flagged as compressed when it is not really compressed.
Action: Try restoring the file from a backup.

FILESYS-X-238: Insufficient RAM to decompress file.

Source: FILESYS.NLM
Possible Cause: Insufficient memory is available to decompress the file. The file that was being decompressed will remain compressed and the system will try again later to decompress it.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-239: Unknown error (number) returned from decompress for file filename.

Source: FILESYS.NLM
Explanation: This is an internal consistency check done by decompression to guarantee the integrity of the data being decompressed. The file that was being decompressed will remain compressed, and the system will try again later to decompress it.
Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.

FILESYS-X-240: Insufficient RAM to decompress file name.

Source: FILESYS.NLM
Explanation: The system tried to allocate memory to decompress a file and failed. The file that was being decompressed will remain compressed, and the system will try again later to decompress it.
Action: Wait until the server is less congested and try again.

FILESYS-X-241: Compressed file is corrupted and unrecoverable.

Source: FILESYS.NLM
Explanation: The compressed file has been corrupted on the disk. During decompression, the integrity of the data describing the compressed file is checked. If any of the checks fail, data corruption is assumed, and compression cannot be completed, as is the case here.
Possible Cause: This error can only be caused by the data changing on the disk. Changed data can result from one of the following causes:

  • Magnetic or electronic media close to the disk drive

  • Failure of the disk drive or supporting hardware

If the disk drive is failing, other files will be corrupted and will not contain the original data.

Action: Try restoring the file from an earlier backup. If you cannot restore the data from a backup, the file is lost.

FILESYS-X-242: Compressed file name is corrupted and unrecoverable.

Source: FILESYS.NLM
Possible Cause: The compressed file has been corrupted on the disk. During decompression, the integrity of the data describing the compressed file is checked. If any of the checks fail, data corruption is assumed, and compression cannot be completed, as is the case here. This error can only be caused by the data changing on the disk.

Changed data can result from one of the following causes:

  • Magnetic or electronic media close to the disk drive

  • Failure of the disk drive or supporting hardware

If the disk drive is failing, other files will be corrupted and will not contain the original data.

Action: Try restoring the file from an earlier backup. If you cannot restore the data from a backup, the file is lost.

FILESYS-X-243: Compressed file name in use by station number is corrupted and unrecoverable.

Source: FILESYS.NLM
Possible Cause: The first block of the compressed file has been corrupted on the disk. During decompression, the integrity of the data describing the compressed file is checked. If any of the checks fail, data corruption is assumed, and compression cannot be completed, as is the case here. This error can only be caused by the data changing on the disk.

Changed data can result from one of the following causes:

  • Magnetic or electronic media close to the disk drive

  • Failure of the disk drive or supporting hardware

If the disk drive is failing, other files will be corrupted and will not contain the original data.

Action: Try restoring the file from an earlier backup. If you cannot restore the data from a backup, the file is lost.

FILESYS-X-253: Error prevented preservation of file path during file erase.

Source: FILESYS.NLM
Explanation: The operating system was unable to retain the specified deleted file in a salvageable state. The file being deleted was purged, and it cannot be salvaged.
Possible Cause: This message should be preceded by a message stating the actual error condition (such as a disk-write error or out-of-memory error).
Action: Use the message displayed before this one to determine the actual cause of and solution for the problem.

FILESYS-X-254: DeleteFileToLimbo failed, unable to save migrated file (path).

Source: FILESYS.NLM
Possible Cause: An internal program error has occurred.
Action: Retry the operation. If the problem persists, contact a Novell support provider.

FILESYS-X-255: Insufficient directory space (or memory) to preserve path during file erase.

Source: FILESYS.NLM
Explanation: While trying to delete a file, the server was unable to obtain the needed directory table space or memory to retain the deleted file in a state in which it could be salvaged. The file was deleted and purged.
Possible Cause: A preceding message on the screen should indicate the cause of this error.
Action: Use the message displayed before this one to determine the actual cause of and solution for the problem.

FILESYS-X-302: Volume name DOS Type (number) does not match the file server DOS Type (number).

Source: FILESYS.NLM
Explanation: Different language types can be specified for the file system by the LCONFIG.SYS file. The default is English. After upgrading the system, you tried to remount a volume that had a previously specified language type different from the language type the server is now using. If you do not change the language for the volume, this error occurs.
Action: If you are using a language type other than English, make sure that the LCONFIG.SYS and SERVER.MSG are both in the server's boot directory.

If you are trying to change from one of the other languages to English, you might get errors that need to be fixed by running VREPAIR.

FILESYS-X-305: Directory FAT chain has a hole.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations. If the FAT chain skips a block, a hole appears in the chain. (A hole is a section that is not sequential.) A hole indicates that the location was never allocated. This message indicates that while a volume was being initialized, a directory volume structure initialization routine found that the file allocation table was not sequential. The FAT value did not match the directory length. The volume mount was aborted and all resources were returned.
Possible Cause: This error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-306: Error reading in volume directory.

Source: FILESYS.NLM
Explanation: The current directory entry being examined did not have the correct root subdirectory code number.
Possible Cause: This error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-307: Invalid maximum space defined in subdirectory.

Source: FILESYS.NLM
Possible Cause: The operating system encountered a problem while mounting a volume.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-308: Subdirectory entry refers to invalid directory block.

Source: FILESYS.NLM
Explanation: The operating system encountered a problem while mounting a volume. A test of the subdirectory first block entry did not return with the correct value.
Possible Cause: The entry contained a value not equal to zero, indicating the wrong directory block or corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-309: Not enough memory to validate directory.

Source: FILESYS.NLM
Possible Cause: The server had enough memory to read the directory tables, but not enough memory to validate the directories. Before dismounting the volume, the user received a warning that the server was running out of memory and that the volume could not be remounted because it has grown too much. This error could occur at one of the following points in the volume mount:

  • After comparing mirrored directory lengths

  • During setup of extra directory structures

  • During directory space restriction routines

  • During directory trustee addition and maintenance routines

Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-310: Mirror copies of the volume directory don’t match.

Source: FILESYS.NLM
Explanation: The contents of directory 0 were compared with those of directory 1. The compare routine found they did not match.
Possible Cause: This error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-312: Insufficient memory for directory tables.

Source: FILESYS.NLM
Explanation: One of the steps in volume directory initialization is to request resource tags and memory for directory tables, directory hash tables, and extended directory tables.
Possible Cause: The volume did not mount because the server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-313: Invalid deleted file.

Source: FILESYS.NLM
Explanation: While checking deleted file directory entries, the system aborted the volume mount process for one of the following reasons:

  • The FAT chain check did not return with a successful completion code.

  • The directory entry file size did not equal zero.

Possible Cause: This error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-314: Invalid available entry.

Source: FILESYS.NLM
Explanation: While scanning the volume directory for valid subdirectories, the system encountered a subdirectory entry that contained information stating it was a file.
Possible Cause: This error probably indicates corrupted data or a corrupted volume.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-317: Name space support not loaded.

Source: FILESYS.NLM
Explanation: The name space NLM™ program did not load properly.
Possible Cause: The name space module had not been loaded before you tried to mount the volume.
Action: Load a correct working version of the name space module before mounting the volume.
Possible Cause: The module is corrupted or is the wrong type.
Action: Run VREPAIR on the volume.

FILESYS-X-318: Invalid name space list.

Source: FILESYS.NLM
Explanation: While scanning subdirectory name space list entries, the system found that the next name space list entry was greater than or equal to the number of defined name spaces for the volume. Another reason for this error might be the next entry scanned was greater than the maximum directory entries.
Possible Cause: In either case, this error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-319: Invalid name space list order.

Source: FILESYS.NLM
Explanation: While scanning subdirectory name space list entries, the system found that the next name space list entries are not in the correct sequence.
Possible Cause: This error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-320: Invalid subdirectory number in trustee directory entry.

Source: FILESYS.NLM
Explanation: While the system was scanning subdirectory entries, the trustee subdirectory number was greater than or equal to the number of directory entries. The trustee subdirectory number is less than zero.
Possible Cause: This error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-321: Invalid suballocation directory entry.

Source: FILESYS.NLM
Explanation: While scanning directory entries, the system found an invalid suballocation entry.
Possible Cause: This error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-322: Invalid trustee directory entry.

Source: FILESYS.NLM
Explanation: While scanning directories in the current volume for trustees, the system found one of the following problems:

  • The trustee count was greater than the number of trustee entries.

  • The trustee count equaled zero.

Possible Cause: In either case, this error indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-323: Deleted file is a subdirectory.

Source: FILESYS.NLM
Explanation: While in the process of initializing the directory volume structures, the system found that one or both of the members of the work directory (directory flag and directory file attribute) had their subdirectory bit turned on. What was thought to be a file was in fact a subdirectory. The directory volume did not initialize properly and all resources were returned.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-324: Invalid subdirectory number in user restriction directory entry.

Source: FILESYS.NLM
Explanation: While scanning subdirectories on a volume to be mounted, the system found a subdirectory with a restriction subdirectory number not equal to zero. This number should always equal zero because it is predefined.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-325: Invalid user restriction node...too many trustees.

Source: FILESYS.NLM
Explanation: The operating system encountered a problem while mounting a volume.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-326: Insufficient memory available for user restriction nodes.

Source: FILESYS.NLM
Explanation: A call for memory from within the set_user_restriction routine failed. This memory would have been used to create user restriction node IDs.
Possible Cause: The server does not have enough memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-327: Invalid directory number code.

Source: FILESYS.NLM
Explanation: The system found that the subdirectory entry it was about to examine did not have the correct directory number (-4) of user restrictions, trustees, and deleted file blocks.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-328: Invalid subdirectory number in file directory entry.

Source: FILESYS.NLM
Explanation: A subdirectory had a number that was greater than or equal to the maximum number of directory entries.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-329: Directory block is inconsistent...has several subdirectory numbers.

Source: FILESYS.NLM
Explanation: Upon initialization, the subdirectory number vector table should contain a value of -1 (which is then changed to a zero). If the value residing in the table is not equal to -1 or 0, the volume mount is aborted and all resources are returned to the system. In this case, the table contained a different value.
Possible Cause: The volume's directory tables have been corrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-332: Directory tree is circularly linked.

Source: FILESYS.NLM
Explanation: A directory contains a subdirectory that is also its parent.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-333: Directory tree is too deep.

Source: FILESYS.NLM
Explanation: The maximum subdirectory tree depth of 25 levels has been exceeded.
Action: Change the server parameter, Maximum Subdirectory Tree Depth to be able to go beyond the default limit of 25. This parameter can be set to a maximum of 100 levels.

FILESYS-X-335: Length differences on mirror directory chains could not be resolved.

Source: FILESYS.NLM
Explanation: The operating system encountered a problem while mounting a volume.
Possible Cause: The amount of directory blocks of directory 0 didn’t match the number of directory 1. The volume mount was aborted because the directory integrity was disrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-336: File without trustee definitions had a trustee node.

Source: FILESYS.NLM
Severity: This is a warning error, but in most cases it will not cause serious problems.
Explanation: The information about a given file indicated that the file had specific trustee assignments, but no trustee assignments could be found.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-337: Invalid deleted file block.

Source: FILESYS.NLM
Possible Cause: While scanning subdirectory entries, the system found that the value of the deleted sequence number of the current block did not equal zero, indicating a corrupted file system.
Action: Run VREPAIR and restart the system.

FILESYS-X-338: Invalid deleted file trustee node.

Source: FILESYS.NLM
Explanation: A directory entry indicates that trustee assignments exist for the directory, but none can be found.
Possible Cause: The file system is corrupted.
Action: Recreate the directory or run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-342: Invalid extended directory entry FAT chain.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations.
Possible Cause: This error might indicate file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-343: Invalid extended attribute in directory entry.

Source: FILESYS.NLM
Explanation: An attempt to identify the extended attributes of a directory has failed.
Action: Check the extended attributes of the directory and reset them if necessary.

FILESYS-X-344: Error allocating a directory entry to add a name space root.

Source: FILESYS.NLM
Explanation: The system tried to add a name space root and failed. The AllocateDirectoryEntry routine found there were no available directory entries in the subdirectory, so the system tried to extend it.
Possible Cause: There were too many directory blocks, or not enough memory was available for the volume's directory tables.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-345: UNIX Hard Link flags set with no UNIX name space.

Source: FILESYS.NLM
Explanation: The user tried to create a hard link before loading the UNIX name space.
Action: Load the UNIX name space before creating a hard link.

FILESYS-X-346: UNIX Hard Link flags don’t match between the name spaces.

Source: FILESYS.NLM
Possible Cause: The name spaces cannot be linked because their flags do not match.
Action: Make sure that the UNIX hard link flags match before trying to link the name spaces.

FILESYS-X-347: The server is not configured to support this volume’s DOS type.

Source: FILESYS.NLM
Possible Cause: The uesr tried to mount a volume whose name space (for example, Macintosh) has not yet been configured on the server.
Action: Try to mount the volume again after configuring the server to support the appropriate name space.

FILESYS-X-348: Error creating suballocation file space.

Source: FILESYS.NLM
Possible Cause: This error might indicate file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-350: File is flagged as both compressible and uncompressible.

Source: FILESYS.NLM
Possible Cause: The system does not know whether to perform file compression on a given file because the file has been assigned both the Immediate Compress (Ic) and Don’t Compress (Dc) attribute.
Action: Use FLAG to remove the Immediate Compress or the Don’t Compress file attribute on the given file.

FILESYS-X-351: Error moving trustee node on NetWare 4 file upgrade.

Source: FILESYS.NLM
Possible Cause: An error in rebuilding the directory entry table while upgrading to NetWare 4 or a later version occurred. This might be due to not enough disk space or other disk problems.
Action: You might need to increase the volume size or repair the volume using VREPAIR. See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-352: File marked as migrated, but volume trustees not converted.

Source: FILESYS.NLM
Possible Cause: This is a report of a seeming inconsistency after a volume upgrade. When migrating data files, the trustee assignments associated with that file have not been moved but the file is marked as fully migrated.
Action: Perform the migration again or update the trustee assignments manually.

FILESYS-X-410: A subdirectory is named PIPE.

Source: FILESYS.NLM
Explanation: PIPE is a reserved DOS name. No subdirectories can have this name or the volume will not mount. In most instances, NetWare will not allow this name to be used.
Action: Rename the subdirectory or contact a Novell support provider for suggestions on resolving this problem.

FILESYS-X-411: Subdirectory entry refers to invalid directory block.

Source: FILESYS.NLM
Explanation: The operating system encountered a problem while mounting a volume.
Possible Cause: A test of the subdirectory first block entry did not return with the correct value.
Possible Cause: The entry contained a value not equal to zero, indicating the wrong directory block or corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-412: Two subdirectories reference the same first directory block.

Source: FILESYS.NLM
Explanation: The operating system encountered a problem while mounting a volume.
Possible Cause: Two subdirectories reference the same directory block.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-413: Not enough memory to validate directory.

Source: FILESYS.NLM
Explanation: The server had enough memory to read the directory tables, but it did not have enough memory to validate the directories. Before the volume was dismounted, you received a warning that the you were running out of memory and that you could not remount the volume because it had grown too much. This error could occur at one of the following points in the volume mount:

  • After comparing mirrored directory lengths

  • During setup of extra directory structures

  • During directory space restriction routines

  • While adding directory trustees

  • During maintenance routines

Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-414: Invalid maximum space defined in subdirectory.

Source: FILESYS.NLM
Explanation: The operating system encountered a problem while mounting a volume.
Possible Cause: This error probably indicates corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-417: File has both do compression and don’t compress attributes set.

Source: FILESYS.NLM
Possible Cause: The system does not know whether to perform file compression on a given file because the file has been assigned both the Immediate Compress (Ic) and Don’t Compress (Dc) attribute.
Action: Use FLAG to remove the Ic or Dc attribute on the given file.

FILESYS-X-418: Directory has both do file compression and don’t file compress attributes set.

Source: FILESYS.NLM
Possible Cause: The system does not know whether to perform file compression in a directory because the directory has been assigned the Immediate Compress (Ic) and Don't Compress (Dc) attribute.
Action: Remove the Ic or the Dc directory attribute.

FILESYS-X-420: File is flagged as both compressible and noncompressible.

Source: FILESYS.NLM
Possible Cause: The system does not know whether to perform file compression on a given file because the file has been assigned both the Immediate Compress (Ic) and Don't Compress (Dc) attribute.
Action: Remove the Ic or the Dc file attribute on the given file.

FILESYS-X-446: Account number deleted by user number on station number. 1 active connection terminated.

Source: FILESYS.NLM
Explanation: Someone, probably the network supervisor, has terminated the connection.
Action: If desired, reestablish the connection.

FILESYS-X-470: GetOriginalNameSpace could not find the originating name space. The DOS name space was assumed. You should run VREPAIR to fix this!

Source: FILESYS.NLM
Possible Cause: This error indicates an inconsistent state of the directory table. The server needed to determine which name space generated the current name of a file. When it searched for which name space assigned the filename, none of the name spaces was marked as the originating name space. NetWare assumes that the name was generated by the DOS name space.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-472: Volume already supports this Name Space.

Source: FILESYS.NLM
Explanation: This status messate indicateds that the specified name space has already been added to the volume. A volume can be configured only once for a specific type of name space.

FILESYS-X-475: Add name space aborted by the user.

Source: FILESYS.NLM
Explanation: This status message indicates that after beginning installation of a name space, the user opted to discontinue the operation.

FILESYS-X-477: Error reading directory on NameSpace upgrade...volume is left in a bad state.

Source: FILESYS.NLM
Explanation: This error occurred when an ADD NAME SPACE command was issued.
Possible Cause: The error could indicate file system corruption.
Action: Run VREPAIR with the Remove Name Space Support from the Volume option.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-481: Add name space aborted by the user due to insufficient disk space.

Source: FILESYS.NLM
Possible Cause: There is insufficient disk space to add the desired name space.
Action: Increase the available disk space on the volume. See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-482: Add name space aborted due to insufficient server RAM.

Source: FILESYS.NLM
Explanation: There is insufficient memory to add the desired name space.
Possible Cause: The server might not have enough available memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-483: Error allocating new entry on NameSpace upgrade...volume is left in a bad state.

Source: FILESYS.NLM
Explanation: An error occurred when an ADD NAME SPACE command was issued.
Possible Cause: The error could indicate file system corruption.
Action: Run VREPAIR with the Remove Name Space Support from the Volume option.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-484: Error setting entry name on NameSpace upgrade...volume is left in a bad state.

Source: FILESYS.NLM
Explanation: An attempt to set a name space name has failed. The name space will not be effective, and problems with other name spaces might occur.
Possible Cause: There might not be enough disk space or system memory to handle the name space.
Action: Verify that the system is large enough to handle the name space. Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.
Action: Increase the available disk space on the volume. See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Then re-create the volume.

FILESYS-X-485: AddNameSpace error reading volume header...volume is left in a bad state.

Source: FILESYS.NLM
Explanation: An error occurred when an ADD NAME SPACE command was issued.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-491: Connection number user name exceeded outstanding NCP directory search limit.

Source: FILESYS.NLM
Possible Cause: The structure that DOS uses to track the current status of a directory search does not have enough fields to track the file that should be found next on a NetWare volume. Because of this, NetWare must keep a separate search structure in server memory that tracks the status of the search and the next file to be found. DOS does not tell NetWare when it has finished a search, so NetWare must guess when it can discard the search information that it is keeping. The number of searches that NetWare will track is controlled by the server parameter, Maximum Outstanding NCP Searches, which is set to a default value of 51 per connection. This message indicates that a program tried to continue a search that NetWare is no longer tracking. Because of this, NetWare cannot return the next filename that should be found.
Action: You can increase the number of searches that the server tracks by changing the server parameter, Maximum Outstanding NCP Searches. However, doing so will use a lot more memory to track searches. (Searches must be tracked separately for each connection.) It also might degrade performance if it causes the number of cache buffers available to be too small.

If performance is degraded, add additional memory to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. A second solution is to determine which program tried to continue a search that the server was not tracking. The search method that the program uses can be modified so that it does not require more than 51 searches to be tracked. Or, if available, an alternate program could be used.

FILESYS-X-492: You exceeded your outstanding NCP directory search limit.

Source: FILESYS.NLM
Explanation: You cannot search directories beyond a certain depth.
Action: If this error appears often, increase the search limit.

FILESYS-X-495: Insufficient memory available to mount volume. Volume name was NOT mounted.

Source: FILESYS.NLM
Possible Cause: The server does not have enough memory to mount the volume.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-496: The FAT chain used to define the FAT is invalid. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-497: The FAT chain used to define the FAT overlaps on itself. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-498: Error reading in the FAT. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-499: The mirror copies of the FAT don’t match. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-500: The FAT chain used to define the FAT has an invalid forward reference. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-501: A file’s FAT chain contains entries out of order. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations. The data of the file might not be damaged, but the file is invalid due to the sequence of the data.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-502: A file’s FAT chain collides with another FAT chain.

Source: FILESYS.NLM
Explanation: The File Allocation Table (FAT) chain is a list of directory block locations. Both files involved are invalid; updates to either file could cause damage to both of them.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-503: The first entry of a file’s FAT chain is invalid. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-504: A FAT chain has an invalid next link. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations. This message indicates that the next link in a FAT chain is invalid.
Possible Cause: This error probably indicates file system corruption. .
Action: If this problem occurs during a volume mount, the operating system will try to load VREPAIR to correct the problem. Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-505: A file with a nonzero length doesn’t have a FAT chain. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations.
Possible Cause: This error indicates an invalid file, probably due to corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-507: Invalid directory FAT chain. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations. There are duplicate extended directory chains (chain0 and chain1). If these chains do not match for some reason, this error is produced and the volume will not mount.
Possible Cause: This error probably indicates file system corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-508: Invalid suballocation node. Volume was NOT mounted.

Source: FILESYS.NLM
Possible Cause: Corruption has occurred in the file system, possibly due to a power outage.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

Action: Also, make sure the server has a good UPS system installed and that the UPS system is operating properly.

FILESYS-X-509: Suballocation node used by multiple files. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: More than one file was using the same block.
Possible Cause: This error could be due to a variety of causes, including a faulty disk drive or other hardware problem, premature downing of the server, or data corruption.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If you suspect corruption, run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-510: Suballocation encountered but not enabled on this volume. Volume name was NOT mounted.

Source: FILESYS.NLM
Possible Cause: This error could be due to a variety of causes, including a faulty disk drive or other hardware problem, premature downing of the server, or data corruption.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If you suspect corruption, run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-511: Suballocation node used on TTS enabled file. Volume name was NOT mounted.

Source: FILESYS.NLM
Explanation: The ending node of the TTS file was a suballocation node.
Possible Cause: This error probably indicates file system corruption.
Action: Try running VREPAIR.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

If the problem persists, contact a Novell support provider.

FILESYS-X-518: System file lock threshold exceeded. Number file open or lock requests failed.

Source: FILESYS.NLM
Explanation: The number indicates the requests that failed to open or lock a file because the limit was exceeded. The file open or lock requests are not being serviced.
Possible Cause: The number of open files and file locks on the server exceeded the maximum specified by the server parameter, Maximum File Locks: number. The default is 10,000.
Action: Increase the number of file locks using the SET MAXIMUM FILE LOCKS command. For more information, see SET in NW 6.5 SP8: Utilities Reference.

FILESYS-X-519: Station number file lock threshold exceeded. Total violations number.

Source: FILESYS.NLM
Explanation: The number of open files and file locks on the server for the specified station exceeded the limit specified. The total violations number indicates the total number of requests to lock a record that failed.
Action: Use the SET console command to increase the number of file locks per connection: 

SET MAXIMUM FILE LOCKS PER CONNECTION= number 



Minimum = 10 



Maximum = 1000 



Default = 250

Increasing the number of file locks will increase the amount of memory used by the server. You might need to increase the available memory on the workstation. Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-520: System record lock threshold exceeded. Number record lock requests failed.

Source: FILESYS.NLM
Explanation: The number of record locks on the server exceeded the maximum specified. Applications that lock records will not function properly. The number in the message indicates the total number of record lock requests for the station that failed because the limit was exceeded.
Action: Increase the number of system record locks using the SET console command. For the syntax and value required, see the parameters for the see SET comand SET MAXIMUM RECORDS LOCKS.

Increasing the number of record locks will increase the amount of memory required by the server. You might need to increase the available memory on the server. Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-521: Station number record lock threshold exceeded. Total violations number.

Source: FILESYS.NLM
Explanation: The number of record locks on the server for the specified station exceeded the limit specified. Applications that request record locks do not function properly until record locks are released by other applications. The total violations number indicates the number of requests that failed to lock a record because the record lock threshold limit was exceeded.
Action: Increase the number of record locks using the SET console command. For the syntax and value required, see the parameters for the SET comand SET MAXIMUM RECORD LOCKS PER CONNECTION.

Increasing the number of record locks will increase the amount of memory required by the server. Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-524: RT Data Migrator Default Read Write Support Module has been changed.

Source: FILESYS.NLM
Explanation: This status message indicates that the default support module has been changed to a new support module.

FILESYS-X-525: Volume name mounted with no Migration NLM loaded, some files may be inaccessible.

Source: FILESYS.NLM
Possible Cause: The volume was mounted with files that cannot be accessed until the RTDM.NLM is loaded.
Action: Load RTDM.NLM and the appropriate support module.

FILESYS-X-526: Volume name mounted without a specified Migration Support NLM. Some files maybe inaccessible.

Source: FILESYS.NLM
Explanation: A volume has been mounted with files that cannot be accessed until the support module needed to access the files has been loaded.
Action: Load the appropriate support NLM program.

FILESYS-X-527: Migrated Data Streams have been corrupted.

Source: FILESYS.NLM
Possible Cause: The data for a migrated file is corrupted.
Action: Replace the corrupted file from a backup.

FILESYS-X-528: Unable to access the Data Migration Look Up Key.

Source: FILESYS.NLM
Explanation: Data that was migrated to a writable disk player (or jukebox) for storage cannot be found. The Data Migration Look Up Key is the pointer that tells where stored data is located in the CD. The directory entry for the file containing the data still exists, but no data exists in the file.
Action: Unless there is a backup of the file, the data is lost. Delete the file from the directory.

FILESYS-X-529: Unable to get DOS entry for Migrated File.

Source: FILESYS.NLM
Explanation: A migrated file's DOS counterpart cannot be found.
Action: Delete the file that was migrated.

FILESYS-X-530: Collision when Claiming Extended Directory space for a migrated file.

Source: FILESYS.NLM
Possible Cause: The volume’s extended directory space has been corrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-557: Illegal hole in suballocation FAT chain.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations. If the FAT chain skips a block, a hole appears in the chain. (A hole is a section that is not sequential.) A hole indicates that the location was never allocated.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-558: Suballocation FAT chain entry exceeds maximum.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) chain is a list of directory block locations.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-559: Suballocation FAT already claimed.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-560: Suballocation out of memory.

Source: FILESYS.NLM
Possible Cause: The operating system was unable to allocate memory for the suballocation FAT because it is out of memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-574: TTS exceeded the limit of number of active transactions. Number transactions delayed.

Source: FILESYS.NLM
Explanation: Because the limit of active transactions was exceeded, the Transaction Tracking System (TTS) must delay additional requests to complete transactions until the number of active transactions comes within the limit.
Action: If the transaction limit has not been set to its maximum, try increasing the value (MONITOR > Server Parameters > Transaction Tracking > Maximum transactions).

FILESYS-X-575: Transaction aborted for station number task number.

Source: FILESYS.NLM
Explanation: Due to a CLEAR STATION command, or some other external connection, the transaction was aborted and backed out.
Action: Review the TTS$ERR.LOG file; then you can see what the user was working on and when it was changed.

FILESYS-X-577: Disable TTS requested by user name on station number.

Source: FILESYS.NLM
Explanation: This informational message indicates that the user issued a DISABLE Transaction Tracking System (TTS) request.

FILESYS-X-578: Server TTS shut down because backout volume name was dismounted.

Source: FILESYS.NLM
Explanation: The informational message is an alert to create a chronological history for troubleshooting. The Transaction Tracking System (TTS) is automatically disabled when the backout volume is dismounted.

FILESYS-X-579: Error writing to TTS$LOG.ERR file.

Source: FILESYS.NLM
Explanation: A Transaction Tracking System (TTS) error could not be logged in the TTS error log file.
Possible Cause: The volume is probably out of space.
Action: Add more disk space to the volume containing the TTS files. See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-580: Error opening or creating TTS$LOG.ERR file.

Source: FILESYS.NLM
Explanation: The Transaction Tracking System (TTS) could not open or create the TTS$LOG.ERR file, which is a file containing a history of what TTS has done.
Possible Cause: The volume might be running out of disk or directory space.
Action: Erase or purge unnecessary files, or add more disk space to the volume containing the TTS files. See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-581: TTS ran out of memory expanding transaction node tables. Number memory allocation requests failed.

Source: FILESYS.NLM
Possible Cause: The server has run out of memory for more transactions.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-582: TTS disabled by operator.

Source: FILESYS.NLM
Explanation: This informational message indicates that the DISABLE TTS command was issued from the server's console.

This message is generated to the screen, and to the TTS$LOG.ERR file, just for a chronological record of when TTS was disabled, and to indicate that it was disabled by the operator rather than by TTS itself (as is the case when the TTS runs out of disk space).

FILESYS-X-583: TTS disabled because of error reading backout file.

Source: FILESYS.NLM
Explanation: The Transaction Tracking System (TTS) could not read the backout file. TTS was disabled because it could not reliably back out any transactions. TTS protection is gone, but completed transactions are intact.
Action: No further action is required. You can continue without TTS protection.

FILESYS-X-584: TTS disabled because of error writing to file during backout.

Source: FILESYS.NLM
Explanation: The Transaction Tracking System (TTS) had a problem writing to the actual database for which it was backing out transactions, so it disabled itself to prevent further problems.
Possible Cause: The database is probably corrupted.
Action: Try to determine whether the database application can read the database. Some database programs have recovery utilities that can detect and repair corruption.

FILESYS-X-585: TTS disabled because of too many defined volumes.

Source: FILESYS.NLM
Possible Cause: The Transaction Tracking System (TTS) can track transactions on only a certain number of volumes. This number has been exceeded.
Action: Combine volumes so that the number is within the limit set by TTS.

FILESYS-X-586: TTS disabled because of error writing volume definition information.

Source: FILESYS.NLM
Possible Cause: A hardware failure could have occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-587: TTS disabled because of error reading backout file during record generation.

Source: FILESYS.NLM
Possible Cause: The Transaction Tracking System (TTS) probably disabled itself because it failed to generate records to be written to a file. This failure occurred when TTS could not read the backout file for some reason. The problem could be a hardware failure, a power failure, or a corrupted file.
Action: If you suspect file corruption, delete the file and restore from a backup.

FILESYS-X-588: TTS disabled because of error growing TTS memory tables.

Source: FILESYS.NLM
Possible Cause: The server does not have enough memory.
Action: See Resolving Server Memory Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-589: TTS disabled because of error allocating more disk space for the backout file.

Source: FILESYS.NLM
Possible Cause: The backout volume is full.
Action: Try adding another drive to the backout volume, deleting or compressing existing files on the backout volume, or moving files from the backout volume to another volume. (Increasing disk space on volumes other than the backout volume will not help.)

FILESYS-X-590: TTS disabled because of directory error on TTS backout file.

Source: FILESYS.NLM
Possible Cause: There is not enough memory space available on the volume for the directory.
Action: Increase the percentage of volume space that can be used by the directory.

FILESYS-X-621: 1 Incomplete Transaction Found. Last record was written at date_and_time.

Source: FILESYS.NLM
Explanation: This informational message indicates that TTS found an incomplete transaction. Begin TTS was called without a subsequent ABORT or END.

FILESYS-X-622: Number Incomplete Transactions Found. Last record was written at date_and_time.

Source: FILESYS.NLM
Explanation: This message indicates that a database has closed improperly. This message lists the number of incomplete transactions and the time the last complete record was written.

FILESYS-X-628: Transactions will be backed out and not displayed or logged.

Source: FILESYS.NLM
Explanation: This informational message indicates that transactions will be backed out, and they will not be displayed or logged.

FILESYS-X-631: Error opening file referenced by the backout file on volume name; file was deleted.

Source: FILESYS.NLM
Explanation: This informationl message indicates that the referenced file has been deleted before the Transaction Tracking System (TTS) could open it to back it out.

FILESYS-X-632: Backout information for transaction number (original write occurred at time).

Source: FILESYS.NLM
Explanation: This informational message is displaying the backout information for the transaction indicated.

FILESYS-X-633: Error opening file for backout. Completion code = code.

Source: FILESYS.NLM
Possible Cause: This is probably a hardware error.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

For information about a specific error code, search the Error Codes online documentation.

FILESYS-X-634: File has been changed (at time) since this backout file ended (at time).

Source: FILESYS.NLM
Explanation: This informational message indicates that the file has changed since it was backed out.

FILESYS-X-637: Error reading original data.

Source: FILESYS.NLM
Possible Cause: This error might indicate hardware failure or a corrupted Transaction Tracking System (TTS) backout file.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If you suspect file corruption, delete the corrupted file and replace it with a backup.

FILESYS-X-638: Record data in the file before the backout.

Source: FILESYS.NLM
Explanation: This is a informational message that states that record data was in the file before it was backed out.

FILESYS-X-642: Error opening file referenced by the backout file on volume name; file was deleted.

Source: FILESYS.NLM
Explanation: This informational message indicates that the referenced file was deleted before the Transaction Tracking System (TTS) could open it to back it out.

FILESYS-X-644: File has been changed (at time) since this backout file ended (at time).

Source: FILESYS.NLM
Explanation: This informational message indicates that the file has changed since it was backed out.

FILESYS-X-645: Hole In File Restored To Offset offset.

Source: FILESYS.NLM
Explanation: This informational message indicates that a hole in the file has been restored to the indicated offset. (A hole is a section that is not sequential.)

FILESYS-X-646: Incomplete transactions referencing unmounted volumes were preserved.

Source: FILESYS.NLM
Explanation: This informational message indicates that not all of the volumes are mounted yet, so the Transaction Tracking System (TTS) backout file is being saved. An incomplete transaction occurred on one of these unmounted volumes.

FILESYS-X-653: Error opening backout file.

Source: FILESYS.NLM
Possible Cause: A hardware failure occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.
Possible Cause: A Transaction Tracking System (TTS) backout file is corrupted.
Action: If you suspect file corruption, make sure a file backup exists.

Warning: If you delete the file, all data will be destroyed. You will have to restore the data from a backup.

Delete the corrupted file and replace it with a backup.

FILESYS-X-656: TTS disabled by operator.

Source: FILESYS.NLM
Explanation: This informational message indicates that the DISABLE TTS command was issued from the server’s console.

This message is generated to the screen, and to the TTS$LOG.ERR file, just for a chronological record of when TTS was disabled, and to indicate that it was disabled by the operator rather than by TTS itself (as is the case when the TTS runs out of disk space).

FILESYS-X-657: TTS disabled because of error reading backout file.

Source: FILESYS.NLM
Explanation: The Transaction Tracking System (TTS) could not read the backout file. TTS was disabled because it could not reliably back out any transactions. TTS protection is gone, but completed transactions are intact.
Action: No further action is required. You can continue without TTS protection.

FILESYS-X-658: TTS disabled because of error writing to file during backout.

Source: FILESYS.NLM
Explanation: The Transaction Tracking System (TTS) had a problem writing to the actual database for which it was backing out transactions, so it disabled itself to prevent further problems.
Possible Cause: The database is probably corrupted.
Action: Try to determine whether the database application can read the database. Some database programs have recovery utilities that can detect and repair corruption.

FILESYS-X-659: TTS disabled because of too many defined volumes.

Source: FILESYS.NLM
Possible Cause: The Transaction Tracking System (TTS) can track transactions on only a certain number of volumes. This number has been exceeded.
Action: Combine volumes so that the number is within the limit set by TTS.

FILESYS-X-660: TTS disabled because of error writing volume definition information.

Source: FILESYS.NLM
Possible Cause: A hardware failure could have occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-661: TTS disabled because of error reading backout file during record generation.

Source: FILESYS.NLM
Possible Cause: The Transaction Tracking System (TTS) probably disabled itself because it failed to generate records to be written to a file. This failure occurred when TTS could not read the backout file for some reason. The problem could be a hardware failure, a power failure, or a corrupted file.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If you suspect file corruption, delete the file and restore from a backup.

FILESYS-X-662: TTS disabled because of error growing TTS memory tables.

Source: FILESYS.NLM
Possible Cause: The server does not have enough memory.
Action: See Resolving Server Memory Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-663: TTS disabled because of error allocating more disk space for the backout file.

Source: FILESYS.NLM
Possible Cause: The backout volume is full.
Action: Try adding another drive to the backout volume, deleting or compressing existing files on the backout volume, or moving files from the backout volume to another volume. (Increasing disk space on volumes other than the backout volume will not help.)

FILESYS-X-664: TTS disabled because of directory error on TTS backout file.

Source: FILESYS.NLM
Possible Cause: There is not enough space available on the volume for the directory.
Action: Increase the percentage of volume space that can be used by the directory.

FILESYS-X-666: TTS cannot allocate sufficient memory.

Source: FILESYS.NLM
Possible Cause: The server does not have enough memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-667: Error renaming old TTS backout file.

Source: FILESYS.NLM
Possible Cause: A hardware error occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-668: Error creating TTS backout file.

Source: FILESYS.NLM
Possible Cause: The volume does not have enough space to create the Transaction Tracking System (TTS) backout file.
Action: Try adding another drive to the backout volume, deleting or compressing existing files on the backout volume, or moving files from the backout volume to another volume. (Increasing disk space on volumes other than the backout volume probably will not help.)

FILESYS-X-669: Error hiding TTS backout file.

Source: FILESYS.NLM
Possible Cause: A hardware error occurred before the volume was mounted.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-670: Error writing volume name information to TTS backout file.

Source: FILESYS.NLM
Possible Cause: A hardware error occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-671: Error writing header information to TTS backout file.

Source: FILESYS.NLM
Possible Cause: A hardware error occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-672: Error manipulating the TTS backout file.

Source: FILESYS.NLM
Possible Cause: A hardware error occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-673: TTS cannot allocate memory to do the transaction backouts.

Source: FILESYS.NLM
Possible Cause: The server does not have enough memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-674: TTS not initialized.

Source: FILESYS.NLM
Explanation: This informational message indicates that Transaction Tracking (TTS) has not initialized.
Action: No action is necessary unless you want to initialize transaction tracking.

FILESYS-X-675: TTS has been shut down.

Source: FILESYS.NLM
Explanation: The informational message indicates that TTS has been shut down.
Action: No action is necessary unless you want to initialize transaction tracking.

FILESYS-X-682: Transaction tracking system enabled.

Source: FILESYS.NLM
Explanation: This informational message indicates that the Transaction Tracking System (TTS) has been enabled.

FILESYS-X-683: Transaction aborted for station number task number.

Source: FILESYS.NLM
Action: See message FILESYS-X-575: Transaction aborted for station number task number.

FILESYS-X-684: Abort transaction attempted on station number and could not occur because transactions were disabled.

Source: FILESYS.NLM
Explanation: A station requested an abort transaction when TTS was not enabled.
Action: Determine why TTS is disabled. A preceding message will indicate whether the operating system disabled TTS on its own. Otherwise, disable TTS could have been entered at the system console.

FILESYS-X-685: Backout information for transaction aborted by station number.

Source: FILESYS.NLM
Explanation: This informational message indicates that the backout information for the transaction was aborted by the station indicated in the message.

FILESYS-X-687: Original record data from the backout file (being written back to the file).

Source: FILESYS.NLM
Explanation: This informational message indicates that the original record data from the backout file is being written back to the file.

FILESYS-X-688: Hole Restored To File At Offset = offset.

Source: FILESYS.NLM
Explanation: This inforamational message indicates that a hole in the file has been restored to the indicated code. (A hole is a section that is not sequential.)

FILESYS-X-694: TTS exceeded the limit of number of active transactions. Number transactions delayed.

Source: FILESYS.NLM
Action: See message FILESYS-X-574: TTS exceeded the limit of number of active transactions. Number transactions delayed.

FILESYS-X-695: TTS ran out of memory expanding transaction node tables. Number memory allocation requests failed.

Source: FILESYS.NLM
Possible Cause: The server has run out of memory for more transactions.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-696: TTS ran out of memory expanding transaction node tables. Number memory allocation requests failed.

Source: FILESYS.NLM
Possible Cause: The server has run out of memory for more transactions.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-737: Unable to create VOL$LOG.ERR on volume.

Source: FILESYS.NLM
Explanation: The system cannot log the error messages it produces to the VOL$LOG.ERR file. Historical error information for this volume will not be recorded at the server.
Possible Cause: The volume was out of room.
Possible Cause: A disk error occurred.
Action: See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-738: Unable to write to VOL$LOG.ERR on volume.

Source: FILESYS.NLM
Explanation: The system was unable to write to the volume’s error file.
Possible Cause: A disk failure occurred.
Action: Another message should appear that indicates what went wrong. Correct the problem according to the information in the message.

FILESYS-X-739: Volume name still operational despite drive deactivation.

Source: FILESYS.NLM
Explanation: One of the disk drives in the volume has gone down. However, the volume’s integrity has not been compromised sufficiently to bring the entire volume down.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-740: Volume name dismounted due to drive deactivation.

Source: FILESYS.NLM
Possible Cause: A disk driver was unloaded.
Possible Cause: The operating system initiated the driver unload.
Action: Make sure the disk driver is loaded.
Possible Cause: A disk failure occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.
Possible Cause: The volume is offline and unavailable to users.
Action: Remount the volume.

FILESYS-X-745: Attempt to allocate memory to read volume definition tables failed.

Source: FILESYS.NLM
Possible Cause: The server does not have enough memory to mount the volume.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-746: Volume name could NOT be mounted. Some or all volume segments cannot be located

Source: FILESYS.NLM
Possible Cause: The volume specified in the MOUNT command could not be mounted. The volume has segments on more than one hard disk, and at least one of the hard disks is not responding.
Action: Make sure all disk drivers have been loaded. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-748: Attempt to allocate memory to hold NetWare partition information failed.

Source: FILESYS.NLM
Possible Cause: The server does not have enough memory to hold partition information.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-759: Unable to read volume definition table from NetWare partition on drive.

Source: FILESYS.NLM
Possible Cause: The volume definition table on the specified drive could not be read because of a disk error. Consequently, the volume could not be mounted.
Action: Check the disk drive and the cable. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-760: Volume definition table mirror mismatch on drive. NetWare partition ignored.

Source: FILESYS.NLM
Explanation: Four copies of the Volume Segment Definition table are kept on each NetWare partition. This error indicates that these copies do not match.
Action: Rename or delete the volume.

FILESYS-X-761: Block allocation size does not match.

Source: FILESYS.NLM
Explanation: Two segments of the volume claim different block allocation sizes.
Possible Cause: Two volumes on the server have identical names, and a segment from each volume is causing the error.
Action: Unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.
Possible Cause: The volume is corrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-762: Number of segments in the volume does not match.

Source: FILESYS.NLM
Explanation: Two segments of the volume claim different numbers of segments.
Possible Cause: Two volumes on the server have identical names and a segment from each volume is causing the error.
Action: Unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.
Possible Cause: The volume is corrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-763: Volume flags do not match.

Source: FILESYS.NLM
Explanation: Two segments of the volume claim that the volume has different flags.
Possible Cause: Two volumes on the server have identical names and a segment from each volume is causing the error.
Action: Unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.
Possible Cause: The volume is corrupted.
Action: If the volume is corrupted, try renaming or deleting the volume.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-764: First block for FAT table 0 does not match.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. Two segments of the volume claim a different File Allocation Table 0's (or 1's) first block.
Possible Cause: Two volumes on the server have identical names and a segment from each volume is causing the error.
Action: Unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.
Possible Cause: The volume is corrupted.
Action: If the volume is corrupted, try renaming or deleting the volume.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-765: First block for FAT table 1 does not match.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. Two segments of the volume claim a different File Allocation Table 0's (or 1's) first block.
Possible Cause: Two volumes on the server have identical names and a segment from each volume is causing the error.
Action: Unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.
Possible Cause: The volume is corrupted.
Action: If the volume is corrupted, try renaming or deleting the volume.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-766: First block for directory table 0 does not match.

Source: FILESYS.NLM
Explanation: Two segments of the volume claim a different directory table zero's first block.
Possible Cause: Two volumes on the server have identical names and a segment from each volume is causing the error.
Action: Unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.
Possible Cause: The volume is corrupted.
Action: If the volume is corrupted, run try renaming or deleting the volume.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-767: First block for directory table 1 does not match.

Source: FILESYS.NLM
Explanation: Two segments of the volume claim a different directory table one’s first block.
Possible Cause: Two volumes on the server have identical names and a segment from each volume is causing the error.
Action: Unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.
Possible Cause: The volume is corrupted.
Action: If the volume is corrupted, try renaming or deleting the volume.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-768: Volume segment entry number on drive is invalid:

Source: FILESYS.NLM
Possible Cause: The Volume Segment table is corrupted.
Possible Cause: The Volume Segment table does not have a volume name.
Possible Cause: The volume name is illegal.
Possible Cause: The block allocation size is illegal.
Possible Cause: One of the other entry fields is illegal.

Another message should follow this message. It will indicate which field is illegal. The segment will not be added to the volume tables. If the segment is needed for mounting the volume, then the volume will not be mounted.

Action: If the volume is corrupted, try renaming or deleting the volume.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-769: Two volume segments with same sync value have mismatched data.

Source: FILESYS.NLM
Explanation: The values specified by two segments on the volume do not match. Another message should follow this message to indicate which values do not match.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-770: Volume has no volume name.

Source: FILESYS.NLM
Possible Cause: The MOUNT or DISMOUNT command was issued, but the volume name was not specified.
Action: Specify a volume name.

FILESYS-X-771: Volume name name is too short.

Source: FILESYS.NLM
Explanation: A volume name must be at least two characters long.
Action: Make sure that you typed a valid volume name in the MOUNT console command and that you spelled it correctly.

FILESYS-X-773: Invalid number of volume segments number.

Source: FILESYS.NLM
Possible Cause: During an attempt to mount a volume, the operating system determined that the volume contained too many segments (there is an eight segment limit).
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-774: Invalid volume segment position of position_number of number segments.

Source: FILESYS.NLM
Possible Cause: The segment position is greater than the number of segments.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-775: Invalid starting sector offset of number on a drive of size number.

Source: FILESYS.NLM
Explanation: The offset of the starting sector of a partition is greater than the size of the partition.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-776: Invalid starting sector offset of number.

Source: FILESYS.NLM
Explanation: The offset of the starting sector is invalid. The sector is probably corrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-777: Invalid segment length of number starting at number on a drive of size number.

Source: FILESYS.NLM
Explanation: A segment of a partition has too many sectors or has sectors that exceed allowable size. The segment is probably corrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-778: Invalid FAT table 0 starting block of number on volume of size number.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. The FAT table on this volume has an invalid table zero starting block. The table is probably corrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-779: Invalid FAT table 1 starting block of number on volume of size number.

Source: FILESYS.NLM
Explanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. The FAT table on this volume has an invalid table one starting block. The table is probably corrupted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-780: Invalid directory table 0 starting block of number on volume of size number.

Source: FILESYS.NLM
Explanation: A segment on the primary volume has an inconsistency in the starting point of the directory table of block pointers.
Possible Cause: The table is probably corrupted.
Action: Run VREPAIR on the primary volume.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-781: Invalid directory table 1 starting block of number on volume of size number.

Source: FILESYS.NLM
Possible Cause: A segment on the mirrored volume has an inconsistency in the starting point of the directory table of block pointers.
Action: Run VREPAIR on the mirrored volume.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-782: Reserved area is not zero filled.

Source: FILESYS.NLM
Possible Cause: While mounting a volume, the operating system found that the reserved area of a segment definition was not zero-filled as it should be. Therefore, the segment was not included in the volume definition table.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-783: Volume name has multiple sync definitions. All definitions except number discarded.

Source: FILESYS.NLM
Explanation: This informational message indicates that while checking a volume definition during mounting of the volume, the operating system discarded all unneeded synchronization values.

FILESYS-X-784: Volume name has multiple definitions for segment number.

Source: FILESYS.NLM
Possible Cause: While mounting a volume, the operating system found multiple definitions for the specified segment, indicating that the current synchronization value is invalid. The operating system will discard the invalid synchronization value.

FILESYS-X-785: Volume name is missing segment number.

Source: FILESYS.NLM
Possible Cause: While checking a volume definition during mounting of the volume, the operating system found that a segment was missing. Segments are consecutively numbered.
Action: If the problem persists, contact a Novell support provider.

FILESYS-X-786: Volume name segment number ends at block number and segment number starts at block number.

Source: FILESYS.NLM
Possible Cause: The volume segments are not contiguous.
Action: Before troubleshooting the problem, back up all data. Make sure that the operating system can recognize all disks over which the volume is distributed and that none have been corrupted. Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-787: Volume name first segment (number) does not start at block 0.

Source: FILESYS.NLM
Explanation: The first segment of a volume must start with block 0. While mounting the specified volume, which is distributed over multiple physical disks, the operating system could not find the first segment. The segment that it found is not the first segment in the volume because it does not begin with block 0.
Possible Cause: The disk was corrupted.
Possible Cause: A hardware problem exists on the network.
Action: Before troubleshooting the problem, back up all data on the affected disk. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-788: Volume name last segment (number) ends at block number instead of number.

Source: FILESYS.NLM
Explanation: This informational message indicates that the segment ends at a block that is incorrect based on the operating system’s calculation of where the segment begins and how large it is.

FILESYS-X-789: Definition for volume name is invalid.

Source: FILESYS.NLM
Explanation: This informational message indicates that while mounting one or more volumes, the operating system found an invalid definition for the specified volume.

FILESYS-X-790: Volume name not found in existing volumes list.

Source: FILESYS.NLM
Explanation: This informational message indicates that the operating system could not find a volume that it tried to discard.

FILESYS-X-791: Definition for sync number of volume name removed.

Source: FILESYS.NLM
Explanation: This informational message indicates that the operating system discarded an unneeded synchronization value while it was schecking a volume definition during mounting of the volume.

FILESYS-X-792: Volume name sync number not found in volume’s sync list.

Source: FILESYS.NLM
Explanation: This informational message indicates that the operating system found that the value was not in the volume’s synchronization list while it was trying to discard an unneeded or invalid synchronization value.

FILESYS-X-796: Volume name could not be mounted. There are already number volumes mounted. No more volumes can be mounted.

Source: FILESYS.NLM
Explanation: Mounting another volume would exceed the allowed limit for volumes concurrently mounted.
Action: Dismount one or more volumes and try the MOUNT server utility again.

FILESYS-X-802: Volume manager error. Volume name not mounted.

Source: FILESYS.NLM
Possible Cause: An error prevented the volume from being mounted.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.

FILESYS-X-817: Unable to initialize system auditing on volume name. Volume mount aborted.

Source: FILESYS.NLM
Possible Cause: The operating system cannot open the audit file.
Possible Cause: The audit file is already at its maximum size.
Action: Check the size of the auditing file before continuing.

FILESYS-X-818: Unable to allocate memory to mount volume name.

Source: FILESYS.NLM
Possible Cause: The server is out of memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-820: Overlapping segment entry found starting at offset number on server for volume name segment number.

Source: FILESYS.NLM
Explanation: This informational message indicates that the operating system found an overlapping disk area when it tried to mount the volume. The operating system will discard the volume.

FILESYS-X-823: Drive failed while reading in volume information tables.

Source: FILESYS.NLM
Possible Cause: The drive holding the volume had a physical failure while the volume information tables were being read.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

FILESYS-X-825: Total volume size does not match.

Source: FILESYS.NLM
Explanation: Two segments of the volume claim different numbers of segments.
Possible Cause: Two volumes on the server have identical names and a segment from each volume is causing the error.
Action: Unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.
Possible Cause: The volume is corrupted.
Action: If the volume is corrupted, run the ConsoleOne and select Volume Options.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it, and restore the data from the backup.