Bug 1475638

Summary: [Scale] : Client logs flooded with "inode context is NULL" error messages
Product: [Community] GlusterFS Reporter: Raghavendra G <rgowdapp>
Component: io-cacheAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.10CC: amukherj, asoman, bugs, pgurusid, rgowdapp, rhinduja, rhs-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.10.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1474180 Environment:
Last Closed: 2017-08-21 13:42: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: 1473229, 1474180    
Bug Blocks: 1475635, 1475637    

Comment 1 Worker Ant 2017-07-27 04:07:31 UTC
REVIEW: https://review.gluster.org/17891 (performance/io-cache: update inode contexts of each entry in readdirplus) posted (#1) for review on release-3.10 by Raghavendra G (rgowdapp)

Comment 2 Worker Ant 2017-08-11 11:09:15 UTC
COMMIT: https://review.gluster.org/17891 committed in release-3.10 by Shyamsundar Ranganathan (srangana) 
------
commit cfa33b224f58053bbbcbc46865fca70621a59f05
Author: Raghavendra G <raghavendra>
Date:   Fri May 17 12:52:32 2013 +0530

    performance/io-cache: update inode contexts of each entry in readdirplus
    
    io-cache stores read-cache in inode which is currently created only in
    lookup. But, with readdirplus and md-cache absorbing lookups, io-cache
    need not receive a lookup before a fop like readv.
    
    >Change-Id: I6eba995b0a90d4d5055a4aef0489707b852da1b8
    >BUG: 1474180
    >Signed-off-by: Raghavendra G <raghavendra>
    >Signed-off-by: Raghavendra G <rgowdapp>
    >Reviewed-on: https://review.gluster.org/5029
    >Smoke: Gluster Build System <jenkins.org>
    >CentOS-regression: Gluster Build System <jenkins.org>
    
    (cherry picked from commit b90e12134af85635199750967c326761d6c06e86)
    Change-Id: I6eba995b0a90d4d5055a4aef0489707b852da1b8
    BUG: 1475638
    Signed-off-by: Raghavendra G <raghavendra>
    Signed-off-by: Raghavendra G <rgowdapp>
    Reviewed-on: https://review.gluster.org/17891
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana>

Comment 3 Shyamsundar 2017-08-21 13:42:02 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.5, please open a new bug report.

glusterfs-3.10.5 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-August/000079.html
[2] https://www.gluster.org/pipermail/gluster-users/