From: Mikael Pettersson <mikpe@csd.uu.se>
To: 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: Sat, 1 Sep 2001 20:08:21 +0200 (MET DST) [thread overview]
Message-ID: <200109011808.UAA20786@harpo.it.uu.se> (raw)
On Sat, 1 Sep 2001 11:03:12 EDT, Floydsmith@aol.com wrote:
>Now, I can get everything (my ide ls-120 and ide HP 8Gig tape) to work in
>...
>If I try not to use SCSI emulation for all 2.4.x kernels (including:
>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)
>
>As mentioned above, scsi emulation works for 2.4.4 (reads and writes). But if
>turned on in 2.4.9-ac5, then I get
>/dev/st0: No such device
FWIW, my Seagate 4/8 GB ATAPI tape drive works just fine in all
2.4.x kernels as /dev/{n,}ht0 -- no SCSI emulation for me.
There are two known problem areas, which may or may not explain
your problems:
- 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.
The driver will log the block size to the kernel log when it's
initializing, so you can take that value and pass it to your
backup utility (26KB in my case so I pass -b52 to tar).
- 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.
/Mikael
next reply other threads:[~2001-09-01 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 18:08 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-04 22:34 Mikael Pettersson
2001-09-28 3:40 ` Pete Zaitcev
2001-09-28 9:15 ` Mikael Pettersson
2001-09-29 2:35 ` Pete Zaitcev
[not found] <mailman.999367801.660.linux-kernel2news@redhat.com>
2001-09-04 0:14 ` Pete Zaitcev
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=200109011808.UAA20786@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=Floydsmith@aol.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tape@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
all inboxes | Powered by JetHome®