REVIEW: http://review.gluster.org/7996 (glusterd/snapshot: Fix snap delete cleanup) posted (#1) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/7996 (glusterd/snapshot: Fix snap delete cleanup) posted (#2) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/7996 (glusterd/snapshot: Fix snap delete cleanup) posted (#3) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/7996 (glusterd/snapshot: Fix snap delete cleanup) posted (#4) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/7996 (glusterd/snapshot: Fix snap delete cleanup) posted (#5) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/7996 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 5b0f65717f0d9489ca1c8750724cf9c8bfa11cbc Author: Avra Sengupta <asengupt> Date: Fri Jun 6 12:48:32 2014 +0000 glusterd/snapshot: Fix snap delete cleanup During commit the first thing that should happen is the snaps should be marked as GD_SNAP_STATUS_DECOMMISSION. So that if the node goes down the marked snap can be cleaned up when the node is coming back. Also during snap handshake while accepting snapshot from peer, we should check if the snap in question is decomissioned. In that case we shouldn't be accepting the peer data. Change-Id: Ib4e38d1b6bf49411928623fbc9f72f2b37b72086 BUG: 1104714 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/7996 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Rajesh Joseph <rjoseph> 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/
glusterd is not hung, but unable to delete stale snapshots
REVIEW: http://review.gluster.org/8954 (glusterd/snapshot: Check if LVM device path exists before delete.) posted (#1) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/8954 (glusterd/snapshot: Check if LVM device path exists before delete.) posted (#2) for review on master by Avra Sengupta (asengupt)
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
REVIEW: http://review.gluster.org/8954 (glusterd/snapshot: Check if LVM device path exists before delete.) posted (#3) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/8954 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 55aa4b185561edd7b3d1ab77a4f29a4facfdd7ff Author: Avra Sengupta <asengupt> Date: Tue Oct 21 08:42:40 2014 +0000 glusterd/snapshot: Check if LVM device path exists before delete. Check if the LV is present before deleting the LV. In case where the LV is absent (already deleted?), need not fail the snap delete operation. Also check if the LV is mounted before trying umount. In case it isn't umounted, only remove the LV. Change-Id: I0f5b2674797299d8748c6fac5b091f0caba65ca4 BUG: 1104714 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/8954 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>