Bug 1331225

Summary:	No way to determine clone-parent volume relationship
Product:	[Community] GlusterFS	Reporter:	Luis Pabón <lpabon>
Component:	snapshot	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.11	CC:	asengupt, bugs, madam, rjoseph
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 10:54:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Luis Pabón 2016-04-28 03:20:08 UTC

Description of problem:
Once a clone is created from a volume, there is no way to determine which volume(s) share the storage with the clone.


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


How reproducible:
100%

Steps to Reproduce:
- gluster volume create myvol ...
- gluster snapshot create mysnap myvol
- gluster snapshot activate mysnap
- gluster snapshot clone mysnap
- gluster snapshot deactivate mysnap
- gluster snapshot delete mysnap 

Actual results:
- gluster volume info
< Does not show any relation ship between volumes >


Expected results:
- gluster volume info
< Show a Parent: or Cloned: line in either one >

or

- gluster snapshot clone list <parent volume>
  Would show all children volumes


Additional info:

Comment 1 Luis Pabón 2016-04-28 03:24:52 UTC

One command is incorrect:
  - gluster snapshot clone mysnap
change to:
- gluster snapshot clone myclone mysnap

Comment 3 Kaushal 2017-03-08 10:54:34 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.