Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1590657

Summary:	Excessive logging in posix_check_internal_writes() due to NULL dict
Product:	[Community] GlusterFS	Reporter:	Krutika Dhananjay <kdhananj>
Component:	posix	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1	CC:	atumball, bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1590655	Environment:
Last Closed:	2019-05-11 00:22:02 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:	1590655
Bug Blocks:

Description Krutika Dhananjay 2018-06-13 07:15:06 UTC

+++ This bug was initially created as a clone of Bug #1590655 +++

Description of problem:

I was running some write-intensive tests on my volume, and in a matter of 2 hrs, the 50GB space in my root partition was filled up. Turns out it's due to excessive logging in bricks - specifically in posix write when posix_check_internal_writes() does dict_get() before performing NULL-check on the dict.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2018-06-13 03:03:59 EDT ---

REVIEW: https://review.gluster.org/20250 (storage/posix: Fix excessive logging in WRITE fop path) posted (#1) for review on master by Krutika Dhananjay

Comment 1 Krutika Dhananjay 2018-10-31 05:00:24 UTC

https://review.gluster.org/c/glusterfs/+/20694