Bug 762242 (GLUSTER-510) - crash in inode_ref
Summary: crash in inode_ref
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-510
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-24 10:07 UTC by Raghavendra Bhat
Modified: 2015-09-01 23:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra Bhat 2009-12-24 07:17:07 UTC 
(In reply to comment #0)
> The glusterfs client crashed in inode_ref
> 
> 
> The backtrace is attached. The core file is in client03 (/core.4845)

This is observed in the availmedia testing.....
Comment 1 Raghavendra Bhat 2009-12-24 10:07:08 UTC 
The glusterfs client crashed in inode_ref


The backtrace is attached. The core file is in client03 (/core.4845)
Comment 2 Raghavendra G 2009-12-24 14:33:10 UTC 
was memory consumption too high when the crash happened? It seems like memory allocation failure due to system being out of memory.
Comment 3 Anand Avati 2010-01-08 15:22:15 UTC 
PATCH: http://patches.gluster.com/patch/2639 in master (libglusterfs/inode: add NULL checks.)
Note You need to log in before you can comment on or make changes to this bug.