public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Andre Hedrick <andre@linux-ide.org>
Cc: e.ckhard@u-code.de, marcel@mesa.nl, linux-kernel@vger.kernel.org
Subject: Re: IDE_TAPE problem wiht ONSTREAM DI30
Date: Mon, 4 Dec 2000 09:25:33 +0100 (MET)	[thread overview]
Message-ID: <200012040825.JAA08264@cave.bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10012032315100.13699-100000@master.linux-ide.org> from Andre Hedrick at "Dec 3, 2000 11:16:37 pm"

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.

-- 
** R.E.Wolff@BitWizard.nl ** 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. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-04  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30 16:26 IDE_TAPE problem wiht ONSTREAM DI30 Eckhard Jokisch
2000-11-30 16:05 ` Marcel J.E. Mol
2000-12-03 21:07   ` Eckhard Jokisch
2000-12-04  7:16     ` Andre Hedrick
2000-12-04  8:25       ` Rogier Wolff [this message]
2000-12-04 15:05         ` Kurt Garloff
2000-12-13 21:05           ` [Solved]IDE_TAPE problem with " Eckhard Jokisch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200012040825.JAA08264@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=andre@linux-ide.org \
    --cc=e.ckhard@u-code.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@mesa.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox