public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Guthrie <guthrie@home.martnet.com>
To: linux-kernel@vger.kernel.org
Subject: Re: unable to read from IDE tape
Date: Wed, 4 Jul 2001 18:48:26 -0400	[thread overview]
Message-ID: <200107042248.SAA06196@home.martnet.com> (raw)

In-Reply-To: <200107022319.TAA19681@home.martnet.com>

Note: the following is my reply to a private reply to my initial post regarding
my problem reading from my tape drive.  I thought that this info might be
helpful on the mailing list as well.


Willem Riede <osst@riede.org> wrote:
> John Guthrie wrote:
> >
> > Hi all,
> >
> > 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
>
> Can you be more specific, and post exactly what commands you issued after
> inserting the tape, and what error you get when, including any log messages?

First, I run

mt rewind

just to get the tape back to the beginning.  (I think that I may have /dev/tape
as asymlink to /dev/nht0, not /dev/ht0.)  Then just as a test, I can do
something like

tar -cvf /dev/nht0 /boot

This command actually runs fine with no errors.  If I then run

mt status

I get the output

SCSI 2 tape drive:
File number=0, block number=16841, partition=0.
Tape block size 512 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (0):

At least the block number is non-zero as I should expect it to be since
I did the tar to /dev/nht0.  If I then run

mt rewind; mt status

I get the output

SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (0):

So now the block number is at 0, which is good since I did just rewind the
thing.  At this point, I would expect (perhaps mistakenly) that I should
be able to run the following

tar -tf /dev/ht0

The output of this command is

tar: /dev/ht0: Cannot read: Input/output error
tar: At beginning of tape, quitting now
tar: Error is not recoverable: exiting now

>
> > 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.
>
> Can you verify that (by rebooting to previous kernels if you still have them)?
> Does it happen with all your tapes?

This is the same error that I have gotten from both 2.4.2 and 2.4.3.  It
definitely happens with all of my tapes including my new ones.  (Due to
circumstanes of my setup, I can't verify 2.4.1 this exact minute, but I can
get back to you on that.)

I am also getting the following lines of dmesg output:

ide-tape: Reached idetape_chrdev_open
ide-tape: ht0: I/O error, pc =  8, key =  5, asc = 2c, ascq =  0

I don't know if this helps.  Apparently IDETAPE_DEBUG_LOG is set to 1 by
default.  Which actually results in a large number of copies of the first line.
I only get the second line when I try to open the tape for reading.

> Regards. Willem Riede.

John Guthrie
guthrie@martnet.com

             reply	other threads:[~2001-07-04 22:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-04 22:48 John Guthrie [this message]
2001-07-05  0:27 ` unable to read from IDE tape Tim Moore
     [not found] <mailman.993932281.2803.linux-kernel2news@redhat.com>
2001-07-01  2:41 ` Pete Zaitcev
  -- 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=200107042248.SAA06196@home.martnet.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox