Bug 1476559
| Summary: | [Stress] : Input/Output Error while creating files(using touch) / bonnie++/dd during MTSH. | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ambarish <asoman> |
| Component: | nfs-ganesha | Assignee: | Kaleb KEITHLEY <kkeithle> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | amukherj, bturner, dang, ffilz, jthottan, kkeithle, mbenjamin, msaini, rhinduja, rhs-bugs, sheggodu, skoduri, storage-qa-internal |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.4.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-ganesha-2.5.4-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-04 06:53:35 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1503134 | ||
|
Description
Ambarish
2017-07-30 10:18:21 UTC
Proposing as a blocker as application got affected. Test case was tried once on FUSE where it passed. [root@gqac019 gluster-mount]# dd if=/dev/zero of=a count=1 bs=100 conv=fdatasync dd: failed to open ‘a’: Input/output error [root@gqac019 gluster-mount]# Updating this: The reaper thread is running, so it's a livelock, not a deadlock. There is a state on the so_state_list that is not in the hashtable. This means state_del_locked() bails early, and the state is not deleted or removed from the so_state_list, causing an infinite loop with cr_mutex held. I'm wondering if this will fix it, but I'd like Frank to weigh in: b049eb90e78670d3e17ffe91b5c4048f8d7520d4 There may be one or two needed on top of that. There are a set of somewhat related patches, the ones marked with * are NLM (NFS v3) only, but may be required due to the other patches: * feb12d2fe13fcdbd5ae80cbe6575af98c4657520 Fix nlm client refcount going up from zero * acb632c319b3846200bcd718aa8e637bb0f4e1fd Fix nsm client refcount going up from zero * 52e0e125322fb0cc5c608be4cd43b90a702d88e2 Fix nlm state refcount going up from zero b049eb90e78670d3e17ffe91b5c4048f8d7520d4 Convert state_owner hash table to behave like others * 51d0f6c77d3e0d95be5ea27abe1f8c66db242884 Fix typo in hash table name in get_nlm_client() 006575d43d77dcd5c3eefd11e9d508a33e2bf459 Fix hashtable_setlatched overwrite parameter * 84d5ef4003e13a4078fa01d69a67bfe2ae02c61a Use care_t care instead of bool nsm_state_applies in get_nlm_state 60e20e2e9b531910c2ef1a20ad4036ff595df66f Fix a race in using hashtables leading to crashes[root@localhost src] There may be other relevant patches also. IO is successful when I try it on the same volume accessed via v3. The livelock is related to the v4 Session ID, so v3 should be unaffected. strea POST with rebase to nfs-ganesha-2.5.x Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2610 |