From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Lorenzo Marcantonio <lomarcan@tin.it>
Cc: Rob Turk <r.turk@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: SCSI Tape corruption - update
Date: Thu, 21 Jun 2001 11:33:40 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.05.10106211122180.1260-100000@callisto.of.borg> (raw)
In-Reply-To: <Pine.LNX.4.05.10105080904010.24912-100000@callisto.of.borg>
On Tue, 8 May 2001, Geert Uytterhoeven wrote:
> On Mon, 7 May 2001, Lorenzo Marcantonio wrote:
> > On Mon, 7 May 2001, Rob Turk wrote:
> > > Have you ruled out hardware failures? There's been a few isolated reports
> >
> > That tape drive (Sony SDT-9000, less than 2 years of service) works
> > perfectly on Windows NT (were it was before) and even on Linux 2.2
> >
> > Also the cartridge was brand new.
>
> In the mean time I down/upgraded to 2.2.17 on my PPC box (CHRP LongTrail,
> Sym53c875, HP C5136A DDS1) and I can confirm that the problem does not happen
> under 2.2.17 neither.
>
> My experiences:
> - reading works fine, writing doesn't
> - 2.2.x works fine, 2.4.x doesn't (at least since 2.4.0-test1-ac10)
> - hardware compression doesn't matter
> - I have a sym53c875, Lorenzo has an Adaptec, so most likely it's not a
> SCSI hardware driver bug
> - I have a PPC, Lorenzo doesn't, so it's not CPU-specific
> - corruption is always a block of 32 bytes being replaced by 32 bytes from
> the previous tape block (depending on block size!) (approx. 6 errors per
> 256 MB)
>
> Lorenzo, can you please investigate the exact nature of the corruption on your
> system?
> - How many successive bytes are corrupted?
> - Where do the corrupted data come from?
Yesterday I noticed the same corruption under 2.2.19 (yes, I run amverify after
backing up my system now, so it detects corruption through the gzip CRCs).
I'll do some more tests (when I find time) to get a higher statistical
certainty that it really doesn't happen under earlier 2.2.x kernels.
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
next prev parent reply other threads:[~2001-06-21 9:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 14:46 SCSI Tape corruption - update 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 [this message]
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
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=Pine.LNX.4.05.10106211122180.1260-100000@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lomarcan@tin.it \
--cc=r.turk@chello.nl \
/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;
as well as URLs for NNTP newsgroup(s).