From: Brad Campbell <brad@wasp.net.au>
To: Thorild Selen <thorild@Update.UU.SE>
Cc: linux-ide@vger.kernel.org
Subject: Re: Promise SATAII150 TX4: strange disk ordering
Date: Wed, 31 Aug 2005 18:50:42 +0400 [thread overview]
Message-ID: <4315C3C2.5010007@wasp.net.au> (raw)
In-Reply-To: <17173.49068.154562.170503@Psilocybe.Update.UU.SE>
Thorild Selen wrote:
> Brad Campbell writes:
> > In one machine, I'm using 15 disks on 4 SATA150TX4 cards with
> > 2.6.11.7 and have been now for over 4 months.. it's working
> > perfectly.. not so much as a glitch.
>
> Is this a single-processor system without hyperthreading or the like?
> In that case, it could be that the problem only appears on SMP/HT
> systems, which would be interesting to know.
>
> (I was hit by the bug on a single-processor Xeon system, but with HT
> enabled. I never thought of testing if disabling HT would make the bug
> disappear or not. And now that the system is up and running again, I
> don't really have the possibility to experiment with it.)
>
> If you have partitions on different devices that you can spare and
> feel a little risky, you can try running badblocks -w (WARNING: this
> will destroy any data on the disk/partition!) on several disks
> simultaneously. That appears to be the simplest way to quickly
> reproduce the bug.
These 15 drives are in a RAID-6 that gets thrashed from time to time quite hard.. so there is almost
*always* simultaneous IO to them.. But it is certainly a UP machine (both of them are).
This one has 15 drives RAID-6, the other has 10 drives RAID-5 and 3 drives RAID-5 (two on the
Promise ctrlr and one on the on-board VIA)
No free partitions to spare, sorry.. all md's are pretty full.
However I did all sorts of badblocks/dd/bonnie runs when I was burning in the box and never had an
issue at all.
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2005-08-31 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 3:05 Promise SATAII150 TX4: strange disk ordering Allen Bolderoff
2005-08-26 3:51 ` another question -- " ha haha
2005-08-26 8:46 ` Erik Slagter
2005-08-31 1:40 ` Thorild Selen
2005-08-31 14:15 ` Brad Campbell
2005-08-31 14:33 ` Thorild Selen
2005-08-31 14:50 ` Brad Campbell [this message]
2005-08-31 14:59 ` Ian Oliver
2005-08-31 18:31 ` Tyler
2005-09-01 12:53 ` Ian Oliver
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 22:48 Eyal Lebedinsky
2005-08-30 4:44 ` Jeff Garzik
2005-08-30 10:31 ` Eyal Lebedinsky
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=4315C3C2.5010007@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-ide@vger.kernel.org \
--cc=thorild@Update.UU.SE \
/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).