Bug 916406
| Summary: | NLM failure against Solaris NFS client | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Anand Avati <aavati> | ||||
| Component: | nfs | Assignee: | bugs <bugs> | ||||
| Status: | CLOSED EOL | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | mainline | CC: | bugs, chrisw, gluster-bugs, ndevos, nsathyan, vagarwal | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-10-22 15:46:38 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: | |||||||
| Attachments: |
|
||||||
These errors look related to the UNLOCK procedures returning NLM_DENIED. $ TZ=UTC tshark -ta -r nlm-solaris-einval.pcap nlm.stat == NLM_DENIED ...removed NLM_DENIED replies from before the log in comment #0 487 01:51:01.514887 172.16.50.183 2045 172.16.1.86 1015 NLM 106 V4 UNLOCK Reply (Call In 486) NLM_DENIED 504 01:51:01.533409 172.16.50.183 2045 172.16.1.86 1015 NLM 106 V4 UNLOCK Reply (Call In 503) NLM_DENIED 6549 01:51:06.655803 172.16.50.183 2045 172.16.1.86 1015 NLM 106 V4 UNLOCK Reply (Call In 6548) NLM_DENIED 6601 01:51:06.758019 172.16.50.183 2045 172.16.1.86 1015 NLM 106 V4 UNLOCK Reply (Call In 6600) NLM_DENIED 6603 01:51:06.759217 172.16.50.183 2045 172.16.1.86 1015 NLM 106 V4 UNLOCK Reply (Call In 6602) NLM_DENIED A quick look at xlators/nfs/server/src/nlm4.c:nlm4_unlock_resume() shows that cs->args->nlm4_stat is not checked there. This might be done somewhere else where I do not spot it this quickly. because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it. |
Created attachment 703726 [details] pcap dump of solaris cthon locks test failure While running the connectathon locking test from Solaris NFS client, the test fails with EINVAL. Gluster NFS logs has the following error: [2013-02-28 01:51:01.514511] W [nlm4.c:1682:nlm4_unlock_resume] 0-nfs-NLM: fd_lookup_uint64() returned NULL [2013-02-28 01:51:01.514713] W [nlm4.c:1689:nlm4_unlock_resume] 0-nfs-NLM: unable to unlock_fd_resume [2013-02-28 01:51:01.533188] W [nlm4.c:1682:nlm4_unlock_resume] 0-nfs-NLM: fd_lookup_uint64() returned NULL [2013-02-28 01:51:01.533278] W [nlm4.c:1689:nlm4_unlock_resume] 0-nfs-NLM: unable to unlock_fd_resume [2013-02-28 01:51:06.655493] W [nlm4.c:1682:nlm4_unlock_resume] 0-nfs-NLM: fd_lookup_uint64() returned NULL [2013-02-28 01:51:06.655614] W [nlm4.c:1689:nlm4_unlock_resume] 0-nfs-NLM: unable to unlock_fd_resume [2013-02-28 01:51:06.757796] W [nlm4.c:1682:nlm4_unlock_resume] 0-nfs-NLM: fd_lookup_uint64() returned NULL [2013-02-28 01:51:06.757908] W [nlm4.c:1689:nlm4_unlock_resume] 0-nfs-NLM: unable to unlock_fd_resume [2013-02-28 01:51:06.758939] W [nlm4.c:1682:nlm4_unlock_resume] 0-nfs-NLM: fd_lookup_uint64() returned NULL [2013-02-28 01:51:06.759015] W [nlm4.c:1689:nlm4_unlock_resume] 0-nfs-NLM: unable to unlock_fd_resume pcap dump from tcpdump of the session is attached.