Data disks are their own entity. You can detach them and attach them to other VMs. CloudStack doesn't assume that you want all the disks to die when you destroy a VM simply because they happen to be attached to that vm at the moment.
On Wed, Jan 28, 2015 at 10:47 PM, Michael Phillips <mphilli7...@hotmail.com> wrote: > What was the logic behind leaving the disks orphaned? > >> From: sanjeev.neelar...@citrix.com >> To: dev@cloudstack.apache.org >> Subject: RE: Orphaned Data Disks >> Date: Thu, 29 Jan 2015 05:30:49 +0000 >> >> That is expected behavior. Right now there is no option to change it. >> >> Sanjeev, >> CloudPlatform Engineering, >> Citrix Systems, Inc. >> >> >> -----Original Message----- >> From: Michael Phillips [mailto:mphilli7...@hotmail.com] >> Sent: Thursday, January 29, 2015 10:43 AM >> To: dev@cloudstack.apache.org >> Subject: Orphaned Data Disks >> >> Has anyone noticed that after destroying and expunging an instance that has >> a data disk attached, cloudstack leaves the datadisk orphaned? If so is this >> expected behavior, and if so is there an option to change it? >
