Bug 1428808
| Summary: | [GANESHA] Ganesha process aborted on the node having VIP from which volume is mounted while performing renaming and lookups from 4 clients | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Soumya Koduri <skoduri> |
| Component: | nfs-ganesha | Assignee: | Daniel Gryniewicz <dang> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | rhgs-3.2 | CC: | amukherj, asrivast, dang, ffilz, jthottan, kkeithle, mbenjamin, msaini, rcyriac, rhs-bugs, sbhaloth, skoduri, storage-qa-internal |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.2.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-ganesha-2.4.1-8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1428798 | Environment: | |
| Last Closed: | 2017-03-23 06:29:23 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: | 1428798 | ||
| Bug Blocks: | 1351528 | ||
|
Comment 2
Soumya Koduri
2017-03-03 12:05:36 UTC
Verified this bug on nfs-ganesha-gluster-2.4.1-8.el6rhs.x86_64 Steps: 1.Create a 5 node ganesha cluster 2.Create 6*2 Distributed-Replicate volume and Enable ganesha on it. 3.In the export file provide RO permission to 3 clients # showmount -e localhost Export list for localhost: /ganesha 10.70.37.192,10.70.37.176,10.70.37.129 4.Mount volume to 4 clients via v4 with 1 VIP 1st Client- Creating 2000 directories and renaming the same 2nd Client-lookups ls -lRt in loop (having RO permission) 3rd Client -lookups ls -lRt in loop (having RO permission) 4th Client- lookups ls -lRt in loop (having RO permission) As the issue is no more observed with this build,hence marking this bug as verified. 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://rhn.redhat.com/errata/RHEA-2017-0493.html |