The following includes messages from LFS.NLM.
LFS-X-60: Error writing to the extended directory space.
Source:
LFS.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.
LFS-X-61: Error writing to file (filename not accessible) data stream number. Write was requested by the SERVER.
Source:
LFS.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.
LFS-X-62: Error writing to file (filename not accessible) data stream number. Write was requested by user name on station number.
Source:
LFS.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.
LFS-X-63: Error writing to file name data stream number. Write was requested by the SERVER. File path path.
Source:
LFS.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.
LFS-X-64: Error writing to file name data stream number. Write was requested by user name on station number. File path server/volume.
Source:
LFS.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.
LFS-X-65: File read error at offset offset data stream number. Error getting filename. Read was requested by the SERVER.
Source:
LFS.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.
LFS-X-66: File read error at offset offset data stream number. Error getting filename. Read was requested by user name on station number.
Source:
LFS.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.
LFS-X-67: Error reading file name. Offset offset data stream number. Read was requested by the SERVER. File path path.
Source:
LFS.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.
LFS-X-68: Error reading file name. Offset offset data stream number. Read was requested by user name on station number. File path path.
Source:
LFS.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.
LFS-X-69: File write pre-read error. Offset offset data stream number. Error getting filename. Read was requested by the SERVER.
Source:
LFS.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.
LFS-X-70: File write preread error. Offset offset data stream number. Error getting filename. Read was requested by user name on station number.
Source:
LFS.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.
LFS-X-71: File name write preread error. Offset offset data stream number. Read was requested by the SERVER. File path path.
Source:
LFS.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.
LFS-X-73: Volume server\volume out of disk space. There are no deleted files using disk space.
Source:
LFS.NLM
Possible Cause:
When the volume is out of disk space, this message will be broadcast to all users on the system. All attempts to write to files will fail because of insufficient disk space.
LFS-X-74: Volume server\volume out of disk space. Number KB of disk space is in use by deleted files. No deleted files have been deleted long enough to purge yet.
Source:
LFS.NLM
Possible Cause:
When the volume is out of disk space, this message will be broadcast to all users on the system. All attempts to write to files will fail because of insufficient disk space. The second line of the message indicates that deleted files have not yet been purged. The third line indicates that all the deleted files cannot be purged yet because the preset purge time has not elapsed. Users might not be able to save files they are using and might lose data.
LFS-X-75: Volume server\volume almost out of disk space.
Source:
LFS.NLM
Possible Cause:
The volume is about to run out of disk space.