From: "Gérard Roudier" <groudier@free.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Gérard Roudier" <groudier@club-internet.fr>,
"Linux Kernel Development" <linux-kernel@vger.kernel.org>
Subject: Re: SCSI Tape corruption - update
Date: Fri, 27 Jul 2001 22:41:31 +0200 (CEST) [thread overview]
Message-ID: <20010727221848.F1554-100000@gerard> (raw)
In-Reply-To: <Pine.LNX.4.05.10107270943580.620-100000@callisto.of.borg>
On Fri, 27 Jul 2001, Geert Uytterhoeven wrote:
> 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.
Fine! But diffs between 1.5a and 1.5g are still large. :(
Results with 1.5c would have divided the diffs by about 2. :(
> 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 expect the problem to pong again to me. For now, I plan to look into the
1.5g-1.5a source diffs and inspect each change. But as I will be in
vacation for the next two weeks, I will not be able to work on this
problem immediately.
> 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.
Thanks for your testings and results.
Regards,
Gérard.
next prev parent reply other threads:[~2001-07-27 20:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 14:46 Lorenzo Marcantonio
2001-05-07 15:39 ` Rob Turk
2001-05-07 19:15 ` Lorenzo Marcantonio
2001-05-08 7:12 ` Geert Uytterhoeven
2001-05-08 8:16 ` Lorenzo Marcantonio
2001-06-21 9:33 ` Geert Uytterhoeven
2001-07-08 13:33 ` Geert Uytterhoeven
2001-07-08 19:01 ` Gérard Roudier
2001-07-20 17:08 ` Geert Uytterhoeven
2001-07-20 21:02 ` Gérard Roudier
2001-07-27 7:49 ` Geert Uytterhoeven
2001-07-27 20:41 ` Gérard Roudier [this message]
2001-07-28 9:57 ` Geert Uytterhoeven
2001-11-01 19:09 ` Geert Uytterhoeven
2001-11-02 7:04 ` Gérard Roudier
2001-11-07 15:26 ` Geert Uytterhoeven
2001-12-05 15:32 ` Geert Uytterhoeven
2001-12-28 20:36 ` Sym53c8xx tape corruption squashed! (was: Re: SCSI Tape corruption - update) Geert Uytterhoeven
2001-12-29 0:57 ` Gérard Roudier
2001-12-29 10:49 ` Geert Uytterhoeven
2001-12-29 13:23 ` Geert Uytterhoeven
2001-12-29 18:39 ` Gérard Roudier
2001-12-29 21:28 ` Geert Uytterhoeven
2001-12-30 0:00 ` Gérard Roudier
-- strict thread matches above, loose matches on Subject: below --
2001-05-09 8:33 SCSI Tape corruption - update Ishikawa
2001-04-12 8:43 SCSI Tape Corruption " lomarcan
2001-04-12 12:43 ` Bob_Tracy
2001-04-12 15:43 ` Gérard Roudier
2001-04-13 7:02 ` Geert Uytterhoeven
2001-04-13 7:13 ` Geert Uytterhoeven
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=20010727221848.F1554-100000@gerard \
--to=groudier@free.fr \
--cc=geert@linux-m68k.org \
--cc=groudier@club-internet.fr \
--cc=linux-kernel@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®