Hello,
Yesterday I was migrating a VM from 1 hypervisor to another. But then this error was shown:
Delete of the replication job was not enough on the target the disk still exists and unable to delete. When I try to delete it through the interface I get this.
What is a correct way to delete this disk from the pool and how can we prevent a dirty bitmap?
For some unknown reason for me, there was a task runner, after stopping the process id I was able to delete it.
Yesterday I was migrating a VM from 1 hypervisor to another. But then this error was shown:
Code:
2022-11-07 00:27:40 use dedicated network address for sending migration traffic ()
2022-11-07 00:27:41 starting migration of VM 3934 to node '' ()
2022-11-07 00:27:41 found local, replicated disk 'vm-data:vm-3934-disk-0' (in current VM config)
2022-11-07 00:27:41 scsi0: start tracking writes using block-dirty-bitmap 'repl_scsi0'
2022-11-07 00:27:41 ERROR: VM 3934 qmp command 'block-dirty-bitmap-add' failed - Bitmap already exists: repl_scsi0
2022-11-07 00:27:41 aborting phase 1 - cleanup resources
2022-11-07 00:27:41 ERROR: migration aborted (duration 00:00:01): VM 3934 qmp command 'block-dirty-bitmap-add' failed - Bitmap already exists: repl_scsi0
TASK ERROR: migration abortedDelete of the replication job was not enough on the target the disk still exists and unable to delete. When I try to delete it through the interface I get this.
Code:
TASK ERROR: zfs error: cannot destroy 'vm-data/vm-3934-disk-0': dataset is busyWhat is a correct way to delete this disk from the pool and how can we prevent a dirty bitmap?
For some unknown reason for me, there was a task runner, after stopping the process id I was able to delete it.
Last edited: