idetape broke in 2.4.x-2.4.9-ac5 (write OK but not read) ide-scsi works in 2.4.4
Quoted 6 lines · Pete Zaitcev
Quoted 3 lines
- 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
Quoted 10 lines
Date: Wed, 5 Sep 2001 00:34:57 +0200 (MET DST)
From: Mikael Pettersson <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
[email protected]Quoted 4 lines
Quoted 3 lines
- 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.
Quoted 5 lines
Quoted 2 lines
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?
OK, perhaps you are right. I received a credible report from Ed Tomlinson that the "reading the last block" bug is in 2.4.10.
It seems that either I fixed something else with the same symptoms or I fixed it improperly. Unfortunately, I cannot reproduce it.
By the way, why does everyone insist on using ide-tape? It seems to be broken beyond any repair by injection of lethal poison marked "OnStream Support" (not that it was brilliant before, but that was the last nail in the coffin). Just use ide-scsi and be done with it. I really do not enjoy reading ide-tape.c.
-- Pete
Quoted 5 lines · Pete Zaitcev
By the way, why does everyone insist on using ide-tape? It seems to be broken beyond any repair by injection of lethal poison marked "OnStream Support" (not that it was brilliant before, but that was the last nail in the coffin). Just use ide-scsi and be done with it. I really do not enjoy reading
ide-tape.c.
I agree that ide-tape.c looks like a buggy piece of cr*p, but apart from that, what would I gain from using scsi tape on top of ide-scsi? Would it magically work on broken Colorados?
/Mikael
Quoted 10 lines
From: Mikael Pettersson <[email protected]>
Date: Fri, 28 Sep 2001 11:15:07 +0200
Cc: [email protected], [email protected]Quoted 5 lines
By the way, why does everyone insist on using ide-tape? It seems to be broken beyond any repair by injection of lethal poison marked "OnStream Support" (not that it was brilliant before, but that was the last nail in the coffin). Just use ide-scsi and be done with it. I really do not enjoy reading
ide-tape.c.
Quoted 3 lines
I agree that
ide-tape.clooks like a buggy piece of cr*p, but apart from that, what would I gain from using scsi tape on top of ide-scsi? Would it magically work on broken Colorados?
Umm... I hope someone else would fix ide-scsi when it breaks :)
I fixed Colorado, but it's certainly not the last bug. Frist, DMA must be off, and it is often on by default. Second, Dell QA already filed a new tapemark related bug...
-- Pete