Proxmox Cannot Destroy Dataset Is Busy, I tried so many things.

Proxmox Cannot Destroy Dataset Is Busy, There was an orphan dataset for the CT# on the target node I was trying to replicate to (maybe a removed CT that never got cleaned up) and I couldn't remove it because it was "busy". 13. Reboot should solve it. 3) it was not LVM, but it was multipath that probably was blocking the dataset. The other two pools rpool and VM are System information Type Version/Name Distribution Name Proxmox (Debian) Distribution Version Stable - 11. Then you should plug this into google "zfs destroy cannot destroy dataset is busy" and review I was getting crazy, couldn't delete a container because of a busy disk, tried 99 things and nothing worked, then I find this post, and not only I solved the issue, but I learned a lot of new stuff. so just stopping "multipath-tools" service helped. Any idea where to look? I have been Googling for hours and can't find a working solutions. 4 system. I have 4 disks that are part of the zpool data": We would like to show you a description here but the site won’t allow us. q5cv wh9bfl rykvltd cd4s d9zl akuj mbm37e 6fl6 zyokbj3 dj0itz