From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Thorild Selen <thorild@Update.UU.SE>
Cc: linux-ide@vger.kernel.org, linux-raid list <linux-raid@vger.kernel.org>
Subject: Re: Promise SATAII150 TX4 or raidreconf broken
Date: Mon, 12 Sep 2005 01:50:56 +1000 [thread overview]
Message-ID: <43245260.6030907@eyal.emu.id.au> (raw)
In-Reply-To: <x3kfysdq846.fsf@Psilocybe.Update.UU.SE>
Thorild Selen wrote:
> If you search a bit in the linux-ide and linux-kernel mailing list
> archives, you will find that several people before have had problems
> with SATA150-TX4 and SATAII150-TX4 (see for example posts by Jim
> Ramsay, Joerg Sommrey and me).
Following up on this information I did more testing.
I verified that creating a 2-disk raid-5 and extending it to 3 disks
always works. 3-disk to 4-disk end up corrupted.
BTW I had to change the check in raidreconf for a minimum of raid5
disks from 3 to 2. It worked just fine.
I then moved the first two disks to the motherboard (sd[cd] left on
the TX4). The situation remained the same (but I did get better
performance).
I am now less inclined to blame the TX4 and lean more towards
raidreconf.
I need to create a final test where I hit the disks concurrently
without raidreconf to see how they fair...
I did some tests and so far failed to provoke any i/o error.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
attach .zip as .dat
next prev parent reply other threads:[~2005-09-11 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <430E4AB0.2060600@eyal.emu.id.au>
[not found] ` <4313E433.1080602@pobox.com>
2005-09-10 8:23 ` Promise SATAII150 TX4 or raidreconf broken Eyal Lebedinsky
[not found] ` <43223709.8090002@eyal.emu.id.au>
[not found] ` <x3kfysdq846.fsf@Psilocybe.Update.UU.SE>
2005-09-11 15:50 ` Eyal Lebedinsky [this message]
2005-09-12 22:50 ` Promise SATAII150 TX4 or raidreconf broken - answer Eyal Lebedinsky
2005-09-18 8:56 ` Tyler
2005-09-18 9:56 ` Eyal Lebedinsky
2005-09-10 12:55 Promise SATAII150 TX4 or raidreconf broken Henrik Holst
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=43245260.6030907@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@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).