From: Tejun Heo <htejun@gmail.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Jens Axboe <axboe@suse.de>, linux@horizon.com, linux-ide@vger.kernel.org
Subject: Re: sata_sil24 corruption details
Date: Sun, 13 Nov 2005 19:19:36 +0900 [thread overview]
Message-ID: <43771338.6010000@gmail.com> (raw)
In-Reply-To: <43755A78.3040005@gmail.com>
Tejun Heo wrote:
> Greg Freemyer wrote:
>>
>> Tejun,
>>
>> Success report:
>>
>> I did a 80 GB test copy with 2.6.14.1 and a Maxtor 80GB SATA drive and
>> a 3112A. I had 3 drives connected to my server, one PATA for booting,
>> one PATA for to hold the source data, and the SATA drive. Let me know
>> if you want want details about the setup.
>>
>> I found no corruption. Given that my error rate was very low it is
>> possible that the corruption simply did not happen, but for now I'm
>> assuming my earlier issues were either a disk problem or a kernel
>> issue that was resolved by the latest kernel.
>>
>> I'm going to continue to test this setup. I'll report any problems I
>> find.
>>
>
> Hi, Greg.
>
> I also have been continuing corruption test on 3112 during last two
> days. It's being performed on 100GB partition of a 160GB harddisk
> (samsung hd160jj). Nine passes of 'badblocks -t random -v -w /dev/sdb2'
> succeeded without any problem. To replicate your test, I created a 4GB
> random file by dd'ing from /dev/urandom in a separate IDE disk and
> copied it to the partition 24times (24 different files of course), then
> I md5sum'd all copied files twice. This test succeeded five times
> without any problem, and it's in the sixth run now.
>
> Above badblocks and file copy tests amount to about 1.4TB of writes and
> 1.9TB of reads without any data corruption.
>
> Let me know how your test turns out.
>
The 4G file test has been running through last two days and it finished
thirteen more runs without any hickup. So, my 3112 + hd160jj
combination finshed 9 runs of 'badblocks -t random -v -w' and 22 runs of
4G file copy & verify twice test. That's > 3TB of writes and > 5TB of
reads without any error.
I guess my setup doesn't have the problem you used to experience. How's
your testing going?
--
tejun
next prev parent reply other threads:[~2005-11-13 10:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 9:59 sata_sil24 corruption details linux
2005-11-07 16:15 ` Greg Freemyer
2005-11-10 7:17 ` linux
2005-11-10 9:01 ` Tejun Heo
2005-11-10 14:15 ` Greg Freemyer
2005-11-10 14:41 ` Tejun Heo
2005-11-10 15:26 ` linux
2005-11-10 17:32 ` Tejun Heo
2005-11-10 20:34 ` Greg Freemyer
2005-11-12 0:49 ` Greg Freemyer
2005-11-12 2:59 ` Tejun Heo
2005-11-13 10:19 ` Tejun Heo [this message]
2005-11-14 23:30 ` Greg Freemyer
2005-11-18 2:23 ` sata_sil24 corruption FIXED by motherboard swap linux
2005-11-18 19:36 ` sata_sil24 test support linux
2005-11-22 0:23 ` linux
2005-11-22 1:52 ` Tejun Heo
2005-11-11 2:16 ` sata_sil24 corruption details linux
2005-11-13 6:11 ` linux
2005-11-10 17:39 ` Jens Axboe
2005-11-10 20:27 ` Edward Falk
-- strict thread matches above, loose matches on Subject: below --
2005-11-07 16:05 SMALL, Timothy
2005-11-15 9:30 SMALL, Timothy
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=43771338.6010000@gmail.com \
--to=htejun@gmail.com \
--cc=axboe@suse.de \
--cc=greg.freemyer@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux@horizon.com \
/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).