Date: Thu, 31 Mar 2005 08:29:13 -0500 From: Vivek Khera <vivek@khera.org> To: freebsd-amd64@freebsd.org Subject: Re: Tyan k8sr lockups Message-ID: <eac50ac5764b01c4683c7bcdf006551b@khera.org> In-Reply-To: <424B8B73.8040100@dmv.com> References: <f0111a98c01333b3c306c81d10294de4@khera.org> <Pine.SOC.4.61.0503300229560.3181@tea.blinkenlights.nl> <97964ce32490a368d64fa9b3500a8ba6@khera.org> <424B8B73.8040100@dmv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 31, 2005, at 12:32 AM, Sven Willenberger wrote: > For a piece of anecdotal evidence we are running a dual opteron k8s > pro with 8GB of RAM and the 320-2x Megaraid controller (which controls > all the harddrives) Except for a problem with fxp (which I haven't > gone back to reinvestigate but rather just used the Broadcom gigE > instead) the system so far has run fairly stable (running Postgres > under a medium load at the moment). We had one issue of a > "spontaneous" reboot that left no indication of what happened in > messages; this box is still in our testing area so it is possible that > it was the result of a power[cord] issue. This is running > 5.4-PRERELEASE from 17 March. Also, we disabled the onboard adaptec > controllers in the bios (as we don't use them). If you can try under very heavy network + disk load, I'd appreciate it. I'm usually locking up and/or having ethernet timeouts when the postgres DB is being dumped and some large reports are running. The DB is about 51Gb on disk, and the dump is going across the network to another machine. The ethernet is connected to a gigE switch. Throw in a postgres VACUUM in there and I'm almost guaranteed a lockup of some sort. I'm not sure the difference of the K8SR and K8S Pro, so it may still be something with the K8SR for all I know. Thanks for responding.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eac50ac5764b01c4683c7bcdf006551b>