Bug 1316116
| Summary: | glusterd crash after running volume status detail command | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | michael.martel | ||||||
| Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.5.7 | CC: | amukherj, bugs | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | glusterfs-3.5.9 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-04-14 18:40: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: |
|
||||||||
Created attachment 1134514 [details]
stack trace from logfile
REVIEW: http://review.gluster.org/13661 (glusterd: fix glusterd_add_inode_size_to_dict to avoid glusterd to crash) posted (#1) for review on release-3.5 by Atin Mukherjee (amukherj) REVIEW: http://review.gluster.org/13661 (glusterd: fix glusterd_add_inode_size_to_dict to avoid glusterd to crash) posted (#2) for review on release-3.5 by Niels de Vos (ndevos) COMMIT: http://review.gluster.org/13661 committed in release-3.5 by Niels de Vos (ndevos) ------ commit 173eb1a056daef79cd593290250211d86de2cb82 Author: Atin Mukherjee <amukherj> Date: Thu Mar 10 10:19:44 2016 +0530 glusterd: fix glusterd_add_inode_size_to_dict to avoid glusterd to crash Backport of http://review.gluster.org/#/c/8134/ http://review.gluster.org/#/c/8492/ There were couple of backports from mainline got missed and due to which glusterd crashes if the underlying file system doesn't fail under list of supported file systems. This patch takes care of handling this negative scenario. Reported-by: Michael Martel <michael.martel> Change-Id: I6f601a4421869bbd7fc26e31f4ca4ffe075c0924 BUG: 1316116 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/13661 NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> 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.5.9, please open a new bug report. glusterfs-3.5.9 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://www.gluster.org/pipermail/announce/2016-April/000055.html [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.5.9, please open a new bug report. glusterfs-3.5.9 has been announced on the Gluster mailinglists [1] a while back, and packages for several distributions should be available by now. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.maintainers/486 |
Created attachment 1134513 [details] logfile from gluster server Description of problem: After running volume status VOLUME detail , the gluster daemon terminates. root@gs1:~# gluster volume status gv0 detail Connection failed. Please check if gluster daemon is operational. Version-Release number of selected component (if applicable): 3.5.7 Running on Debian Wheezy How reproducible: root@gs1:~# gluster volume status gv0 detail Connection failed. Please check if gluster daemon is operational. Steps to Reproduce: 1. root@gs1:~# gluster volume status gv0 detail Connection failed. Please check if gluster daemon is operational. 2. 3. Actual results: root@gs1:~# gluster volume status gv0 detail Connection failed. Please check if gluster daemon is operational. Expected results: unknown. I have never seen the output from the detail command. Additional info: