John R. Jackson wrote:
>> amrestore: short file header block: 26624 bytes
>
>
> What do you get if you do this:
>
> mt -f /dev/tape rewind
> dd if=/dev/tape bs=32k count=1 > /tmp/f0.b0
> ls -l /tmp/f0.b0
> strings /tmp/f0.b0
#mt rewind
#dd if=/dev/tape bs=32k count=1 > /tmp/f0.b0
0+1 records in
0+1 records out
#ll /tmp/f0.b0
-rw-r--r-- 1 root root 26624 Jan 25 09:04 /tmp/f0.b0
#strings /tmp/f0.b0
AMANDA: TAPESTART DATE 20010123 TAPE Optivel-01
>
>
>> amrestore: WARNING: not at start of tape, file numbers will be offset
>
>
> Had you positioned this tape with an fsf or something else before
> running amrecover?
>
> Had you rewound the tape? Amrecover does not do so (or anything else), so
> if it was at the end (or someplace in the middle), bad things will happen.
It gives exactly the same messages (including amidxtaped.debug) whether
amrecover is preceeded by 'mt rewind' or 'mt fsf'. Seems to make no
difference. Many people have said amrecover doesn't rewind, but the
tape drive sure sounds like it does.
>
>
>> Mack
>
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
>
>
>
--
**********************************
Mack Earnhardt
Optivel, Inc.
E-mail: [EMAIL PROTECTED]
Voice: 317.507.6274
Fax: 800.832.5615
Web: http://www.optivel.com
**********************************
