Description of problem: While running BVT on 3.7beta2 build on rhel6.6 , saw a posix crash Backtrace of the core: (gdb) bt #0 0x0000003d4e20c380 in pthread_spin_lock () from /lib64/libpthread.so.0 #1 0x00007f4800e98dbd in ?? () from /usr/lib64/glusterfs/3.7.0beta2/xlator/storage/posix.so #2 0x0000003d4fa1cfd3 in dict_foreach_match () from /usr/lib64/libglusterfs.so.0 #3 0x0000003d4fa1d068 in dict_foreach () from /usr/lib64/libglusterfs.so.0 #4 0x00007f4800e98335 in do_xattrop () from /usr/lib64/glusterfs/3.7.0beta2/xlator/storage/posix.so #5 0x00007f4800e98841 in posix_xattrop () from /usr/lib64/glusterfs/3.7.0beta2/xlator/storage/posix.so #6 0x0000003d4fa2d0f3 in default_xattrop () from /usr/lib64/libglusterfs.so.0 #7 0x0000003d4fa2d0f3 in default_xattrop () from /usr/lib64/libglusterfs.so.0 #8 0x0000003d4fa2d0f3 in default_xattrop () from /usr/lib64/libglusterfs.so.0 #9 0x0000003d4fa2d0f3 in default_xattrop () from /usr/lib64/libglusterfs.so.0 #10 0x0000003d4fa2d0f3 in default_xattrop () from /usr/lib64/libglusterfs.so.0 #11 0x0000003d4fa2d0f3 in default_xattrop () from /usr/lib64/libglusterfs.so.0 #12 0x0000003d4fa2d0f3 in default_xattrop () from /usr/lib64/libglusterfs.so.0 #13 0x0000003d4fa307b2 in default_xattrop_resume () from /usr/lib64/libglusterfs.so.0 #14 0x0000003d4fa4bb60 in call_resume () from /usr/lib64/libglusterfs.so.0 #15 0x00007f47fb3a2398 in iot_worker () from /usr/lib64/glusterfs/3.7.0beta2/xlator/performance/io-threads.so #16 0x0000003d4e2079d1 in start_thread () from /lib64/libpthread.so.0 #17 0x0000003d4dee89dd in clone () from /lib64/libc.so.6 Version-Release number of selected component (if applicable): Red Hat Enterprise Linux Server release 6.6 (Santiago) glusterfs-3.7.0beta2-0.0.el6.x86_64 How reproducible: Tried once Steps to Reproduce: Run BVT on 3.7beta2 build on rhel6.6 Actual results: Posix crash Expected results: No crashes and cores Additional info:
REVIEW: http://review.gluster.org/11167 (storage/posix: Handle MAKE_INODE_HANDLE failures) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/11167 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit a824655de117d536b16c20ab8e38dfc698107d6a Author: Pranith Kumar K <pkarampu> Date: Mon Jun 1 13:34:33 2015 +0530 storage/posix: Handle MAKE_INODE_HANDLE failures Backport of http://review.gluster.com/11028 BUG: 1221473 Change-Id: Iefa2a9037e7a415e55581054b16c840bae56561e Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11167 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krutika Dhananjay <kdhananj> Tested-by: NetBSD Build System <jenkins.org>
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.2, please reopen this bug report. glusterfs-3.7.2 has been announced on the Gluster Packaging mailinglist [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/packaging/2015-June/000006.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user