Hello,
I tried the ide-tape driver for several weeks now. And after some time during
writing or reading tar stops because of errors.
Error messages are:
Nov 30 15:32:20 kernel: ide-tape: ht0: I/O error, pc = 8, key = 0,
asc = 0, ascq = 2 Nov 30 15:32:25 eckhard last message repeated 1000 times
Nov 30 15:32:25 kernel: ide-tape: ht0: unrecovered read error on logical block number 461706, skipping
Nov 30 15:32:25 kernel: ide-tape: ht0: I/O error, pc = 8, key = 0, asc = 0, ascq = 2
Nov 30 15:32:31 last message repeated 1000 times
Nov 30 15:32:31 kernel: ide-tape: ht0: unrecovered read error on logical block number 461707, skipping
Nov 30 15:32:31 kernel: ide-tape: ht0: I/O error, pc = 8, key = 0, asc = 0, ascq = 2
I tried to switch of pipelining by setting the parameters in ide-tape.c to 0
but it didn't help too much ( the error seems to raise later :-(
This happens with 2.2.14, 2.2.17 and 2.4.test11 on SuSE-Linux6.4.
I would really like to help finding the reason for this despite it takes a lot
of time to fill a complete tape with tar.
Please - what's going on there?
Eckhard Jokisch
On Thu, Nov 30, 2000 at 04:26:09PM +0000, Eckhard Jokisch wrote:
>
> I tried the ide-tape driver for several weeks now. And after some time during
> writing or reading tar stops because of errors.
>
> Error messages are:
> Nov 30 15:32:20 kernel: ide-tape: ht0: I/O error, pc = 8, key = 0,
> asc = 0, ascq = 2 Nov 30 15:32:25 eckhard last message repeated 1000 times
> Nov 30 15:32:25 kernel: ide-tape: ht0: unrecovered read error on logical block number 461706, skipping
Block number 461706 is about the last block on the tape. So you probably hit
end of media. The end of tape processing in ide-tape.c doesn'y seem to
be quit robust yet.
I ran into such problems since februari or so and have been in contact with
the ide-tape developers and Onstream about it.
I recently volunteered to try improving the end of media handling (basicly by
implementing early warning EOM) but so far have not had much time to work on it...
-Marcel
--
======-------- Marcel J.E. Mol MESA Consulting B.V.
=======--------- ph. +31-(0)6-54724868 P.O. Box 112
=======--------- [email protected] 2630 AC Nootdorp
__==== http://www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
They couldn't think of a number, so they gave me a name!
-- Rupert Hine
Am Don, 30 Nov 2000 schrieben Sie:
> On Thu, Nov 30, 2000 at 04:26:09PM +0000, Eckhard Jokisch wrote:
> >
> > I tried the ide-tape driver for several weeks now. And after some time during
> > writing or reading tar stops because of errors.
> >
> > Error messages are:
> > Nov 30 15:32:20 kernel: ide-tape: ht0: I/O error, pc = 8, key = 0,
> > asc = 0, ascq = 2 Nov 30 15:32:25 eckhard last message repeated 1000 times
> > Nov 30 15:32:25 kernel: ide-tape: ht0: unrecovered read error on logical block number 461706, skipping
....
> I ran into such problems since februari or so and have been in contact with
> the ide-tape developers and Onstream about it.
> I recently volunteered to try improving the end of media handling (basicly by
> implementing early warning EOM) but so far have not had much time to work on it...
Where can I start to do that?
Can you tell me how I can set the debug_level to 3 or 5?
Why do I get this errors on make modules when I compile the driver with
IDETAPE_DEBUG_LOG_VERBOSE to 1 in ide-tape.c?: gcc -D__KERNEL__
-I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
-fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i686
-malign-functions=4 -DMODULE -DMODVERSIONS -include
/usr/src/linux/include/linux/modversions.h -c -o ide-tape.o ide-tape.c
ide-tape.c: In function `idetape_sense_key_verbose': ide-tape.c:1395: warning:
function returns address of local variable ide-tape.c: In function
`idetape_command_key_verbose': ide-tape.c:1413: parse error before `case'
ide-tape.c:1424: warning: function returns address of local variable make[2]:
*** [ide-tape.o] Error 1 make[2]: Leaving directory
`/src/2.4-test11/drivers/ide' make[1]: *** [_modsubdir_ide] Error 2 make[1]:
Leaving directory `/src/2.4-test11/drivers' make: *** [_mod_drivers] Error 2
Hopefully
Eckhard
On Sun, 3 Dec 2000, Eckhard Jokisch wrote:
> Am Don, 30 Nov 2000 schrieben Sie:
> > On Thu, Nov 30, 2000 at 04:26:09PM +0000, Eckhard Jokisch wrote:
> > >
> > > I tried the ide-tape driver for several weeks now. And after some time during
> > > writing or reading tar stops because of errors.
> > >
> > > Error messages are:
> > > Nov 30 15:32:20 kernel: ide-tape: ht0: I/O error, pc = 8, key = 0,
> > > asc = 0, ascq = 2 Nov 30 15:32:25 eckhard last message repeated 1000 times
> > > Nov 30 15:32:25 kernel: ide-tape: ht0: unrecovered read error on logical block number 461706, skipping
You have to love the new ARD media...
> ....
>
> > I ran into such problems since februari or so and have been in contact with
> > the ide-tape developers and Onstream about it.
> > I recently volunteered to try improving the end of media handling (basicly by
> > implementing early warning EOM) but so far have not had much time to work on it...
>
> Where can I start to do that?
> Can you tell me how I can set the debug_level to 3 or 5?
> Why do I get this errors on make modules when I compile the driver with
> IDETAPE_DEBUG_LOG_VERBOSE to 1 in ide-tape.c?: gcc -D__KERNEL__
> -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
> -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i686
> -malign-functions=4 -DMODULE -DMODVERSIONS -include
> /usr/src/linux/include/linux/modversions.h -c -o ide-tape.o ide-tape.c
> ide-tape.c: In function `idetape_sense_key_verbose': ide-tape.c:1395: warning:
> function returns address of local variable ide-tape.c: In function
> `idetape_command_key_verbose': ide-tape.c:1413: parse error before `case'
> ide-tape.c:1424: warning: function returns address of local variable make[2]:
> *** [ide-tape.o] Error 1 make[2]: Leaving directory
> `/src/2.4-test11/drivers/ide' make[1]: *** [_modsubdir_ide] Error 2 make[1]:
> Leaving directory `/src/2.4-test11/drivers' make: *** [_mod_drivers] Error 2
This I can fix, but the decoding noise makers are still in progress.
Andre Hedrick
Linux ATA Development
Andre Hedrick wrote:
> On Sun, 3 Dec 2000, Eckhard Jokisch wrote:
>
> > Am Don, 30 Nov 2000 schrieben Sie:
> > > On Thu, Nov 30, 2000 at 04:26:09PM +0000, Eckhard Jokisch wrote:
> > > >
> > > > I tried the ide-tape driver for several weeks now. And after some time during
> > > > writing or reading tar stops because of errors.
> > > >
> > > > Error messages are:
> > > > Nov 30 15:32:20 kernel: ide-tape: ht0: I/O error, pc = 8, key = 0,
> > > > asc = 0, ascq = 2 Nov 30 15:32:25 eckhard last message repeated 1000 times
> > > > Nov 30 15:32:25 kernel: ide-tape: ht0: unrecovered read error on logical block number 461706, skipping
>
> You have to love the new ARD media...
>
> > ....
> >
> > > I ran into such problems since februari or so and have been in contact with
> > > the ide-tape developers and Onstream about it.
Stay away from onstream is my advice nowadays.
We've been trying to get the stupid thing to work since july 8th, and
onstream technical support has been very helpful by telling us what to
do and such. Like downgrading to a kernel version that has known
remote attacks. However doing that does not solve the problems we
report. After much ado, they promise to "escalate" the problem to
people in the states, and then this does not lead to results in
the month we've given them.
In short: in the simplest case, just writing a stream of bytes to the
drive, it works. But the drive then doesn't nearly have the "raw error
rate" that they claim.
If you start using a backup program that needs to seek back and forth
a few times, the drive loses track where it is, and doesn't recover
from this situation.
I've returned mine to my vendor, and I hope that Onstream gets the
message in the end: They do NOT support Linux.
Roger.
--
** [email protected] ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
Hi,
On Mon, Dec 04, 2000 at 09:25:33AM +0100, Rogier Wolff wrote:
> Stay away from onstream is my advice nowadays.
I've been using the USB and the SCSI versions of OnStream tapes with
good success!
> We've been trying to get the stupid thing to work since july 8th, and
> onstream technical support has been very helpful by telling us what to
> do and such.
If you want a really helpful advice:
Use the osst driver and the use it with ide-scsi.
Report problems to the osst mailing list.
So far, I'm not aware of anybody we failed to help.
http://linux1.onstream.nl/test/
> Like downgrading to a kernel version that has known remote attacks.
Who did give such a stupid advice?
> However doing that does not solve the problems we
> report. After much ado, they promise to "escalate" the problem to
> people in the states, and then this does not lead to results in
> the month we've given them.
I'm afraid I do not know too much about the ide-tape support for DI-30.
Gadi Oxman is the author of it (has been paid by OnStream to write it, BTW),
but he may be short on time at the moment to help you with the problem.
> If you start using a backup program that needs to seek back and forth
> a few times, the drive loses track where it is, and doesn't recover
> from this situation.
I don't know whether this is a hard- or a software problem in your case.
> I've returned mine to my vendor, and I hope that Onstream gets the
> message in the end: They do NOT support Linux.
I have a completely different impression. Otherwise neither the DI-30 would
be supported by ide-tape, nor would there be the osst driver, supporting
SC-x0, DI-30 (over ide-scsi) and USB30 (usb-storage in 2.4 w/ Freecom
support).
Regards,
--
Kurt Garloff <[email protected]> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG SCSI, Security
On Mon, 04 Dez 2000, Kurt Garloff wrote:
>
> If you want a really helpful advice:
> Use the osst driver and the use it with ide-scsi.
> Report problems to the osst mailing list.
> So far, I'm not aware of anybody we failed to help.
> http://linux1.onstream.nl/test/
This was really really helpfull :-)
It just works fine now.
Wouldn't it be good to put a slight hint somewhere in the kernel
configuration?
BR
Eckhard Jokisch