Hi,
MisterE wrote:
Tonight i will try the Asus motherboard with 1 drive and much I/O. And
i will create a new array which takes 7 hours. But how often/hours do
you need to try something to prove it does not fail :P
On one box I had problems with the SATA300 TX4 using 2.6.21 through
2.6.22 (different versions). I have 4x500GB Seagate ES SATA drives
connected. The system would run fine, but when put to a stress - i.e.
loaded on all sata ports one or two ports would fail - one after the
other. I have _always_ been able to make it fail doing:
dd if=/dev/sda of=/dev/null bs=1M &
dd if=/dev/sdb of=/dev/null bs=1M &
dd if=/dev/sdc of=/dev/null bs=1M &
dd if=/dev/sdd of=/dev/null bs=1M &
The ports would freeze before running long - e.g. in less than an hour.
This can be done without even starting the array (mdadm). Therefore no
data corruption will happen.
The above issue was fixed by updating to vanilla 2.6.23.1.
Until then I have been running with 2.6.21-rc2 with a Mikael Petterson
patch to force the SATA to 1.5Gbps (this could possibly be accomplished
by jumpers on the drives as well - but I didn't try that).
I have another system (Dell PE1800 = different from the above) running
24x7 using vanilla linux 2.6.19.5. This system has been running without
hickups for more than a year (current uptime 135 days).
Hope this helps,
Best regards,
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
