From: rct@gherkin.sa.wlk.com (Bob_Tracy)
To: lomarcan@tin.it
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: SCSI Tape Corruption - update
Date: Thu, 12 Apr 2001 07:43:43 -0500 (CDT) [thread overview]
Message-ID: <m14ngRr-0005khC@gherkin.sa.wlk.com> (raw)
In-Reply-To: <20010412084318.LESP2878.fep02-svc.tin.it@fep41-svc.tin.it> "from lomarcan@tin.it at Apr 12, 2001 10:43:18 am"
lomarcan@tin.it wrote:
> It seems that the tape is written incorrectly. I wrote some large file
> (300MB)
> and read it back four time. The read copies are all the same. They differ
> from the original only in 32 consecutive bytes (the replaced values SEEM
> random). Of course, 32 bytes in 300MB tar.gz files are TOO MUCH to be
> accepted :)
Several years ago I ran into a problem with similar symptoms on an old
Adaptec AHA-154X controller. Files (and most certainly "file systems"
if I had persisted) on my hard disk were getting corrupted in random
places with constant length strings of garbage. This turned out to be
an inappropriate setting for the AHA1542_SCATTER constant: it *was* 16,
and setting it to 8 fixed my problem. I'd look for a similar "#define"
in the header file for your SCSI device driver and try cutting the value
by half. Why "half"? No justification other than it worked for me, and
it's a power-of-two kind of thing that hardware seems to like :-).
--Bob
next prev parent reply other threads:[~2001-04-12 12:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 8:43 lomarcan
2001-04-12 12:43 ` Bob_Tracy [this message]
2001-04-12 15:43 ` Gérard Roudier
2001-04-12 20:06 ` SCSI Tape Corruption - update 2 Lorenzo Marcantonio
2001-04-13 7:02 ` SCSI Tape Corruption - update Geert Uytterhoeven
2001-04-13 7:13 ` Geert Uytterhoeven
2001-05-07 14:46 SCSI Tape corruption " 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
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-05-09 8:33 Ishikawa
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=m14ngRr-0005khC@gherkin.sa.wlk.com \
--to=rct@gherkin.sa.wlk.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lomarcan@tin.it \
/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®