Just for the logs:
Finally I found the failure. It was the Raid-Controller (3ware).
It seems that the 64-bit Kernel has troubles with this Device.
I tried different mainboards with different controllers and the failure
was reproducable with a 3ware-8000. I tried two of them.
Cheers,
Christoph
Mike,
I had the same failures without network.
And it is a onboard-controller :-)
Christoph
>
> Christoph,
> Have you tried replacing the network card with the one from the
> working machine? Network cards can cause problems under high load but will
> appear fine otherwise
At 09:42 AM 5/18/2007, you wrote:
Hi,
It seems to be the Hardware somehow. I tested on another Machine with same
OS,
and everything seems to run now. I am using the same Memory so this is not
the
problem. Both Machines have hardware raid. The only thing left is the
mainboard. Vey ugly.
Hi,
It seems to be the Hardware somehow. I tested on another Machine with same OS,
and everything seems to run now. I am using the same Memory so this is not the
problem. Both Machines have hardware raid. The only thing left is the
mainboard. Vey ugly.
Cheers,
Christoph
On Friday 18
Christoph,
I don't know if this helps or not, but I had a similar problem
a few years back on a Windows machine. Memory kept getting corrupted and I
traced the problem to Intel Accelerator that I had running. Intel only
admitted to the problem with their software months later. My ad
Hi everybody,
On Friday 18 May 2007 14:50:55 Brent Baisley wrote:
> You may be running into file system file size "limits". You would need to
> make sure the file system you are using is set to handle files larger than
> 4GB, in addition, you need to check that the account mysqld us running
> unde
You may be running into file system file size "limits". You would need to make sure the file system you are using is set to handle
files larger than 4GB, in addition, you need to check that the account mysqld us running under is allowed to create files larger
than 4GB. Just because the OS and fil
