Bug 1207643
| Summary: | [geo-rep]: starting the geo-rep causes "Segmentation fault" and core is generated by "gsyncd.py" | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Rahul Hinduja <rhinduja> | |
| Component: | geo-replication | Assignee: | Kotresh HR <khiremat> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | mainline | CC: | bugs, gluster-bugs, hchiramm, nsathyan | |
| Target Milestone: | --- | Keywords: | Triaged | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.7.0beta1 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1219428 (view as bug list) | Environment: | ||
| Last Closed: | 2015-05-14 17:27:12 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: | 1186580, 1219428 | |||
| 
        
          Description
        
        
          Rahul Hinduja
        
        
        
        
        
          2015-03-31 12:08:27 UTC
        
       REVIEW: http://review.gluster.org/10074 (libgfchangelog: Pass correct 'this' pointer to gf_history_consume) posted (#1) for review on master by Kotresh HR (khiremat) REVIEW: http://review.gluster.org/10074 (libgfchangelog: Use correct 'this' pointer on new thread creation) posted (#2) for review on master by Kotresh HR (khiremat) The two patches which handles the 'this' pointer correctly in libgfchangelog fixes this. http://review.gluster.org/#/c/9993/ (BUG: 1170075 : core seen with geo-rep start) http://review.gluster.org/10074 (The core seen with history crawl) REVIEW: http://review.gluster.org/10074 (libgfchangelog: Use correct 'this' pointer on new thread creation) posted (#3) for review on master by Kotresh HR (khiremat) REVIEW: http://review.gluster.org/10074 (libgfchangelog: Use correct 'this' pointer on new thread creation) posted (#4) for review on master by Kotresh HR (khiremat) REVIEW: http://review.gluster.org/10074 (libgfchangelog: Use correct 'this' pointer on new thread creation) posted (#5) for review on master by Kotresh HR (khiremat) COMMIT: http://review.gluster.org/10074 committed in master by Venky Shankar (vshankar) ------ commit 00d4125a5cb7102efeb23873cbaf155a71faa9dd Author: Kotresh HR <khiremat> Date: Tue Mar 31 20:13:59 2015 +0530 libgfchangelog: Use correct 'this' pointer on new thread creation When libgfchangelog is linked with non xlator application, it should point to 'master' xlator which is initiated separately. When ever a new thread is created, 'THIS' points to the global xlator. 'THIS' should point to corresponding xlator even then. This patch adjusts the pointer accordingly. Change-Id: I2a199bb3c73146a0329540aedcbae697a00f6f0a BUG: 1207643 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/10074 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar> Tested-by: Venky Shankar <vshankar> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |