Bug 1221560

Summary:	`-bash: fork: Cannot allocate memory' error seen regularly on nodes on execution of any command
Product:	[Community] GlusterFS	Reporter:	senaik
Component:	bitrot	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED EOL	QA Contact:
Severity:	urgent	Docs Contact:	bugs <bugs>
Priority:	unspecified
Version:	3.7.0	CC:	ashah, bugs, sasundar, smohan, vbellur, vshankar
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1224182 (view as bug list)		Environment:
Last Closed:	2017-03-08 10:59:59 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:
Bug Depends On:	1226146
Bug Blocks:	1186580, 1224182

Description senaik 2015-05-14 11:20:55 UTC

Description of problem:
=======================
"-bash: fork: Cannot allocate memory error" is seen constantly on the nodes on execution of any command. This issue is seen with the latest glusterfs 3.7.0beta2 build. 

Not sure if this is a glusterfs problem as this issue was not seen on the earlier build on the same hardware.

I have collected the sosreports after rebooting from the console as no commands can be executed through the CLI until a reboot.


Version-Release number of selected component (if applicable):
=============================================================
glusterfs 3.7.0beta2


How reproducible:
=================
Intermittent.

Steps to Reproduce:
===================
1.Created some EC and tiered volumes with USS, quota and bitrot enabled.

2.Scheduled some snapshots 


Actual results:
==============
After a while we get "-bash: fork: Cannot allocate memory" on execution of any command. 


Expected results:


Additional info:

Comment 2 Anil Shah 2015-05-14 11:43:02 UTC

I also faced this issue immediately after installing glusterfs 3.7.0beta2 build.

Comment 3 Vijay Bellur 2015-05-14 11:57:58 UTC

I have seen this behavior with bitrot and more than 3 bricks on the same node. Maybe that's something we can avoid for now as it is a known problem with bitrot. Thanks.

Comment 4 Venky Shankar 2015-05-20 03:58:18 UTC

This is related to bz #1207134. Patch is under review.

Comment 5 Venky Shankar 2015-05-20 04:28:58 UTC

Just to be fully sure: did the problematic node have more than three (3) bricks (for a given volume).

Comment 7 senaik 2015-05-20 05:04:31 UTC

Yes, the nodes where I faced the issue had more than 3 bricks per volume

Comment 9 Kaushal 2017-03-08 10:59:59 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.