mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Guthrie <guthrie@home.martnet.com>
To: guthrie@martnet.com, linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Re: [PATCH] small patch to ide-tape.c
Date: Wed, 4 Jul 2001 19:02:08 -0400	[thread overview]
Message-ID: <200107042302.TAA08608@home.martnet.com> (raw)

Pete Zaitcev <zaitcev@redhat.com> wrote:
> > This patch adds a missing semicolon that is noticed only if you define
> > IDETAPE_DEBUG_LOG_VERBOSE:
> > 
> > John Guthrie
> > guthrie@martnet.com
> 
> It makes me curious, why do you need to define
> IDETAPE_DEBUG_LOG_VERBOSE?
> 
> I fixed some stuff with files not restoring properly
> with last block corrupt. Talking with Andre and Gadi now.
> What is your problem?

I sent out some posts earlier on this.  To summarize, I have an HP Colorado
5GB IDE tape drive.  I have been able to use mt to move the tape forward, find
out where the tape is positioned, rewind it, etc.  I have also been able to
use tar to write to the tape drive.  When I try to use tar to read from the
tape drive though, I get the following as output:

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

The following also appears in dmesg output when I try to run the tar command:

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

Willem Riede suggested to me that I try turning IDETAPE_DEBUG_LOG_VERBOSE on
to help with debugging.  That iswhen I ran into this line that as missing a
semicolon.

John Guthrie
guthrie@martnet.com

             reply	other threads:[~2001-07-04 23:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-04 23:02 John Guthrie [this message]
     [not found] <mailman.994203003.28209.linux-kernel2news@redhat.com>
2001-07-04  0:36 ` Pete Zaitcev
  -- strict thread matches above, loose matches on Subject: below --
2001-07-03 23:27 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=200107042302.TAA08608@home.martnet.com \
    --to=guthrie@home.martnet.com \
    --cc=guthrie@martnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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

all inboxes | Powered by JetHome®