From: Michael Evans <mjevans1983@gmail.com>
To: Maarten <maarten@ultratux.net>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: woes with... mdadm ?
Date: Thu, 28 Jan 2010 20:58:32 -0800 [thread overview]
Message-ID: <4877c76c1001282058s6931a9e2tbe0da4ef67428680@mail.gmail.com> (raw)
In-Reply-To: <4B608645.8030102@ultratux.net>
The point about the CRC being only slightly off is that usually a
change in the data-set produces a much larger variation. It could be
only a single bit or two near the end.
The point about stress-testing the CPU/RAM is to validate that those
are known clean in as close to a high-temp real load environment as
possible.
That would then point to corruption on the cables or drives. Which
you can diagnose more easily individually instead of as part of an
array.
next prev parent reply other threads:[~2010-01-29 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 22:27 woes with... mdadm ? Maarten
2010-01-27 4:14 ` Michael Evans
2010-01-27 18:30 ` Maarten
2010-01-29 4:58 ` Michael Evans [this message]
2010-01-29 10:42 ` Neil Brown
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=4877c76c1001282058s6931a9e2tbe0da4ef67428680@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=maarten@ultratux.net \
/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).