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

[bugzilla at redhat.com]

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

            Bug ID: 1157452
           Summary: [USS]: deletion and creation of snapshots with same
                    name causes problems
           Product: Red Hat Storage
           Version: 3.0
         Component: gluster-snapshot
          Severity: high
          Assignee: rjoseph at redhat.com
          Reporter: rjoseph at redhat.com
        QA Contact: storage-qa-internal at redhat.com
                CC: bugs at gluster.org, rabhat at redhat.com
        Depends On: 1151004



+++ This bug was initially created as a clone of Bug #1151004 +++

Description of problem:

The deletion and recreation of a snapshot with same name creates problems while
accessing the contents of newly created snapshot bu giving ENOTCONN errors.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a file on the glusterfs mount point
2. Create a snapshot "snap1"
3. delete the file
4. delete the snapshot "snap1"
5. create a snapshot "snap1"
6. try to access snap1

Actual results:
applications get ENOTCONN

Expected results:
Applications should not get ENOTCONN

Additional info:
When the snapshot "snap1" is created first time and accessed (<mount
point>/<entry point>/snap1/<filename>), a new inode and dentry were created for
snap1 with parent being the entry point. Within the inode context the glfs_t
instance to access the snapshot and the handle to access the inode in the
snapshot world (or gfapi world in this case) is saved. But when the snapshot
was deleted and recreated, a new glfs_t instance is established (older one
being destroyed). So to access snap1 now, we have to do yet another lookup and
save the glfs_t instance and the new handle within the inode context. Since
that was not being done, older glfs_t instance was still used which gave
ENOTCONN when accessed as the corresponding snapshot volume does not exist
anymore.

--- Additional comment from Anand Avati on 2014-10-09 08:30:19 EDT ---

REVIEW: http://review.gluster.org/8917 (features/snapview-server: check if the
reference to the snapshot world is correct before doing any fop) posted (#1)
for review on master by Raghavendra Bhat (raghavendra at redhat.com)

--- Additional comment from Anand Avati on 2014-10-10 03:35:18 EDT ---

REVIEW: http://review.gluster.org/8917 (features/snapview-server: check if the
reference to the snapshot world is correct before doing any fop) posted (#2)
for review on master by Raghavendra Bhat (raghavendra at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1151004
[Bug 1151004] [USS]: deletion and creation of snapshots with same name
causes problems
-- 
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=qcD0SmZefN&a=cc_unsubscribe