Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

vFile: GC should not remove orphan internal volume #1897

Closed
lipingxue opened this issue Sep 22, 2017 · 1 comment
Closed

vFile: GC should not remove orphan internal volume #1897

lipingxue opened this issue Sep 22, 2017 · 1 comment

Comments

@lipingxue
Copy link
Contributor

Currently, GC removed orphan service and orphan internal volume. It will cause some issue.
For example: two ESX shared 1 datastore, one each ESX, we have a swarm cluster running. When the first swarm cluster create a volume "aaa", an internal volume "_vf_aaa" will be created on the shared datastore. Then for the second swarm cluster, only internal volume "_vf_aaa" is visible, and it think "_vf_aaa" is an orphan volume and try to delete volume "aaa", which is wrong.

So we should remove the code to cleanup orphan internal volume.

@lipingxue lipingxue modified the milestones: Sprint - Superman, Sprint - Spiderman Sep 22, 2017
@lipingxue lipingxue self-assigned this Sep 26, 2017
@luomiao luomiao assigned luomiao and unassigned lipingxue Sep 28, 2017
@shuklanirdesh82
Copy link
Contributor

mustfix for vFile beta release

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants