Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 27 Jul 2001 03:53:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 27 Jul 2001 03:53:32 -0400 Received: from hood.tvd.be ([195.162.196.21]:64328 "EHLO hood.tvd.be") by vger.kernel.org with ESMTP id ; Fri, 27 Jul 2001 03:53:15 -0400 Date: Fri, 27 Jul 2001 09:49:10 +0200 (CEST) From: Geert Uytterhoeven To: =?ISO-8859-1?Q?G=E9rard_Roudier?= cc: Linux Kernel Development Subject: Re: SCSI Tape corruption - update In-Reply-To: <20010720222746.J3846-100000@gerard> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Original-Recipient: rfc822;linux-kernel-outgoing On Fri, 20 Jul 2001, G?rard Roudier wrote: > On Fri, 20 Jul 2001, Geert Uytterhoeven wrote: > > The problem is indeed introduced by the changes to the Sym53c8xx in 2.2.18-pre1. > > I managed to find some intermediate versions in the 2.3.x series, and here are the > > results: > > - sym53c8xx-1.3g (from BK linuxppc_2_2): OK > > - sym53c8xx-1.5e: crash in SCSI interrupt during driver init > > - sym53c8xx-1.5f: lock up during driver init > > - sym53c8xx-1.5g: random 32-byte error bursts when writing to tape > > That's an interesting result. But 1.5g - 1.3g diffs are probably very > large. Patches available from ftp.tux.org should allow to resurrect > driver versions 1.4, 1.5, 1.5a, 1.5b, 1.5c, 1.5d. > > ftp://ftp.tux.org/pub/roudier/drivers/linux/sym53c8xx/README > > You may, for example, apply incremental patches that address kernel 2.2.5 > to a fresh kernel 2.2.5 tree and extract driver files accordingly. Thanks! With some small modifications, I made 1.5a to work fine. No error burst. So the problem is introduced between 1.5a and 1.5g. Unfortunately my DDS-1 drive seems to have died for real after this test :-( I don't know yet whether I will replace it with a new tape drive or with a CD-RW. Which means I may never find out which change caused the problem... I assume other people suffer from the same error burst problem, but they never notice until they really want to restore data. Me myself only notived it by accident, too. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/