Database Error Messages

No directory entry was found for the indicated file. There are two possible causes:

1. The file had no corresponding directory entry.
2. The file had a directory entry, but there was a problem with corresponding directory file.

If fsck with the -a switch is currently running, then no further action is needed. If fsck without the -a switch is running, then run fsck with the -a switch to resolve the problem. fsck will attempt to repair any directories that are in an inconsistent state first. Any file that does not have a valid directory entry following directory repairs will be moved to the 'lost+found' directory.

No directory entry was found for the indicated file. There are two possible causes:

1. The file had no corresponding directory entry.
2. The file had a directory entry, but there was a problem with corresponding directory file.

If the ACFS Fixer is currently running, then no further action is needed. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will attempt to repair any directories that are in an inconsistent state first. Any file that does not have a valid directory entry following directory repairs will be moved to the 'lost+found' directory.

No directory entry was found for the indicated file. There are two possible causes:

1. The file had no corresponding directory entry.
2. The file had a directory entry, but there was a problem with corresponding directory file.

If the ACFS Fixer is currently running, then no further action is needed. If the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS Fixer will attempt to repair any directories that are in an inconsistent state first. Any file that does not have a valid directory entry following directory repairs will be moved to the 'lost+found' directory.