All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Andreas-Sokov <andre.s@j8.com.ru>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: mdadm 2.6.4 : How i can check out current status of reshaping ?
Date: Thu, 07 Feb 2008 16:15:58 -0500	[thread overview]
Message-ID: <47AB750E.2060202@tmr.com> (raw)
In-Reply-To: <119270390.20080206221505@j8.com.ru>

Andreas-Sokov wrote:
> Hello, Neil.
>
> .....
>   
>> Possible you have bad memory, or a bad CPU, or you are overclocking
>> the CPU, or it is getting hot, or something.
>>     
>
> As seems to me all my problems has been started after i have started update MDADM.
> This is server worked normaly (but only not like soft-raid) more 2-3 years.
> Last 6 months it worked as soft-raid. All was normaly, Even I have added successfully
> 4th hdd into raid5 )when it stared was 3 hdd). And then Reshaping have been passed fine.
>
> Yesterday i have did memtest86 onto it server and 10 passes was WITH OUT any errors.
> Temperature of server is about 25 grad celsius.
> No overlocking, all set to default.
>
>   
What did you find when you loaded the module with gdb as Neil suggested? 
If the code in the module doesn't match the code in memory you have a 
hardware error. memtest86 is a useful tool, but it is not a definitive 
test because it doesn't use all CPUs and do i/o at the same time to load 
the memory bus.

> Realy i do not know what to do because off wee nedd grow our storage, and we can not.
> unfortunately, At this moment - Mdadm do not help us in this decision, but very want
> it get.
>   

I would pull out half my memory and retest. If it still fails I would 
swap to the other half of memory. If that didn't show a change I would 
check that the code in the module is what Neil showed in his last 
message (I assume you already have), and then reseat all of the cables, etc.

I agree with Neil:
>> But you clearly have a hardware error.
>>     
>
>   
>> NeilBrown
>>     
>
>
>
>   


-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



  parent reply	other threads:[~2008-02-07 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04  4:08 mdadm 2.6.4 : How i can check out current status of reshaping ? Andreas-Sokov
2008-02-04 22:48 ` Neil Brown
2008-02-05  9:13   ` Re[2]: " Andreas-Sokov
2008-02-05 10:10     ` Neil Brown
2008-02-06 19:15       ` Re[4]: " Andreas-Sokov
2008-02-06 22:26         ` Janek Kozicki
2008-02-07 21:15         ` Bill Davidsen [this message]
2008-02-09  4:40       ` Re[4]: " Andreas-Sokov

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=47AB750E.2060202@tmr.com \
    --to=davidsen@tmr.com \
    --cc=andre.s@j8.com.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.