Hi,
I have been using amanda to succesfully back-up to an OnStream SC-50
tape drive. I realize these are rather poor tape drives, but right now
that's all we have, and I'd like to make it work if possible. I am
able to backup, but restoring is possible but difficult.
I am running a modified RedHat 6.2 installation with kernel 2.2.21.
The machine has 80 MB RAM and is a Pentium 200. I am using an Adaptec
2940UW SCSI adapter to drive the SC-50. I am using amanda-2.4.2p2. As
a side-note, I am running a DI-30 OnStream drive from this machine as
well. I don't have any tapes for it right now so I haven't been able
to test it for this problem. DI-30=/dev/nosst0, SC-50=/dev/nosst1.
I am having no trouble backing up my data, I can also run amverify
and get no errors. I also run the "mt -f /dev/nosst1 stoptions
scsi2log" after each tape change as recommended by OnStream. The
problem I am having is with amrecover. I rewind the tape and attempt
to use amrecover, but everytime I extract I get the following error
message in amrecover:
Restoring files into directory /root
Continue? [Y/n]: Y
Load tape DailySet102 now
Continue? [Y/n]: Y
(2 minute pause here)
EOF, check amidxtaped.debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Now, I have gone through just about every message I could find about
this error, and nothing matches the problem. Like I said, my
permissions are all okay, I have rewound the tape, etc. Here is an
excerpt of my amidxtape.debug file:
amanda ahosts security check passed
> 6
amrestore_nargs=6
> -h
> -p
> /dev/nosst1
> intip
> ^/$
> 20020703
Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "/dev/nosst1"
argv[4] = "intip"
argv[5] = "^/$"
argv[6] = "20020703"
amrestore: 0: skipping start of tape: date 20020703 label
DailySet102
amrestore: 1: skipping intip._var.20020703.0
amidxtaped: amrestore terminated normally with status: 0
Rewinding tape: done
amidxtaped: pid 26638 finish time Wed Jul 10 14:17:31 2002
However, I can actually recover the file I'm looking for if before
recovering the file, I issue "mt -f /dev/nosst1 fsf 4" which skips four
filemarks ahead to where the disk I am trying to restore from exists on
the tape. If I manually skip ahead I can restore every time.
Shouldn't amrecover be able to get beyond the first filemark?
It is apparent from the debug file and the amrecover error that it
tries to skip past the first filemark, and at that point it can't read
the header of the next file and gives up. However, amverify works fine
and gives no errors (it does see all files on the tape, not just the
first one). Is this a problem with amanda that others have had, or is
this just a result of using an OnStream drive?
Thank you,
Leif Gustafson