Bug 612101 - livelock when using nfs4 on 2.6.18-194.3.1.el5
Summary: livelock when using nfs4 on 2.6.18-194.3.1.el5
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.5
Hardware: All
OS: Linux
low
urgent
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-07 10:22 UTC by olaf
Modified: 2018-03-19 12:13 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:18:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
part of /var/log/messages (35.09 KB, text/plain)
2010-07-07 10:22 UTC, olaf
no flags Details

Description olaf 2010-07-07 10:22:16 UTC
Created attachment 430020 [details]
part of /var/log/messages

OS: CentOS 5.5 x86_64

Because of slow write performance of nfs v3 I tried to play a little with nfs v4.
The server worked previously fine using nfs v3 mounts.
I tried to copy 4,8,16 GB files on the nfs server.
For several transfers it worked, and next the nfsd processes and kjournald got blocked.
I attache /var/log/messages.
The system was working but any access to affected filesystem caused the accessing process to block.
To get it to normal state again a reset was necessary (reboot hung of course).

The filesystem that was exported was stacked as below:
RAID1->LUKS->LVM->Ext3.

Also reported in CentOS bugzilla:

http://bugs.centos.org/view.php?id=4337

Comment 1 RHEL Program Management 2014-03-07 13:44:09 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 2 RHEL Program Management 2014-06-02 13:18:31 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).


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