On Thu, 26 Sep 2002, Muli Ben-Yehuda wrote: > Now, could you explain furtherm, if the setup is already working, why > are you considering upgrading the kernel? Are there specific bottle > necks that you're running into?
The overview I gave was to explain a pattern of behaviour we have with really stressed servers here. The service I experienced problem with is different, and since it's part of a non-disclosure agreement we have, I cannot specify more. What I can say it that it's a system running an application which has to be able to deal with ~100Mbit/s full duplex (50 in 50 out). The system also does ALOT of IO, the system is dual CPU, runs a database that works pretty hard, and runs 1GB of memory that are ~80% used. The problems started after upgrading to 1GB memory, I assume because the pattern of operation changed (less swapping). The problem occurs in kjournaled in a reproductivable manner, but I do not think kjournald is the problem, but that something else gets stuck, which causes kjournald to fail, and then the system stops. --Ariel -- Ariel Biener e-mail: [EMAIL PROTECTED] PGP(6.5.8) public key http://www.tau.ac.il/~ariel/pgp.html ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
