Description of problem: A seek with SEEK_HOLE can return an offset bigger than the file size. Additionally some offsets beyond the file size do return a valid answer instead of ENXIO as they should. Version-Release number of selected component (if applicable): mainline How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/17228 (cluster/ec: correctly handle end of file for seek) posted (#1) for review on master by Xavier Hernandez (xhernandez)
REVIEW: https://review.gluster.org/17228 (cluster/ec: correctly handle end of file for seek) posted (#2) for review on master by Xavier Hernandez (xhernandez)
REVIEW: https://review.gluster.org/17228 (cluster/ec: correctly handle end of file for seek) posted (#3) for review on master by Xavier Hernandez (xhernandez)
COMMIT: https://review.gluster.org/17228 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit eb96dd45f8e583c6bad84bf32ca17e2bb01dd38f Author: Xavier Hernandez <xhernandez> Date: Tue May 9 19:40:21 2017 +0200 cluster/ec: correctly handle end of file for seek When a SEEK_HOLE was issued near to the end of file, sometimes an offset beyond the end of file was returned. Another problem was that using some offsets greater than the end of file returned successfully instead of failing with ENXIO. Change-Id: I238d2884ba02fd19a78116b0f8f8e8d6338fb3f5 BUG: 1449348 Signed-off-by: Xavier Hernandez <xhernandez> Reviewed-on: https://review.gluster.org/17228 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts> 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.11.2, please open a new bug report. glusterfs-3.11.2 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-July/031908.html [2] https://www.gluster.org/pipermail/gluster-users/
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.12.0, please open a new bug report. glusterfs-3.12.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://lists.gluster.org/pipermail/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/