Bug 1903468

Summary:	A brick process is getting crashed
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Mohit Agrawal <moagrawa>
Component:	core	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Leela Venkaiah Gangavarapu <lgangava>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	lgangava, Patric_Uebele, pprakash, puebele, rhs-bugs, sajmoham, sheggodu, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.z Batch Update 4	Flags:	puebele: needinfo+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-50	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-29 07:21:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mohit Agrawal 2020-12-02 07:39:23 UTC

One brick on one server is crashed and all attempts to bring it back online have failed.The corresponding brick on the other (of a replica 2) server is ok. Other bricks are ok.

The brick process is getting crashed at the time running a lookup operation.After analyzed the coredump we have found it was crashed because on file huge xattrs are created.On the brick side it run's every posix_operation under iot_worker thread and per thread stack size is around 256k. In posix_layer the function posix_get_ancestry_non_directory call's alloca based on backend xattr size because the size was bigger than 256k so it was crashed.

Comment 1 Mohit Agrawal 2020-12-02 07:40:54 UTC

The issue is already fixed in upstream https://github.com/gluster/glusterfs/issues/1699

Comment 17 errata-xmlrpc 2021-04-29 07:21:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (glusterfs bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1462