Bug 809816
Summary: | [glusterfs-3.3.0qa33]: nfs client hung because of some rpc errors in nfs-server | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Raghavendra Bhat <rabhat> |
Component: | nfs | Assignee: | Vivek Agarwal <vagarwal> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | amarts, gluster-bugs, sankarshan, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-24 17:14:30 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Raghavendra Bhat
2012-04-04 12:54:32 UTC
[2012-04-03 14:04:48.389913] W [client3_1-fops.c:2173:client3_1_lk_cbk] 0-mirror-client-1: remote operation failed: Transport endpoint is not connected Same is the case with 0-mirror-client-0 and 0-mirror-client-2 Can you check why it got disconnected? That is the reason nfs clients have hung. There is an NLM related log: [2012-04-03 14:04:48.934015] E [nlm4.c:1624:nlm4_unlock_resume] 0-nfs-NLM: fd_lookup_uint64() returned NULL There is a separate bug for this (802885), it does not cause the client to hang though. Raghavendra, moving it to on_qa, you can close this if you think it is not a bug. rabhat didn't see the issue in recent time, moving it to ON_QA |