+++ This bug was initially created as a clone of Bug #1398076 +++ Description of problem: Found while testing the downstream kernel with FUSE support for seek_hole/data that we always get zero as the offset when we try these flags. --- Additional comment from Worker Ant on 2016-11-23 23:02:29 EST --- REVIEW: http://review.gluster.org/15920 (protocol/server: capute offset in seek) posted (#1) for review on master by Ravishankar N (ravishankar) --- Additional comment from Worker Ant on 2016-11-26 10:37:08 EST --- REVIEW: http://review.gluster.org/15920 (protocol/server: capture offset in seek) posted (#2) for review on master by Ravishankar N (ravishankar) --- Additional comment from Worker Ant on 2016-11-28 05:33:14 EST --- COMMIT: http://review.gluster.org/15920 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit cc37e5929d1e3ea4eaf4c4576a82066bf131ad05 Author: Ravishankar N <ravishankar> Date: Thu Nov 24 08:31:47 2016 +0530 protocol/server: capture offset in seek Problem: http://review.gluster.org/11482 implemented seek FOP but http://review.gluster.org/#/c/14137/ 'undid' the change where we pack the offset returned by seek in server xlator before sending it to the client. As a result, seek always returns zero to the client for SEEK_HOLE/ SEEK_DATA. Fix: I think 14137 removed it unintentionally, hence adding it back again. Signed-off-by: Ravishankar N <ravishankar> Change-Id: I67a1f7b53214b043c5291f5704be4a50b698f91c BUG: 1398076 Reviewed-on: http://review.gluster.org/15920 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
REVIEW: http://review.gluster.org/15944 (protocol/server: capture offset in seek) posted (#1) for review on release-3.9 by Ravishankar N (ravishankar)
COMMIT: http://review.gluster.org/15944 committed in release-3.9 by Pranith Kumar Karampuri (pkarampu) ------ commit 7639e8b55229e5984f781ad8c05854d357c709fb Author: Ravishankar N <ravishankar> Date: Thu Nov 24 08:31:47 2016 +0530 protocol/server: capture offset in seek Problem: http://review.gluster.org/11482 implemented seek FOP but http://review.gluster.org/#/c/14137/ 'undid' the change where we pack the offset returned by seek in server xlator before sending it to the client. As a result, seek always returns zero to the client for SEEK_HOLE/ SEEK_DATA. Fix: I think 14137 removed it unintentionally, hence adding it back again. > Reviewed-on: http://review.gluster.org/15920 > Smoke: Gluster Build System <jenkins.org> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Pranith Kumar Karampuri <pkarampu> (cherry picked from commit cc37e5929d1e3ea4eaf4c4576a82066bf131ad05) Signed-off-by: Ravishankar N <ravishankar> Change-Id: I67a1f7b53214b043c5291f5704be4a50b698f91c BUG: 1399131 Reviewed-on: http://review.gluster.org/15944 NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
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.9.1, please open a new bug report. glusterfs-3.9.1 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/gluster-users/2017-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/