1. The VRM delete volume is executed by the deleteVolumeThread. The non-virtualized data store. The message sent to the host is bsbFormatVolume. Locate the host delivered by the delete command in the vrm.log log and log in to the host to check the log.
![]()
2. Check the nc.log log of the host, find the bsbFormatVolume entry, and find that the dmsetup create command fails, prompting dm device create failed.
![]()
3. View the message log, there is a device-mapper error print: error adding target to table
![]()
4. In the /dev/disk/by-id directory, find the drive letter corresponding to the data store. In this example, sdd, execute the lsblk command, and see the unknown dm device with lvm remaining on sdd.![]()
root cause :
If there is a residual dm device on the data storage to be deleted, the dmsetup create command fails to be executed when the volume is deleted. The disk deletion fails and the space cannot be freed.
Solution :
Delete the residual dm device and execute the command in the background of the host:
Dmsetup remove /dev/mapper/fsp_mongdb-ceilometer--data
Dmsetup remove /dev/mapper/fsp_mongdb-rabbitmq
