Bug 172465
Summary: | NFS share hangs | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Glen <glen> | ||||
Component: | kernel | Assignee: | Steve Dickson <steved> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4.0 | CC: | dshaks, jbaron | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-06-20 16:12:50 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: | |||||||
Attachments: |
|
Description
Glen
2005-11-04 21:22:58 UTC
Created attachment 120742 [details]
tcpdump on the nfs server
Would it be possible to post a bzip2 binary tethereal network trace (i.e. tethereal -w /tmp/data.pcap host <server>) and then post a system backtrace on the server by doing an "echo t > /proc/sysrq-trigger". Note: the backtrace will be in /var/log/messages.... But looking at the tcpdump you have posted, it really appears the server is just going away... Note the last 5 nfs messages are NULL which tells me the client is trying to "ping" the server to see if its still there... Actually, I had two different RAID units attached to this one server. When I split them up so they were each on a seperate server my problems went away. However, I have the exact same setup going on a Fedora Core 4 machine and it has been perfectly fine. Seems to me that something is seriously wrong with I/O on RHEL 4. In fact, I did a few benchmarks with dbench on both OS's and FC4 gets me around double the performance on the exact same hardware. 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. |