[Bugs] [Bug 1158791] [USS]: deletion and creation of snapshots with same name causes problems

[bugzilla at redhat.com]

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



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9007 committed in release-3.6 by Vijay Bellur
(vbellur at redhat.com) 
------
commit 2ebb417e7558a35990b7c2784d25fe38ea975d0e
Author: Raghavendra Bhat <raghavendra at redhat.com>
Date:   Thu Oct 9 17:32:48 2014 +0530

    features/snapview-server: check if the reference to the snapshot world is
correct before doing any fop

    The following operations might lead to problems:
    * Create a file on the glusterfs mount point
    * Create a snapshot (say "snap1")
    * Access the contents of the snapshot
    * Delete the file from the mount point
    * Delete the snapshot "snap1"
    * Create a new snapshot "snap1"

    Now accessing the new snapshot "snap1" gives problems. Because the inode
and
    dentry created for snap1 would not be deleted upon the deletion of the
snapshot
    (as deletion of snapshot is a gluster cli operation, not a fop). So next
time
    upon creation of a new snap with same name, the previous inode and dentry
itself
    will be used. But the inode context contains old information about the
glfs_t
    instance and the handle in the gfapi world. Directly accessing them without
    proper check leads to ENOTCONN errors. Thus the glfs_t instance should be
    checked before accessing. If its wrong, then right instance should be
obtained
    by doing the lookup.

    Change-Id: I975245b8f6b7fea0a90eb5e36e8149d12457ac10
    BUG: 1158791
    Reviewed-on: http://review.gluster.org/9007
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>
    Tested-by: Vijay Bellur <vbellur at redhat.com>

-- 
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=TXKU39yQcs&a=cc_unsubscribe