Description of problem: Some fops such as readv, writev, open etc checks if the object is bad or not by getting the info from the inode context. If the inode_context_get operation fails, then bit-rot-stub still allows the fops to go through. It should fail the fop if inode context could not be obtained. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/11449 (features/bit-rot-stub: fail the fop if inode context get fails) posted (#4) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/11449 (features/bit-rot-stub: fail the fop if inode context get fails) posted (#5) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/11449 (features/bit-rot-stub: fail the fop if inode context get fails) posted (#6) for review on master by Raghavendra Bhat (raghavendra)
COMMIT: http://review.gluster.org/11449 committed in master by Venky Shankar (vshankar) ------ commit 7b44b6c16fb538e5f15a255182de4dee781994a0 Author: Raghavendra Bhat <raghavendra> Date: Sat Jun 27 13:17:32 2015 +0530 features/bit-rot-stub: fail the fop if inode context get fails In stub, for fops like readv, writev etc, if the the object is bad, then the fop is denied. But for checking if the object is bad inode context should be checked. Now, if the inode context is not there, then the fop is allowed to continue. This patch fixes it and the fop is unwound with an error, if the inode context is not found. Change-Id: I5ea4d4fc1a91387f7f9d13ca8cb43c88429f02b0 BUG: 1243391 Signed-off-by: Raghavendra Bhat <raghavendra> Reviewed-on: http://review.gluster.org/11449 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Venky Shankar <vshankar>
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