Bug 1560969

Summary:	Garbage collect inactive inodes in fuse-bridge
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	fuse	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	amukherj, bugs, csaba, rgowdapp, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1511779	Environment:
Last Closed:	2019-03-25 16:30:19 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:	1511779
Bug Blocks:

Comment 1 Amar Tumballi 2018-03-27 11:31:38 UTC

Description of problem:
Currently fuse-bridge has an lru limit of the inode table as infinite. This means we are dependent on kernel to send forgets even though the inode is not active. However, we can implement garbage collection of inodes in lru list of itable. We can ask kernel to send a forget by calling inode/entry_invalidate on the inode.

Comment 2 Worker Ant 2018-03-27 11:35:22 UTC

REVIEW: https://review.gluster.org/19778 (fuse: add --lru-limit option) posted (#2) for review on master by Amar Tumballi

Comment 3 Worker Ant 2018-12-14 17:35:20 UTC

REVIEW: https://review.gluster.org/19778 (fuse: add --lru-limit option) posted (#36) for review on master by Amar Tumballi

Comment 4 Shyamsundar 2019-03-25 16:30:19 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-6.0, please open a new bug report.

glusterfs-6.0 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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/