Description of problem: multiple failures for testcase: tests/basic/inode-quota-enforcing.t links to failures: rackspace-netbsd7-regression-triggered/16387/console rackspace-netbsd7-regression-triggered/16390/console Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14135 (quota: mark inode-quota-enforcing.t as bad_test) posted (#2) for review on master by Niels de Vos (ndevos)
COMMIT: http://review.gluster.org/14135 committed in master by Niels de Vos (ndevos) ------ commit 6631f9eb6740961e50c352dfef7c0a9d779d72f8 Author: Susant Palai <spalai> Date: Sun May 1 15:15:12 2016 +0530 quota: mark inode-quota-enforcing.t as bad_test tests/basic/inode-quota-enforcing.t regularly leaves a core behind. Some of the failed tests: * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16387/console * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16390/console Change-Id: I6c9c8f3503f033a3a10d585efa2de13caf4ac610 BUG: 1332021 Signed-off-by: Susant Palai <spalai> Reviewed-on: http://review.gluster.org/14135 Reviewed-by: Niels de Vos <ndevos> Tested-by: Niels de Vos <ndevos> Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com>
Adding the 'tracking' keyword so that our bug-status-check-script does not triple over it. Please remove the keyword when progress on this bug is made.
Look at the stack trace of the corefile, some memory corruption in synctask framework #0 0xbb4104b7 in ?? () (gdb) bt #0 0xbb4104b7 in ?? () #1 0xbb410458 in ?? () #2 0x00000004 in ?? () #3 0x00000006 in ?? () #4 0xbb457084 in ?? () #5 0xbb759119 in synctask_destroy (task=0xb8a18030) at /home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:391 #6 0xbb759195 in synctask_done (task=0xb8a18030) at /home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:409 #7 0xbb759a81 in synctask_switchto (task=0xb8a18030) at /home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:668 #8 0xbb759b2f in syncenv_processor (thdata=<error reading variable: Cannot access memory at address 0xba0fdfd8>, thdata@entry=<error reading variable: Cannot access memory at address 0xba0fdfd4>) at /home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/syncop.c:699 (gdb) quit
REVIEW: http://review.gluster.org/14184 (quota/tests : remove inode-quota-enforcing.t from bad tests) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)
COMMIT: http://review.gluster.org/14184 committed in master by Raghavendra Talur (rtalur) ------ commit 622f60c01c586a510a06b10a87dbc612206a5305 Author: Manikandan Selvaganesh <mselvaga> Date: Tue May 3 15:08:30 2016 +0530 quota/tests : remove inode-quota-enforcing.t from bad tests Change-Id: I4aef04cdbef7ecdabfe1dd64784cecf0624e6d8c BUG: 1332021 Signed-off-by: Manikandan Selvaganesh <mselvaga> Reviewed-on: http://review.gluster.org/14184 NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra Talur <rtalur>
Hi Manikandan, is ASSIGNED the correct status of this bug? If not, please correct it :) Thanks, Niels
Hi Niels, The bug state seems correct to me?
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.9.0, please open a new bug report. glusterfs-3.9.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://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/