Bong-Goku

Hello! Yesterday, I ran a Scatter/Move job to move all data (2.7 TB) from Disk 2 to Disk 8. I had to abort the job at about 2.3 TB transferred, but it seems the files have been copied and not moved, because the files are now on both Disk 2 and Disk 8. Which means that Disk 2 still has 2.7 TB used, and Disk 8 is filled up by the already tranferred 2.3 TB. How can I complete this job so the files get moved properly? Clicking on the small red X in the job history is not working. Thanks in advance and kind regards! Edit: I studied the behaviour of rsync and found that simply rerunning the very same job would fix the issue, but it was not possible because Unbalance denied running it because Disk 8 now didnt have enough free space to transfer 2.7 TB "again". So I had to run the job again in chunks... I would suggest not to use the Stop button, or implement a "resume aborted job" feature which ignores or handles free space better on the destination disk.

I have the same issue, but only for folders within the extracted archive. The extracted root folder is fine: drwxrwxrwx 1 nobody users 268 Jun 11 15:41 Ma********/ This is how the extracted files and folders look: -rw-r--r-- 1 nobody users 36862898736 Oct 28 2018 Ma*********.mkv drwxr-xr-x 1 nobody users 146 Sep 3 2019 Proof/ -rw-r--r-- 1 nobody users 956 Oct 29 2018 ma**********.nfo And the files inside the undeletable "Proof" folder: -rw-r--r-- 1 nobody users 133289 Oct 29 2018 m*********.proof.jpg The Umask 000 setting has of course been done. Those folders can only be deleted or moved in Terminal with root access. Any idea how this can be fixed? Kind regards and thanks in advance!