Bug 1790211
| Summary: | glusterfs-client crashed - signal received: 6 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Arie Skliarouk <skliarie+redhat-bugzilla> | ||||||
| Component: | fuse | Assignee: | bugs <bugs> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 7 | CC: | bugs, jahernan, lesser.evil, nchilaka, pasik, rhs-bugs, vbellur | ||||||
| Target Milestone: | --- | Keywords: | ZStream | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-03-12 12:20:00 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: |
|
||||||||
|
Description
Arie Skliarouk
2020-01-12 16:13:12 UTC
Coredump (281MB compressed) could be downloaded here: https://t12.catchmedia.com/tmp/glusterfs71-client.core.gz Hi, Can you share "thread apply all bt full" output from the core image? I have to setup the environment to access the same. Thanks, Mohit Agrawal Created attachment 1651777 [details]
gdb output of thread apply all bt full on the core
See attached gdb output of
thread apply all bt full
Kindly install the glusterfs debug version RPM and then share the stack dump. I am not able to see the stack of glusterfs in the attached bt output. Created attachment 1651797 [details]
gdb output of thread apply all bt full on the core - with debug symbols
Attached
gdb output of thread apply all bt full on the core - with debug symbols
Hi, As per stack dump it seems it is not a gluster bug, as we can see futex is getting crashed after throwing the error message "The futex facility returned an unexpected error code.". It seems the issue is similar to gcc bug that is already fixed in the latest release. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935750 Thanks, Mohit Agrawal I believe this to be an upstream bug which was accidentally marked to downstream . Hence changing it to appropriate stream. If I am wrong, feel free to correct accordingly I think it is imperative to fix glusterfs to workaround the bug in gcc of previous versions. You see, the gcc-9 is only available in ubuntu 19.04 and higher: https://packages.ubuntu.com/search?keywords=gcc-9 Whereas ubuntu 18.04 is still subject to the problem. Servers (where glusterfs usually is used) tend to be upgraded slowly, so we are talking about year if not more of users unable to use glusterfs on ubuntu. By not doing workaround (or possible - backporting the fix to previous version of gcc) many users will be unable to use the glusterfs-client. *** Bug 1775927 has been marked as a duplicate of this bug. *** Based on the stack trace, I would say this bug is the same as bug #1785208. It's fixed in version 7.2. Can you check if it doesn't crash anymore if you upgrade to 7.2 ? Do we need to upgrade/restart servers or only clients is enough. This is important for us because of production env. The recommended upgrade procedure is described here: https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_7/ First you should upgrade servers, then clients. For minor revision updates probably it's irrelevant the order, but as far as I know this is not tested. This bug is moved to https://github.com/gluster/glusterfs/issues/873, and will be tracked there from now on. Visit GitHub issues URL for further details Upgraded glusterfs to version 7.4 (using PPA https://launchpad.net/~gluster), no problems for 12 days already, from my perspective the bug is fixed. |