Description of problem: Every two weeks or so the gluster client process is crashing / getting killed by OOM killer when running commvault backups. Version-Release number of selected component (if applicable): glusterfs-3.8.4-18.el6rhs.x86_64 How reproducible: Intermittent, happens about once every two weeks when running daily backups where commvault writes to gluster. Steps to Reproduce: 1. Run commvault backup SW 2. Backup to a gluster FUSE mount 3. Crash / OOM killer kills the FUSE mount and the backup fails. Actual results: Crash / OOM kill takes down the gluster mount. Expected results: Normal operation. Additional info: We have 2 app cores from the gluster client mount process that need analysis.
Few more details required! Size of RAM. $ grep 'lru' <statedump-file> $ grep 'active' <statedump-file>
RAM at time of coredump was 16GB, client has since been upgraded to 32GB RAM. Statedumps will be uploaded to case
Its been since 12/3 and no updates have been added and no owner is assigned, what is the status of this bug?
Core was generated by `/usr/sbin/glusterfs --volfile-server=aclrhgs.noblehosted.com --volfile-server=a'. Program terminated with signal 11, Segmentation fault. #0 mem_get (mem_pool=0x7fcd5800f4e0) at mem-pool.c:523 523 *pool_ptr = (struct mem_pool *)mem_pool; (gdb) f 0 #0 mem_get (mem_pool=0x7fcd5800f4e0) at mem-pool.c:523 523 *pool_ptr = (struct mem_pool *)mem_pool; (gdb) p ptr $1 = (void *) 0x0 (gdb) p pool_ptr $2 = (struct mem_pool **) 0x10