|To:||Robert Hancock <hancockr@xxxxxxx>|
|Subject:||Re: Lots of con-current I/O = resets SATA link? (18.104.22.168)|
|From:||Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>|
|Date:||Sat, 5 Jul 2008 19:24:52 -0400 (EDT)|
|Cc:||linux-kernel@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx, linux-ide@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, Alan Piszcz <ap@xxxxxxxxxxxxx>|
|References:||<fa.u8J+BqAcxU1mg8ob9pMBJaAHBPo@xxxxxxxxxx> <486FBFAB.5050303@xxxxxxx> <alpine.DEB.1.10.0807051527210.8002@xxxxxxxxxxxxxxxx> <48700228.7060904@xxxxxxx>|
|User-agent:||Alpine 1.10 (DEB 962 2008-03-14)|
On Sat, 5 Jul 2008, Robert Hancock wrote:
Justin Piszcz wrote:Can you post your dmesg from bootup with the controller/drive detection?So you've got 6 drives in the machine. Intel chipsets normally seem pretty robust with AHCI.Are you certain that your machine has enough power to run all those drives properly? We've seen in a number of cases that power fluctuations or noise can cause these kinds of errors.
I have a 650watt PSU (nice antec one) and the power draw of the box is ~148watts w/ veliciraptors, ~250 when fully load all 4 cores + all 12 disks writing. I have turned off the irqbalance daemon and I am going to see if the problem re-occurs.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Lots of con-current I/O = resets SATA link? (22.214.171.124), Robert Hancock|
|Next by Date:||Re: Xfs Access to block zero exception and system crash, Dave Chinner|
|Previous by Thread:||Re: Lots of con-current I/O = resets SATA link? (126.96.36.199), Robert Hancock|
|Next by Thread:||Re: Lots of con-current I/O = resets SATA link? (188.8.131.52), Justin Piszcz|
|Indexes:||[Date] [Thread] [Top] [All Lists]|