User Guide

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