From: "Kasimir Müller" <kjm@kasimir-mueller.de>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
christian.kuehn@hamburg.de
Subject: Re: [Fwd: Re: libata , Silicon Image 3124]
Date: Wed, 09 Jan 2008 18:31:50 +0100 [thread overview]
Message-ID: <47850506.4040806@kasimir-mueller.de> (raw)
In-Reply-To: <4782F243.6060606@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
Am 08.01.2008 04:47, Tejun Heo schrieb:
> Kasimir Müller wrote:
>
>> Hi Tejun,
>>
>> Old communication appended below.
>>
>> I wish you a Happy Xmas and a successful New Year.
>>
>> I spent some time during Christmas to further investigate the problem. I
>> bought a new 500GB disk and put all data on this disk.
>> This is also contineously watched by nagios and cacti
>> Then
>> 1.) All 5 disks in the external case connected via Portmapper and sil24
>> card have excellent health-status with smartd.
>> 2.) I get no(!!!!) errors at all if I use the disks as single drives or
>> with lvm. I verified this by copying large amounts of data (100-200GB)
>> with rsync , cp-av and running bonnie++ single and simultaneously
>> to various combinations of drives.
>> 3.) I get the errors as soon as I use raid. Same errors with raid0 (2
>> disks), 1 (2 disks), 5 (3 disks) in any combination of the drives
>> 4.) The errors appear usually first during mkfs (same with ext3 and
>> reiserfs) and than
>> after writing about 10-50 GB to the raid, and repeat then at 5 to
>> 10 minute intervals according the disk activity.
>> 5.) I used Kernel 2.6.23.1 with Your latest patch: same result
>> 6.) I used kernel 2.6.24 patch rc-6 : same result
>> 7.) during the tests I marked all files with md5-sums: No data
>> corruption (!!!), so maybe I can live with it.
>>
>
> Please apply the attached patch on top of 2.6.24-rc6 and report whether
> anything changes.
>
> Thanks.
>
>
Hi Tejun,
thanks very much again for your time and readiness to help.
I applied the patch as you proposed without problem.
I attach the kernel logs of the past few days. As far as I can see, with
the patched kernel errors appear only under heavy load .
If you want, I could provide a (temporary) ssh-login to my machine.
Maybe it would make it easier for you to debug the problem.
If you want to use it, I need your public ssh-certificate and your
login-name and I would send the login-details to you.
Thanks again,
yours Kasimir.
[-- Attachment #2: kernel.log.gz --]
[-- Type: application/x-gzip, Size: 99041 bytes --]
next prev parent reply other threads:[~2008-01-09 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <473A5B03.2020808@gmail.com>
2008-01-06 10:55 ` [Fwd: Re: libata , Silicon Image 3124] Kasimir Müller
2008-01-08 3:47 ` Tejun Heo
2008-01-09 17:31 ` Kasimir Müller [this message]
2008-01-10 4:08 ` Tejun Heo
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=47850506.4040806@kasimir-mueller.de \
--to=kjm@kasimir-mueller.de \
--cc=christian.kuehn@hamburg.de \
--cc=htejun@gmail.com \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.