Bug 103070 - hangs when running lagre date even use rsync, cp , tar
Summary: hangs when running lagre date even use rsync, cp , tar
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel
Version: 2.1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Larry Woodman
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-26 11:50 UTC by MF Lee
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2007-10-19 19:24:14 UTC


Attachments (Terms of Use)

Description MF Lee 2003-08-26 11:50:11 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0

Description of problem:
ENOMEM in journal_alloc_journal_head, retrying.
ENOMEM in journal_get_undo_access_Rsmp_767cdac6, retrying.
ENOMEM in get_transaction, retrying.
ENOMEM in journal_alloc_journal_head, retrying.
ENOMEM in journal_get_undo_access_Rsmp_767cdac6, retrying.
ENOMEM in journal_alloc_journal_head, retrying.
ENOMEM in journal_alloc_journal_head, retrying.
ENOMEM in get_transaction, retrying.
ENOMEM in journal_get_undo_access_Rsmp_767cdac6, retrying.
ENOMEM in get_transaction, retrying.
ENOMEM in get_transaction, retrying.

Version-Release number of selected component (if applicable):
kernel-2.4.9-e.16enterprise

How reproducible:
Sometimes

Steps to Reproduce:
Server Info :
8xCPU
16GB Memory

patch update:
gcc 2.96-118
glibc 2.2.4-31
snmp 4.2.5-7



Additional info:

Comment 1 Larry Woodman 2004-11-29 20:49:30 UTC
The latest AS2.1 kernel has fixes to better defragment memory and
launder/reclaim lowmem.  Please try the latest AS2.1 kernel and verify
that this problem has been fixed.

Larry Woodman


Comment 2 RHEL Product and Program Management 2007-10-19 19:24:14 UTC
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.


Note You need to log in before you can comment on or make changes to this bug.