>#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
That's got to be something like:
* A hardware problem.
* A drive settings problem.
* A hardware block size mismatch problem (see my other post today).
I'd stick a scratch tape in the drive and start playing with short files
with 32 KByte blocks and make sure I could get them back. I'd also
check the hardware block size and drive settings.
>... Many people have said amrecover doesn't rewind, but the
>tape drive sure sounds like it does.
I can guarantee you amrecover/amrestore do **not** rewind. Many people,
including myself, use that feature to position the tape by hand because
it's faster on some devices than scanning through file by file.
If the drive is rewinding, you may have the wrong device, although your
other mail seems to indicate that's OK. I'd guess you're just hearing
the drive wind up for I/O, not actually doing a rewind.
>Mack Earnhardt
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
