HP-UX Reference (11i v2 03/08) - 1M System Administration Commands N-Z (vol 4)

v
vxrestore(1M) vxrestore(1M)
You can override a termination in interactive mode or by specifying the
-y option when you invoke vxre-
store. If a termination is overridden,
vxrestore tries to skip over bad data and continue restoring.
It is not a good practice to do this except under extraordinary circumstances. As part of normal
dump/restore processing, it is best to identify the underlying cause of the problem and repair it.
Error Conditions
Error conditions that can terminate a restore can be grouped into the following general categories:
• media problems
• resource or permission problems
• consistency check failures
A media error can occur while accessing the dump/restore media, or may be caused by selecting an
incorrect volume for restore processing. Also check for physical problems such as damage to the tape,
and be sure that the tape drive is cleaned. Some typical media problem error messages are:
no header after volume mark!
ran off end of tape
not at beginning of a file
unknown tape header type number
unexpected tape header
partial block read: size should be size
Changing volumes on pipe input?
active file into volume 1
A resource allocation or permission problem can occur while trying to allocate or access files or memory
space required by vxrestore for its internal processing. To avoid some common problems, be sure you
are running with the correct UID, that target files have write permission, and that there is sufficient
memory. Some typical resource allocation or permission error messages are:
no memory to extend symbol table
no memory directory table
no space for string table
no memory for entry table
cannot allocate space for symbol table
no memory for file removal list
no memory for file dump list
cannot create save file filename for symbol table
output error to file filename writing symbol table
cannot open symbol table file filename
cannot stat symbol table file filename
cannot read symbol table file filename
A consistency check failure generally occurs while examining the data on the dump/restore media. This
kind of problem may be caused by a media failure, by dumping a mounted and active file system, or
because of an error in media or parameter selection. Some typical consistency check failure error mes-
sages are:
Root directory is not on tape
cannot find directory inode inumber
error setting directory modes
Cannot find directory inode inumber named name
corrupted symbol table
state name impossible state
inumber bad first
unknown file on tape
missing inumber inumber
addino: out of range inumber
deleteino: out of range inumber
deleteino: inumber not found
name is not a directory
name path name too long
bad name to addentry name
link to non-existent name
duplicate entry
Section 1M−−906 Hewlett-Packard Company − 4 − HP-UX 11i Version 2: August 2003