From: Pete Zaitcev <zaitcev@redhat.com>
To: mikpe@csd.uu.se, Floydsmith@aol.com
Cc: linux-kernel@vger.kernel.org, linux-tape@vger.kernel.org
Subject: Re: idetape broke in 2.4.x-2.4.9-ac5 (write OK but not read) ide-scsi works in 2.4.4
Date: Mon, 3 Sep 2001 20:14:06 -0400 [thread overview]
Message-ID: <200109040014.f840E6m00316@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.999367801.660.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.999367801.660.linux-kernel2news@redhat.com>
> >Kernel 2.4.9-ac5 on i686
> >then
> >ide-tape: ht0: I/O error, pc = 8, key = 5, asc = 2c, ascq = 0
> >tar: /dev/ht0: Cannot read: Input/output error
> >(writes work OK though)
> - block size: The 2.4 ide-tape driver only works reliably if you
> write data with the correct block size. If you don't write full
> blocks the last block of data may not be readable.
I fixed that some time ago, it's in current -ac
if not in Linus's tree. The bug has nothing to do
with the ASC=2c problem the original poster complained.
> - HP's not-quite ATAPI drives: Don't know about your model, but the
> HP 14(?)GB model is believed to deviate from ATAPI standards.
Colorado sucks... I think I have a bug pending about it,
did not look well yet. IIRC it was giving ASC=24, not 2c.
I'll look it up.
-- Pete
next parent reply other threads:[~2001-09-04 0:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.999367801.660.linux-kernel2news@redhat.com>
2001-09-04 0:14 ` Pete Zaitcev [this message]
2001-09-04 22:34 idetape broke in 2.4.x-2.4.9-ac5 (write OK but not read) ide-scsi works in 2.4.4 Mikael Pettersson
2001-09-28 3:40 ` Pete Zaitcev
2001-09-28 9:15 ` Mikael Pettersson
2001-09-29 2:35 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2001-09-01 18:08 Mikael Pettersson
2001-09-01 15:03 Floydsmith
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=200109040014.f840E6m00316@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=Floydsmith@aol.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tape@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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