From: Doug Ledford <dledford@redhat.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Neil Brown <neilb@suse.de>,
Trey Scarborough <treys@locallinux.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: raid 5 mismatch_cnt errors
Date: Wed, 26 May 2010 11:49:52 -0400 [thread overview]
Message-ID: <4BFD4320.6090606@redhat.com> (raw)
In-Reply-To: <4BFD392E.3030906@tmr.com>
[-- Attachment #1: Type: text/plain, Size: 1955 bytes --]
On 05/26/2010 11:07 AM, Bill Davidsen wrote:
> Doug Ledford wrote:
>> On 05/20/2010 06:38 PM, Neil Brown wrote:
>>
>>> On Thu, 20 May 2010 17:29:37 -0500
>>> Trey Scarborough <treys@locallinux.com> wrote:
>>>
>>>
>>>> Neil Brown wrote:
>>>>
>>>>> On Thu, 20 May 2010 12:02:23 -0500
>>>>> Trey Scarborough <treys@locallinux.com> wrote:
>>>>>
>>>>>
>>>>>> I have a raid 5 array with 9 disks and I have a mismatch_cnt that
>>>>>> keeps growing. This is causing file corruption on the underlaying
>>>>>> file systems as well. I can copy a group of 100 100mb files and
>>>>>> then do a md5sum on them and 1-3 will be corrupt. If this is a
>>>>>> drive that is bad is there anyway to run a report on the count per
>>>>>> drive that these mismatches occur. I have run smarttools test and
>>>>>> do not see one drive that stands out to be causing errors. Could
>>>>>> something else be causing these errors?
>>>>>>
>>
>> While a bad drive is certainly a possibility here, this is precisely the
>> type of failure scenario that would make me suspect bad RAM,
>> motherboard, or CPU. So I wouldn't rule those out as possibilities
>> either.
>>
>
> I have the same thought, I would remove half the RAM from the system and
> test again, then swap to the "other" half and repeat. Of course running
> memtest first is a good idea, but I have seen failures which only happen
> on disk access.
Indeed, I've seen lots of failures that only happen with disk access and
not with memory testers. Hence why I have a shell script on my web page
in my sig that uses disk access to test memory.
> If the system is O/C obviously the first step is to cut the speed back...
>
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-26 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 17:02 raid 5 mismatch_cnt errors Trey Scarborough
2010-05-20 21:16 ` Neil Brown
2010-05-20 22:29 ` Trey Scarborough
2010-05-20 22:38 ` Neil Brown
2010-05-21 2:16 ` Doug Ledford
2010-05-21 16:40 ` MRK
2010-05-21 20:57 ` Doug Ledford
2010-05-24 9:34 ` Tim Small
2010-05-25 19:09 ` Robert Hancock
2010-05-26 15:07 ` Bill Davidsen
2010-05-26 15:49 ` Doug Ledford [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-20 16:58 Trey Scarborough
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=4BFD4320.6090606@redhat.com \
--to=dledford@redhat.com \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=treys@locallinux.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 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.