All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: guthrie@home.martnet.com, linux-kernel@vger.kernel.org
Subject: Re: unable to read from IDE tape
Date: Sat, 30 Jun 2001 22:41:36 -0400	[thread overview]
Message-ID: <200107010241.f612fa209443@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.993932281.2803.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.993932281.2803.linux-kernel2news@redhat.com>

> Lately, I have been having problems reading from from my HP Colorado IDE
> tape drive.  I can use mt to get the status of the drive and to forward the
> drive to a different file.  I can even use tar to write to the tape.
> But whenever I try to read the tar files that I have written to tape, I
> get an I/O error, and there doesn't even seem to be any attempt by the
> driver to read the tape.  This is currently happening under 2.4.5, and
> has been happening undeer at least 2.4.2 and 2.4.3, I think it was also
> happening under 2.4.1 as well.
>[...]
> Any thoughts on what might be wrong?

No good thoughts, the driver is simply horrible...
You might be able to pick some interesting info by
running with tape->debug_level set to 4 (There is an option,
but I forget what. Just assign 4 to it after
a call to idetape_add_settings. Be prepared for a lots of
tracing.

If you come up with any patches, post them to the list.

-- Pete

       reply	other threads:[~2001-07-01  2:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.993932281.2803.linux-kernel2news@redhat.com>
2001-07-01  2:41 ` Pete Zaitcev [this message]
2001-07-04 22:48 unable to read from IDE tape John Guthrie
2001-07-05  0:27 ` Tim Moore
  -- strict thread matches above, loose matches on Subject: below --
2001-06-30 20:15 John Guthrie

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=200107010241.f612fa209443@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=guthrie@home.martnet.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.