REVIEW: http://review.gluster.org/7892 (glusterd/snapshot : Remove the barrier key from snap volinfo before generating brick volfile.) posted (#1) for review on master by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/7892 (glusterd/snapshot : Remove the barrier key from snap volinfo before generating brick volfile.) posted (#2) for review on master by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/7892 (glusterd/snapshot : Remove the barrier key from snap volinfo before generating brick volfile.) posted (#3) for review on master by Krishnan Parthasarathi (kparthas)
COMMIT: http://review.gluster.org/7892 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 9f90cbee7da450271873340c0b13059064c41af1 Author: Sachin Pandit <spandit> Date: Tue Jun 3 05:50:53 2014 +0530 glusterd/snapshot : Remove the barrier key from snap volinfo before generating brick volfile. Problem : During snapshot creation if I/O is in progress, then barrier value is enabled. Hence during snapshot create and in-turn snapshot restore the barrier value is set to enable. Because of this further I/O on the mount point fails. Solution : Remove the barrier key from newly created snap volinfo before generating the brick volfiles. Change-Id: I180b3adfbb364159fd353b2d0fb630e004099aa5 BUG: 1098487 Signed-off-by: Sachin Pandit <spandit> Reviewed-on: http://review.gluster.org/7892 Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users