Bug 164151 - NFS server freeze with kernel-2.6.9-11.EL
Summary: NFS server freeze with kernel-2.6.9-11.EL
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Steve Dickson
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-25 13:08 UTC by Thomas Woerner
Modified: 2012-06-20 13:28 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2012-06-20 13:28:06 UTC

Attachments (Terms of Use)

Description Thomas Woerner 2005-07-25 13:08:46 UTC
Description of problem:
Booting from or installing via NFS does not work with the latest RHEL-4 kernel
on the server. Clients report in install: "server not responding, still trying".

Transfering lots of data to the NFS server freezes NFS after a moment and
results in high load on the server. Only a restart of NFS resolved the problem
for a moment.

Booting kernel-2.6.9-5.0.5.EL instead resolves the problem completely.

The bug is similar to #152102, but the server is RHEL-4 (i686) and the clients
are FC-3 (i686 and x86_64) or FC-4 (i686 and x86_64).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Setup NFS server with kernel-2.6.9-11.EL.
2. Transfer data to or from the server.
3. Transfer aborted.
Actual results:
NFS service freezes.

Expected results:
No freeze.

Additional info:

Comment 1 Steve Dickson 2005-07-27 12:12:44 UTC
Is there any type of error message on the server as
to why it stop sending? Posting an system trace
(i.e. echo t > /proc/sysrq-trigger) of the server might

Comment 12 Jiri Pallich 2012-06-20 13:28:06 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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