hopelessDude

Hi @trurl point taken. How does it usually work when the VM exceeds the cache size? Pause until cache becomes available again and so on?

Hi @jonathanm I think I will do that next. Or possibly specify a disk where the vdisk image is stored during vm creation. In the log it sais that the mover is skipping the vdisk image of the vm rackserver move: move: skip /mnt/cache/domains/Ubuntu/vdisk1.img instead it has kilometers of jbreed-nessus entries: /appdata/jbreed-nessus/opt/nessus/lib/nessus/plugins/openSUSE-2019-1419.nasl

I am pretty much back to my original problem now. The cache is full. The mover is running (log is at 61% now) and my VM is paused again. I am downloading data to the VM and it seems as though the download is faster than the mover.. pretty much unusable.

thx for the feedback. It is awesome that attachements cannot be deleted.. so there is that 🤣

thank you @itimpi I clicked for a bit to find it. It seems that some stuff has worked out now that I have changed all the shares to yes. appdata is lowkey complaining that it is not cache only.. but who cares right?

The script is not clearing my cache drive, but it is moving now to fill up the rest of my drives. I have no idea where it is getting all the data from to be honest. Disk 1 is now at 100% .. when will it stop. I have tried changing the share settings to force free space, but mover is ignoring it pretty much. I deleted a VM that had a 2tb diskimage.. (and likely was the cause to clog my cache drive which was only 500GB) but it is not really "clearing the space" now if that makes sense. Also mover has no verbose mode that I can look at (or understand where to look for it). Any advice would be cool.