When I use amrecover to recover file, if the tape that contains those files
isn't in the drive, it will crap out even though it asks me if I want to
mount that tape, and I said Yes.  It seems like 'amrecover' forgets to issue
load tape command after it determins which tape it needs.  It just goes to
the tape drive, and tries to retrieve the file without checking for correct
tape, or mounting the correct tape first.  The output from amrecover and
amidxtaped is pasted below.  It gives out these error because I have the
wrong tape in the drive and 'amrecover' didn't even issue a 'reject' command
to the drive.  If I dont know have any tape in the drive, it simply returns
a "UNKNOWN FILE      amrecover: Can't read file header" error.  Anyone has
solution to this?  I sure hope 'amrecover' doesn't require me to load the
tape manually.

regards,
Mark

amrecover output:
-------
amrecover> add sem.e
Added /sem.e
amrecover> extract

Extracting files using tape drive /dev/rmt/0bn on host frey.
The following tapes are needed: E17900

Restoring files into directory /opt/backup
Continue? [Y/n]:

Load tape E17900 now
Continue? [Y/n/t]:
EOF, check amidxtaped.debug file on frey.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue? [Y/n]:
amrecover>
------------------

amidxtaped output:
----------------------
amandahosts security check passed
> 6
amrestore_nargs=6
> -h
> -p
> /dev/rmt/0bn
> frey
> ^/opt/backup$
> 20020226
Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "/dev/rmt/0bn"
argv[4] = "frey"
argv[5] = "^/opt/backup$"
argv[6] = "20020226"
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore:   0: reached end of information
amidxtaped: amrestore terminated normally with status: 1
Rewinding tape: done
amidxtaped: pid 12778 finish time Thu Feb 28 16:32:56 2002
--------------------

Reply via email to