Description of problem: 1 - The bug in ec_update_stripe() that prevented some stripes to be updated after a write. 2 - If a file does not exist and we write on unaligned offset and user size, the last stripe on which "end" will fall should also be cached. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/18918 (cluster/ec: Fix bugs in stripe-cache feature) posted (#1) for review on master by Ashish Pandey
COMMIT: https://review.gluster.org/18918 committed in master by \"Ashish Pandey\" <aspandey> with a commit message- cluster/ec: Fix bugs in stripe-cache feature 1 - This patch fixes a bug in ec_update_stripe() that prevented some stripes to be updated after a write. 2 - This patch also include code modification for the case in which a file does not exist and we write on unaligned offset and user size, the last stripe on which "end" will fall should also be cached. Change-Id: I069cb4be1c8d59c206e3b35a6991e1fbdbc9b474 BUG: 1520758 Signed-off-by: Ashish Pandey <aspandey>
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-4.0.0, please open a new bug report. glusterfs-4.0.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/2018-March/000092.html [2] https://www.gluster.org/pipermail/gluster-users/