Bug 1273716 - [RFE]: [SNAPSHOT]: snapshot-clone should not be created under /run/gluster/snaps
Summary: [RFE]: [SNAPSHOT]: snapshot-clone should not be created under /run/gluster/snaps
Keywords:
Status: CLOSED DUPLICATE of bug 1273722
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: snapshot
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: rjoseph
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-21 06:07 UTC by Shashank Raj
Modified: 2016-11-08 03:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-14 09:17:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Shashank Raj 2015-10-21 06:07:40 UTC
Description of problem:

Currently if we create the clone of a snapshot, the clones gets created under /run/gluster/snaps. Since clone is like a regular volume, there should be a separate path for this like /run/gluster/clones


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


How reproducible:
Always

Steps to Reproduce:
1.Create a volume and create a snapshot of it.
2.Now create a clone of this snapshot.
3.Observe that the clone is created under /run/gluster/snaps where we have entries for the snapshots.
4.We should have clones created under a separate directory.

Actual results:
Clones are getting created under /run/gluster/snaps


Expected results:
Clones should not be created under /run/gluster/snaps and they should have entries in a separate directory like /run/gluster/clones, since they are just like regular volumes



Additional info:

Comment 2 Avra Sengupta 2016-07-14 09:17:30 UTC
There are no consequences of storing the clones under /run/gluster/snaps pther than the one mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1273722.
This will be handled as part of the fix for 1273722. Marking this as a duplicate

*** This bug has been marked as a duplicate of bug 1273722 ***


Note You need to log in before you can comment on or make changes to this bug.