weizhouapache commented on issue #5461: URL: https://github.com/apache/cloudstack/issues/5461#issuecomment-1006372429
> @DaanHoogland, I think it's a bug. After reinstalling a VM, CS creates new volumes, and the old ones in DB are marked as destroyed but still exist on the hypervisor side. I've tested this on 4.16 (I think it's the same on 4.15), hypervisor KVM. > > > mysql> SELECT uuid,instance_id, state, pool_id FROM cloud.volumes where name="ROOT-6531"; > > +--------------------------------------+-------------+---------+---------+ > > | uuid | instance_id | state | pool_id | > > +--------------------------------------+-------------+---------+---------+ > > | 156e1612-ff54-4d77-a29e-87cea3303fc4 | NULL | Destroy | 117 | > > | 0af8094b-9766-4f42-8e08-9e2013980cc6 | NULL | Destroy | 117 | > > | 02e9022d-aaa3-4b73-8fc2-d0a64051499d | NULL | Destroy | 117 | > > | f8cfb72b-d879-4831-b99f-9fcd8d473238 | 6531 | Ready | 117 | > > +--------------------------------------+-------------+---------+---------+ > > 4 rows in set (0.01 sec) > > > -rw-r--r-- 1 root root 22M Nov 27 07:29 156e1612-ff54-4d77-a29e-87cea3303fc4 > > -rw-r--r-- 1 root root 23M Nov 27 07:41 0af8094b-9766-4f42-8e08-9e2013980cc6 > > -rw-r--r-- 1 root root 23M Nov 27 08:04 02e9022d-aaa3-4b73-8fc2-d0a64051499d > > -rw-r--r-- 1 root root 19M Nov 27 08:20 f8cfb72b-d879-4831-b99f-9fcd8d473238 @slavkap I think this is not a bug. when reinstall a vm, the old root disk is changed to 'Destroy' state. you can recover to a Ready volume, and use it like other volumes. Otherwise, the 'Destroy' volume will be cleaned up by cloudstack after a period (depends on global setting `storage.cleanup.interval` and `storage.cleanup.delay`) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
