Description of problem: glusterfsd version 3.8.4 is crashing every four hours. The core Version-Release number of selected component (if applicable): glusterfs 3.8.4 centos kernel 2.6.32-642.6.1.el6.x86_64 How reproducible: Not reproducible happens Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Crash info (gdb) where #0 0x00007f096422ffc3 in _IO_vfprintf_internal (s=0x7f0938a7c280, format=0x7f0953df6371 "mkdir of %s failed", ap=0x7f0938a7c460) at vfprintf.c:236 #1 0x00007f09642ee03c in __vasprintf_chk (result_ptr=0x7f0938a7c498, flags=1, format=0x7f0953df6371 "mkdir of %s failed", args=0x7f0938a7c460) at vasprintf_chk.c:68 #2 0x00007f096588740d in _gf_msg () from /usr/lib64/libglusterfs.so.0 #3 0x00007f0953de19d6 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/storage/posix.so #4 0x00007f09535af339 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/trash.so #5 0x00007f0953de1201 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/storage/posix.so #6 0x00007f09535af339 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/trash.so #7 0x00007f0953de1201 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/storage/posix.so .... .... #395 0x00007f0953de1201 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/storage/posix.so #396 0x00007f09535b1dfa in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/trash.so #397 0x00007f0953ddcaf1 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/storage/posix.so #398 0x00007f09535b06f3 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/trash.so #399 0x00007f0953dd1549 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/storage/posix.so #400 0x00007f09535a9e75 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/trash.so #401 0x00007f0953387919 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/changetimerecorder.so #402 0x00007f0952cd042f in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/changelog.so #403 0x00007f095289a908 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/bitrot-stub.so #404 0x00007f095268964e in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/access-control.so #405 0x00007f0965902569 in default_unlink () from /usr/lib64/libglusterfs.so.0 #406 0x00007f095225ba31 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/worm.so #407 0x00007f095204dc96 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/read-only.so #408 0x00007f0951e3ef67 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/leases.so #409 0x00007f0951c29252 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/features/upcall.so #410 0x00007f0965906d57 in default_unlink_resume () from /usr/lib64/libglusterfs.so.0 #411 0x00007f09658a1050 in call_resume () from /usr/lib64/libglusterfs.so.0 #412 0x00007f0951a1d911 in ?? () from /usr/lib64/glusterfs/3.8.4/xlator/performance/io-threads.so #413 0x00007f096496baa1 in start_thread (arg=0x7f0938b7b700) at pthread_create.c:301 #414 0x00007f09642d4aad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115
Vigneswaran, If possible, please attach the core file to the BZ. Also, please mention the full primary glusterfs package name, this will help identify the build.
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days