[Bugs] [Bug 1271627] Creating a already deleted snapshot-clone deletes the corresponding snapshot.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1271627



--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12406 committed in release-3.7 by Rajesh
Joseph (rjoseph at redhat.com) 
------
commit c11e3232963d28b4cdf73b694d82f7b6ed38894f
Author: Avra Sengupta <asengupt at redhat.com>
Date:   Thu Oct 15 16:08:03 2015 +0530

    snapshot: Fix snapshot clone postvalidate

        BackPort Of http://review.gluster.org/#/c/12364/

    In glusterd_snapshot_clone_postvalidate(), we were deleting
    snap object and snap vol, by looking up snapname. Hence, it
    was deleting the orignal snapshot from which the clone was
    being created

    Instead it should fetch the clonename, the respective
    clone vol, and its corresponding snap object, and delete them.

    Also glusterd_snap_remove(), needs to differentiate a clone
    snap object from a snaphsot snap object, as in case of a clone
    snap object, we don't have any persisted data in
    /var/run/gluster/snaps/ and hence is shouldn't try to delete
    anything there.

    Change-Id: I02bb22a3898d5720e318a02d6cc32d25f75d317d
    BUG: 1271627
    Signed-off-by: Avra Sengupta <asengupt at redhat.com>
    Reviewed-on: http://review.gluster.org/12364
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga at redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph at redhat.com>
    (cherry picked from commit 59401a32de51cdb6c1a5a1208723e89e1a4abd30)
    Reviewed-on: http://review.gluster.org/12406

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=slPDqqELZW&a=cc_unsubscribe