[591] in linux-scsi channel archive
Stopping tape from rewinding
daemon@ATHENA.MIT.EDU (Louis Mandelstam)
Wed Sep 6 21:21:39 1995
Date: Wed, 6 Sep 1995 17:02:21 +0200 (GMT+0200)
From: Louis Mandelstam <louis@khotso.sacc.wn.apc.org>
To: linux-scsi@vger.rutgers.edu
Good day.
I'm having a problem with a tape drive which rewinds automatically after
doing anything, and I can't seem to prevent this. I'm not sure whether
this is a software or hardware problem, but let's see what other Linux
SCSI users can offer.
Linux 1.2.13, with Jun14 aic7xxx patch.
Adaptec aha2940 host.
Drive details from bootup text:
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 1.45/1.17/1.19
scsi : 1 host.
aic7xxx: Scanning channel A for devices.
aic7xxx: target 1 now synchronous at 4.4Mb/s, offset = 0xe
Vendor: WANGTEK Model: 5525ES SCSI REV7 Rev: 3J
Type: Sequential-Access ANSI SCSI revision: 01
Detected scsi tape st0 at scsi0, id 1, lun 0
If I execute something like:
tar vcf /dev/tape /root
the tape wins audibly, and after a while, tar exits.
Executing "tar vtf /dev/tape" lists, as expected, the files just written.
"mt retension" does as expected.
"mt fsr 1" and "mt fsr 1000" do as expected, with markedly different
times taken.
In every case hoever, the tape is rewound after completing the action.
Whenever I do "mt tell" I get "At block 0." and this is quite correct, as
the tape really is at the beginning at this point. I can also hear the
tape being rewound after doing as told.
Now the problem with all this is that I can only put one archive on a
tape, because there's no way to wind to the end of the first file and
then writing a second, as the tape will be rewound and my second file
gets written from the beginning of the tape, over the first.
Trying to get tar to append to the tape gets me the following:
root:~# tar Af /dev/tape khotso.boot
tar: can't write to /dev/tape : I/O error
root:~#
The error message only appears after I can hear the tape being wound past
the first tar already on the tape, so it's as if the error occurs as soon
as tar tries to write to the end of the first archive.
Also, along with the above error, the kernel logs:
st0: Error 28000002. extra data not valid Current error st0: sns = 70 5
Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x38 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x08
st0: Error on write filemark.
I'm out of ideas. I've been trying to email someone at Wang to check
whether maybe it's just something like a jumper setting on the drive, but no
luck there yet.
I can certainly use the drive as it is, but it would be nicer if I can
put more than one archive on a tape. Also, ntape (which looks like some
pretty decent software) doesn't work, because the identifying header it
puts on the tape gets overwritten the first time I try to add an archive
to the tape, so ntape no longer recognizes the tape.
So, can anyone please provide some clues?
Thanks in advance.
Regards
----------------------------------------------------------------------
L.Mandelstam - System Administrator louis@sacc.wn.apc.org
S A Council of Churches, PO Box 4921, Johannesburg, 2000, South Africa
tel:+27-11-492-1380 x249 fax:+27-11-492-1448
----------------------------------------------------------------------
