Anil, Robert,

Please try the following patch. We don't understand the reason why
this "block 3015" problem is becoming so common now where it didn't
appear before; something must have changed, but in any case, the
following ide-tape patch should work around it.

Andre, please include it in one of your 2.2.15 patches, to avoid
repeated reports about it.

Cheers,

Gadi

--- ide-tape.c~ Fri Apr 28 12:12:25 2000
+++ ide-tape.c  Fri Apr 28 12:13:58 2000
@@ -3834,8 +3834,12 @@
 #endif
                                clear_bit(IDETAPE_PIPELINE_ERROR, &tape->flags);
                                position = idetape_read_position(drive);
-                               printk(KERN_INFO "ide-tape: %s: blank block detected, 
positioning tape to block %d\n", tape->name, position + 60);
-                               idetape_position_tape(drive, position + 60, 0, 1);
+                               if (position >= 2980 && position < 3000)
+                                       position = 3000;
+                               else
+                                       position += 60;
+                               printk(KERN_INFO "ide-tape: %s: blank block detected, 
+positioning tape to block %d\n", tape->name, position);
+                               idetape_position_tape(drive, position, 0, 1);
                                cnt += 40;
                                continue;
                        } else

On 22 May 2000, Anil B. Somayaji wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I've spent the past few days trying to get my new OnStream DI-30 IDE
> tape drive working, with little success.  I thought I might have a
> hardware problem, but the drive works fine under windows (backup and
> compare of a 2G partition works correctly consistently).  For good
> measure, I even replaced the IDE cable with the one supplied with the
> drive - that made no difference.
> 
> Although I've seen other problems, the most consistent one seems to be
> a problem with verifying a tape.  I can do a tar of a 1.2G partition,
> and that will work fine.  However, a compare of that same partition
> aborts relatively quickly, with messages like this:
> 
>   May 22 00:09:20 lydia kernel: ide-tape: ht0: skipping frame,
>     logical_blk_num 3015 (expected 8)
>   May 22 00:09:20 lydia kernel: ide-tape: ht0: couldn't find logical
>      block 8, aborting (block 3015 found)
>   May 22 00:09:20 lydia kernel: ide-tape: ht0: skipping frame,
>      logical_blk_num 3015 (expected 9)
>   May 22 00:09:20 lydia kernel: ide-tape: ht0: couldn't find logical
>      block 9, aborting (block 3015 found)
> 
> The weird part is the references to block 3015 are very, very common -
> even with different tapes.  I've gotten this error with 2, possibly 3
> tapes, with different kernels, over 3 days of testing.
> 
> I'm using the patches from the OnStream web site:
>   ide.2.2.14.20000124.patch.gz
>   ide_2_2_15_20000504_patch.gz
> 
> I've played with patched versions of both 2.2.14 and 2.2.15 (both of
> which are stable for me otherwise).  I've tried building the kernel
> using gcc 2.95.2 and 2.7.2.3.  I've built it both with and without
> chipset-specific support.
> 
> One other big glitch - my X server (Mach64 3.3.6) has a tendency to
> lock up completely when the tape is being accessed, if you do things
> like switch virtual screens around.  The lock is total - keyboard and
> mouse death, uninterruptible sleep.  Remote logins still work, though,
> and the machine can be rebooted that way.  Even under heavy load, my X
> server has never acted this badly.
> 
> I've also seen messages about lost interrupts on hdd (the drive is set
> up as my IDE secondary slave), and DMA problems; however, my hard
> drive has worked consistently with Ultra DMA access (it is a Maxtor
> 91020D6 10G).  Also, disabling DMA on hdd using hdparm doesn't fix
> things.
> 
> My system is an HP Pavilion 8260, which has an Intel 440LX chipset.
> The DI-30 firmware is reported as version 1.06.  My system is running
> Debian 2.2 (potato).  My current kernel (patched 2.2.14) uses the
> following options in the block section:
> 
> CONFIG_BLK_DEV_FD=y
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDEDISK=y
> CONFIG_BLK_DEV_IDECD=y
> CONFIG_BLK_DEV_IDETAPE=m
> CONFIG_BLK_DEV_IDEPCI=y
> CONFIG_BLK_DEV_IDEDMA=y
> CONFIG_IDEDMA_AUTO=y
> IDEDMA_PCI_EXPERIMENTAL=y
> CONFIG_BLK_DEV_PIIX=y
> CONFIG_BLK_DEV_PIIX_TUNING=y
> CONFIG_BLK_DEV_LOOP=m
> CONFIG_BLK_DEV_RAM=m
> CONFIG_PARIDE_PARPORT=m
> CONFIG_BLK_DEV_IDE_MODES=y
> 
> I can think of more tests to try, but right now I'd just be shooting
> in the dark.  Anyone have a clue about what's going on?
> 
> Thanks!
> 
>   --Anil
> 
> - -- 
> Anil Somayaji ([EMAIL PROTECTED])
> http://www.cs.unm.edu/~soma
> +1 505 872 3150
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.1 (GNU/Linux)
> 
> iEYEARECAAYFAjko2aYACgkQXOpXEmNZ3ScS/ACeLnRaqoTeFUOGnY7cOcITQ6U6
> vbIAn2AelZnF/med87aQtlDXsrZOlm3P
> =ioan
> -----END PGP SIGNATURE-----
> 


Reply via email to