Bug 762242 (GLUSTER-510)

Summary:	crash in inode_ref
Product:	[Community] GlusterFS	Reporter:	Raghavendra Bhat <rabhat>
Component:	core	Assignee:	Anand Avati <aavati>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	mainline	CC:	chrisw, gluster-bugs, raghavendra
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.)