Troubleshooting cachefspack Errors

You might see the following error messages when you use the cachefspack command.

cachefspack: pathname - can't open directory: permission denied

Cause

You might not have the correct permissions to access the file or directory.

Action

Set the correct permissions.

cachefspack: pathname - can't open directory: no such file or
directory

Cause

You might not have specified the correct file or directory.

Action

Check for a possible typo.

cachefspack: pathname - can't open directory: stale NFS file handle

Cause

The file or directory might have been moved or deleted from the server at the time you attempted to access it.

Action

Verify that the file or directory on the server is still accessible.

cachefspack: pathname - can't open directory: interrupted system
call

Cause

You might have inadvertently pressed Control-C while issuing the command.

Action

Reissue the command.

cachefspack: pathname - can't open directory: I/O error

Cause

You might have a hardware problem.

Action

Check your hardware connections.

cachefspack: error opening dir

Cause

You might not have specified the correct file or directory. The path identified after the BASE command in the file format could be a file and not a directory. The path specified must be a directory.

Action

Check for a possible typo. Check the path identified after the BASE command in your file format. Ensure that the path identifies a directory, not a file.

cachefspack: unable to get shared objects

Cause

The executable might be corrupt or in a format that is not recognizable.

Action

Replace the executable.

cachefspack: filename - can't pack file: permission denied

Cause

You might not have the correct permissions to access the file or directory.

Action

Set the correct permissions.

cachefspack: filename - can't pack file: no such file or directory

Cause

You might not have specified the correct file or directory.

Action

Check for a possible typo.

cachefspack: filename- can't pack file: stale NFS file handle

Cause

The file or directory might have been moved or deleted from the server at the time you attempted to access it.

Action

Verify that the file or directory on the server is still accessible.

cachefspack: filename- can't pack file: interrupted system call

Cause

You might have inadvertently pressed Control-C while issuing the command.

Action

Reissue the command.

cachefspack: filename- can't pack file: I/O error

Cause

You might have a hardware problem.

Action

Check your hardware connections.

cachefspack: filename- can't pack file: no space left on device.

Cause

The cache is out of disk space.

Action

You need to increase the size of the cache by increasing disk space.

cachefspack: filename - can't unpack file: permission denied

Cause

You might not have the correct permissions to access the file or directory.

Action

Set the correct permissions.

cachefspack: filename - can't unpack file: no such file or directory

Cause

You might not have specified the correct file or directory.

Action

Check for a possible typo.

cachefspack: filename- can't unpack file: stale NFS file handle

Cause

The file or directory might have been moved or deleted from the server at the time you attempted to access it.

Action

Verify that the file or directory on the server is still accessible.

cachefspack: filename- can't unpack file: interrupted system call

Cause

You might have inadvertently pressed Control-C while issuing the command.

Action

Reissue the command.

cachefspack: filename- can't unpack file I/O error

Cause

You might have a hardware problem.

Action

Check your hardware connections.

cachefspack: only one `d', `i', `p', or `u' option allowed

Cause

You specified more than one of these options in a command session.

Action

Select one option for the command session.

cachefspack: can't find environment variable.

Cause

You forgot to set a corresponding environment variable to match the $ in your configuration file.

Action

Define the environment variable in the proper location.

cachefspack: skipping LIST command - no active base

Cause

A LIST command is present in your configuration file but has no corresponding BASE command.

Action

Define the BASE command.