Bug 50711
Summary: | mm problems under heavy load | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Renato <renato> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | cbaudry, kalaklanar |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
URL: | not specific | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Renato
2001-08-02 14:34:14 UTC
I also tried with the latest raw hide kernel - 2.4.6-3.1smp, but with this one I have a kernel panic after a couple of hours. I have the same error using the 2.4.3-12enterprise kernel on a Dell PowerEdge 6400 with the megaraid driver for the RAID controller. It has 2GB of RAM. This occurrs under any heavy load and effectively kills the server. This is a newly "upgraded" server (formatted RH 6.2 and put on a new install of 7.1). This occurs when I issue an rsync command to get the data from it's partner in a failover cluster rsync -ave ssh --exclude="/.../" 192.168.1.1::home/ /home/ It then begins transferring 93GB on the rsync, but it is so drained as to be unusable during this time. The "tigger" message as it has been nicknamed than begins to come up on the console. (Glad I don't do this often...) Simply killing the rsync process removes the errors and the performance is back to normal. This did not occur in the 2.2.19 kernel used previous to the 7.1 install. Research gives this discussion: http://lwn.net/2001/0607/kernel.php3 but the success of this patch is not later discussed. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |