We're running amanda 242p2 with a Linux server and Exabyte 220 tape library.
We can't seem to get amrecover to work. We have to manually load the
correct tape and then run amrecover, because if the correct tape is not in,
it's not able to access the tape device.
It appears that somewhere in the amrecover - amrestore - amidxtaped call
chain, we're not getting the correct tape device to amrestore. As shown
below, amrestore is getting passed a tape device of "0". This should
actually be "/dev/tape0", which is specified as "config 0" in our
chg-scsi.conf file. Have we misconfigured something, or is this a bug?
thanks in advance,
Carey
bash$ cat amidxtaped.20010619100843.debug
amidxtaped: debug 1 pid 30070 ruid 401 euid 401 start time Tue Jun 19
10:08:43 2001
amidxtaped: version 2.4.2p2
> SECURITY USER root
> 6
amrestore_nargs=6
> -h
> -p
> 0
> justice
> ^/home$
> 20010614
Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "0"
argv[4] = "justice"
argv[5] = "^/home$"
argv[6] = "20010614"
amrestore: could not open tape 0: No such file or directory
amidxtaped: amrestore terminated normally with status: 2
amidxtaped: could not stat 0
could not stat 0
amidxtaped: pid 30070 finish time Tue Jun 19 10:08:44 2001
bash$
