From: Norman Schmidt <schmidt@naa.net>
To: linux-raid@vger.kernel.org
Subject: Re: libata badness
Date: Tue, 05 Oct 2004 07:27:28 +0200 [thread overview]
Message-ID: <416230C0.3060509@naa.net> (raw)
In-Reply-To: <416227E1.8020306@wasp.net.au>
Brad Campbell schrieb:
> For future reference, I have had errors show up after 24-36 hours of
> memtest86. I usually find that if it passes 48 hours of testing then
> things are looking pretty reliable. A couple of hours is usually too
> small a sample to rely on.
>
> Brad
I can confirm that finding. What I usually do in addition to that is to
start enough burnmmx/burnp6 processes to make the system swap, run
bonnie at the same time ant let the machine chew on this for two days.
Ich none of the processes stops, it can go into production.
However, I now had problems with a faulty power supply (capacitors) the
second time - symptoms was erratic behaviour, the software raid fell
apart quite often (because some of the disks sometimes went down) and so
on. One learns all the time.
Bye Norman.
--
Norman Schmidt Institut fuer Physikal. u. Theoret. Chemie
Dipl.-Chem. Univ. Friedrich-Alexander-Universitaet
schmidt@naa.net Erlangen-Nuernberg
IT-Systembetreuer Physikalische Chemie
prev parent reply other threads:[~2004-10-05 5:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 12:12 libata badness William Knop
2004-10-04 13:59 ` Jon Lewis
2004-10-04 15:50 ` William Knop
2004-10-04 16:06 ` Mark Lord
2004-10-04 16:24 ` William Knop
2004-10-04 16:30 ` Jeff Garzik
2004-10-04 16:09 ` Jon Lewis
2004-10-04 16:34 ` William Knop
2004-10-04 16:30 ` Jeff Garzik
2004-10-04 16:55 ` William Knop
2004-10-04 17:42 ` William Knop
2004-10-04 17:50 ` Jim Paris
2004-10-04 18:03 ` William Knop
2004-10-04 18:01 ` Jeff Garzik
2004-10-04 22:47 ` Neil Brown
2004-10-05 3:11 ` William Knop
2004-10-05 4:49 ` Brad Campbell
2004-10-05 5:27 ` Norman Schmidt [this message]
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=416230C0.3060509@naa.net \
--to=schmidt@naa.net \
--cc=linux-raid@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 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).