Bug 1520751
| Summary: | [GSS]nfs-ganesha crashing after enabling ganesha.enable on a volume | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Abhishek Kumar <abhishku> |
| Component: | nfs-ganesha | Assignee: | Daniel Gryniewicz <dang> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | abhishku, amukherj, bkunal, chpai, dang, ffilz, jthottan, kkeithle, pasik, pdhange, psony, rhinduja, rhs-bugs, ssaha, storage-qa-internal |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-ganesha-2.5.5-1 | Doc Type: | Bug Fix |
| Doc Text: |
NFS-Ganesha crashed on NFS version 3 request if the GUARDED flag was set to true. The GUARDED flag checks for the presence of a duplicate file before performing the create or open call and should fail the request with NFS3ERR_EXIST if a duplicate file exists. With this fix, the GUARDED flag can handle the NFS version 3 create request and does not crash NFS-Ganesha.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-04 06:54:24 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: | 1503138 | ||
|
Description
Abhishek Kumar
2017-12-05 04:54:17 UTC
Hi Abhishek, It seems following commit got fixed this issue in upstream https://review.gerrithub.io/#/c/355473/. The patch will be available as part of 2.5 nfs-ganesha(RHGS 3.4). Requesting Dan to confirm the same. -- Jiffin Jiffin is correct. That is the correct fix. Note the workaround is unrelated to the patch; the patch fixes the issue, no workaround necessary. Without the patch, the workaround is needed (but will continue to be needed every time the situation comes up) I think it's a coincidence. Probably the file(s) in question were deleted as part of the server move. I'm not aware of any way to find which files are triggering the crash, I'm sorry. Which files are opened GUARDED is up to the client workload, and we have no way of finding them after the fact. In addition the codepath in question doesn't log anything useful. Logs could be added, but if we're giving them a patch, we should give them the fix. Even if they are found, removing them is only a temporary workaround. The next time they are not deleted by the client workload (the original bug was due to a crash in the client), the server will start crashing again. This means that the workaround is not very effective; it will allow the boot, but the crash will manifest again at some unknown point in the future. The only way to fully fix the issue is to apply the patch. *** Bug 1528376 has been marked as a duplicate of this bug. *** RHEA-2018:32427 was filed in error. this BZ is included in RHEA-2018:32429 Yes, nfs-ganesha-2.5.5-1 will be in RHGS-3.4 Agreed. "if the GUARDED flag was set to true, and the file existed." 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 |