Bug 1590657 - Excessive logging in posix_check_internal_writes() due to NULL dict
Summary: Excessive logging in posix_check_internal_writes() due to NULL dict
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: posix
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1590655
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-13 07:15 UTC by Krutika Dhananjay
Modified: 2019-05-11 00:22 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.1.1
Clone Of: 1590655
Environment:
Last Closed: 2019-05-11 00:22:02 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.