From: Mikael Pettersson <mikpe@csd.uu.se>
To: zaitcev@redhat.com
Cc: Floydsmith@aol.com, 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: Wed, 5 Sep 2001 00:34:57 +0200 (MET DST) [thread overview]
Message-ID: <200109042234.AAA28635@harpo.it.uu.se> (raw)
On Mon, 3 Sep 2001 20:14:06 -0400, Pete Zaitcev wrote:
>> - 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.
Sorry, but that's not correct. I just ran a test, and the bug is
still there in 2.4.9-ac7. Maybe you're thinking of some other bug?
ide-tape tells me it uses a 14*26KB buffer for my Seagate STT8000A.
If I dd a 39KB (1.5 "buffer units") file with bs=1k to /dev/ht0 it tells
me it wrote 39 blocks. If I then rewind and dd with bs=1k from /dev/ht0
it only reads 26 blocks. The same happens in 2.2 + Hedrick's IDE patch.
2.2 vanilla reads 56 blocks, of which the first 39 are identical to
what I initially wrote. The last 13 contain junk but that's not a big
problem since I back up with tar which writes its own EOF mark.
/Mikael
next reply other threads:[~2001-09-04 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 22:34 Mikael Pettersson [this message]
2001-09-28 3:40 ` idetape broke in 2.4.x-2.4.9-ac5 (write OK but not read) ide-scsi works in 2.4.4 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
-- 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=200109042234.AAA28635@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 \
--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