Description of problem: gfapi: Use inode_forget in case of unlink/rename objects After unlink/rename, the nonexistent inode should be remove from inode table, that's better than put to lru list. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/20641 (gfapi: Use inode_forget in case of unlink/rename objects) posted (#2) for review on master by Kinglong Mee
COMMIT: https://review.gluster.org/20641 committed in master by "Amar Tumballi" <amarts> with a commit message- gfapi: Use inode_forget in case of unlink/rename objects After unlink/rename, the nonexistent inode should be remove from inode table, that's better than put to lru list. Change-Id: I5a40df188f3f42a2c864cfb4404b22b288fdcc12 fixes: bz#1612750 Signed-off-by: Kinglong Mee <mijinlong>
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-5.0, please open a new bug report. glusterfs-5.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/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/