Description of problem: Any directory or file creation should result in cache-invalidation requests sent to parent directory. However that is not the case currently due to a bug while processing these requests in the upcall xlator. We need to do invalidation checks on parent inode.
REVIEW: http://review.gluster.org/11387 (Upcall: Fix an issue with invalidating parent entries) posted (#2) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/11387 (Upcall: Fix an issue with invalidating parent entries) posted (#3) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/11387 (Upcall: Fix an issue with invalidating parent entries) posted (#4) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/11411 (protocol/server: Include a check to validate xprt->client) posted (#1) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/11411 (protocol/server: Include a check to validate xprt->client) posted (#3) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/11411 (protocol/server: Include a check to validate xprt->client) posted (#4) for review on master by soumya k (skoduri)
COMMIT: http://review.gluster.org/11387 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit 35d24f0c967130ef8424660b5f6dfd182bb305c1 Author: Soumya Koduri <skoduri> Date: Thu Jun 25 00:47:19 2015 +0530 Upcall: Fix an issue with invalidating parent entries Any directory or file creation should result in cache-invalidation requests sent to parent directory. However that is not the case currently due to a bug while processing these requests in the upcall xlator. We need to do invalidation checks on parent inode. Fixed the same. Also fixed an issue with null client entries while sending upcall notifications. Change-Id: I3da7c79091291ba36fd8f8ebcfebcd77a192f250 BUG: 1235542 Signed-off-by: Soumya Koduri <skoduri> Reviewed-on: http://review.gluster.org/11387 Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Meghana M <mmadhusu> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaleb KEITHLEY <kkeithle>
COMMIT: http://review.gluster.org/11411 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit 14cf2bbe77fbbaee8ee3211ec841a4f1ef3a8380 Author: Soumya Koduri <skoduri> Date: Thu Jun 25 19:49:59 2015 +0530 protocol/server: Include a check to validate xprt->client rpc_transport entries(xprt) are added to the conf->xprt_list during client connection with the server. But the client object is created and assigned to that transport object only during GF_HANDSK_SETVOLUME. Hence till that period, there could be xprt entries in the xprt_list without client associated with it. Added a check to validate the client object during upcall notify. Change-Id: I11e2fcd8b0a67e35302ede478b777b72d1973456 BUG: 1235542 Signed-off-by: Soumya Koduri <skoduri> Reviewed-on: http://review.gluster.org/11411 Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle>
REVIEW: http://review.gluster.org/11440 (Upcall: Fix an issue with invalidating parent entries) posted (#1) for review on release-3.7 by soumya k (skoduri)
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user