User Guide

FILESYS - File System Messages 99
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
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.