Bug 1601331
Summary: | dht: Crash seen in thread dht_dir_attr_heal | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Kotresh HR <khiremat> | |
Component: | distribute | Assignee: | Nithya Balachandran <nbalacha> | |
Status: | CLOSED ERRATA | QA Contact: | Prasad Desala <tdesala> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.4 | CC: | khiremat, rhs-bugs, sankarshan, spalai, storage-qa-internal, vdas | |
Target Milestone: | --- | Keywords: | Regression | |
Target Release: | RHGS 3.4.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.12.2-15 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1602866 (view as bug list) | Environment: | ||
Last Closed: | 2018-09-04 06:50: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: | 1503137, 1602866 |
Description
Kotresh HR
2018-07-16 06:18:05 UTC
Please provide access to the coredump I have just uploaded the core to qe machine. Prasad will share the details. The host is "fedora 24" not rhel and it's my local VM. So if you can't use the core file, let me know if I need to update the other gluster binaries. I am unable to see any symbols in the core file when I try to open it. Will check and update if dht misses any gfid update in healing code path. Nithya, If you are working on this already, could you move this to assigned state. Susant (In reply to Susant Kumar Palai from comment #9) > Nithya, If you are working on this already, could you move this to assigned > state. > > Susant Done. I suspect the heal in dht_lookup_dir_cbk() - the gfid is not set in loc. loc->inode->gfid is also NULL which is what causes the crash. Hi, The lib64 directory which was missing is uploaded here http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1601331/ core/ 2018-07-16 12:04 - georep-basic-dr-rsyn..> 2018-07-16 12:37 131M gluster-binares.tar 2018-07-16 12:37 1.6M lib64.tar 2018-07-17 16:50 333M libraries.tar 2018-07-16 12:44 30M Steps to use the core for debugging. 1. Create a directory on local machine and change directory #mkdir /dht-crash #cd /dht-crash 2. Download all libraries.tar, gluster-binaries.tar and core/core-glustersproc0-6-0-0-13668-1531717404 into /dht-crash directory 3. untar all the tar files 4. gdb usr/local/sbin/glusterfs core-glustersproc0-6-0-0-13668-1531717404 (gdb) set solib-absolute-prefix /dht-crash (gdb) bt Mid air collision, setting the status back to ASSIGNED (In reply to Kotresh HR from comment #11) > Hi, > > The lib64 directory which was missing is uploaded here > > http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1601331/ > > core/ 2018-07-16 12:04 - > georep-basic-dr-rsyn..> 2018-07-16 12:37 131M > gluster-binares.tar 2018-07-16 12:37 1.6M > lib64.tar 2018-07-17 16:50 333M > libraries.tar 2018-07-16 12:44 30M > > > Steps to use the core for debugging. > > 1. Create a directory on local machine and change directory > #mkdir /dht-crash > #cd /dht-crash > > 2. Download all libraries.tar, gluster-binaries.tar and > core/core-glustersproc0-6-0-0-13668-1531717404 into /dht-crash directory > > 3. untar all the tar files > > 4. gdb usr/local/sbin/glusterfs core-glustersproc0-6-0-0-13668-1531717404 > > (gdb) set solib-absolute-prefix /dht-crash > (gdb) bt Thank you. I can now see the symbols. Still looking into this. I shall update by tomorrow. On glusterfs version: 3.12.2-15.el7rhgs.x86_64, ran the same test case mentioned in the description multiple times and didn't hit this issue. Hencce, moving this BZ to Verified state. 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/RHSA-2018:2607 |