Example--Creating a Packing List
The following example shows the contents of a packing list file.
BASE /home/ignatz LIST plans LIST docs IGNORE *.ps |
The path identified with the BASE statement is the directory where you have items you wish to pack.
The two LIST statements identify specific files within that directory to pack.
The IGNORE statement identifies the file type of .ps, which you do not wish to pack.
How to Pack Files in the Cache With a Packing List
Pack files in the packing list by using the cachefspack -f command, as follows:
$ cachefspack -f packing-list |
-f | Specifies that you want to use a packing list. |
packing-list | Specifies the name of the packing list. |
Example--Packing Files in the Cache With a Packing List
This example uses the list.pkg file as the packing list for the cachefspack command.
$ cachefspack -f list.pkg |
Unpacking Files or Packing Lists From the Cache
You might need to remove, or unpack, a file from the cache. Perhaps you have some files or directories that have a higher priority than others, so you need to unpack the less critical files. For example, you finished up a project and have archived the files that are associated with that project. You are now working on a new project, and therefore, a new set of files.
How to Unpack Files or Packing Lists From the Cache
Unpack files or packing lists from the cache by using the -u or -U option of the cachefspack command.
$ cachefspack -u filename | -U cache-directory |
-u | Specifies that you want the file or files unpacked. You must specify a filename with this option. |
filename | Specifies the name of the file or packing list that you want unpacked in the cache. |
-U | Specifies that you want to unpack all files in the cache. |
For more information about the cachefspack command, see the man page.
Examples--Unpacking Files or Packing Lists From the Cache
The following example shows the file /data/abc/bin/big being unpacked from the cache.
$ cachefspack -u /data/abc/bin/big |
The following example shows several files being unpacked from the cache.
$ cd /data/abc/bin/big $ cachefspack -u big small medium |
The following example shows how to unpack a packing list, which is a file that contains the path to a directory of files, as follows:
$ cachefspack -uf list.pkg |
The following example uses the -U option to specify that all files in a cache directory being unpacked.
$ cachefspack -U /local/mycache |
You cannot unpack a cache that does not have at least one file system mounted. With the -U option, if you specify a cache that does not contain mounted file systems, you see output similar to the following:
$ cachefspack -U /local/mycache cachefspack: Could not unpack cache /local/mycache, no mounted filesystems in the cache. |
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 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 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. Make sure it identifies a directory, not a file.
cachefspack: unable to get shared objects |
- Cause
The executable might be corrupt or it's 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 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. |