Space not freed up after force-canceling a task

When a task is force-canceled, there is no clean-up performed, so temporary disks can be left in the Layering Service repository. You need to manually delete these. You can do this by logging in as root, or through any file manager like WinSCP or FileZilla.

Files can be left in one of these two folders:

/mnt/repository/Unidesk/Packaging Disks

/mnt/repository/Unidesk/Layered Images

If no tasks are running, then there should be no files in either folder. If there are tasks running, please allow them to complete or be canceled before proceeding.

Here is an example of “ls -l” with two force-canceled layer edit tasks, one for a layer named TEST APP and one for a layer named TEST. Since those tasks have already been force-canceled, you can delete all 4 files back and get 23GB back in your repository.

/mnt/repository/Unidesk/Packaging Disks

total 23158606

-rw-r–r– 1 root root 10752833024 Feb 6 15:53 TEST APPBoot.vhd

-rw-r–r– 1 root root 138452480 Feb 6 15:53 TEST APPPkg.vhd

-rw-r–r– 1 root root 12619631104 Feb 6 12:09 TESTBoot.vhd

-rw-r–r– 1 root root 203496448 Feb 6 12:09 TESTPkg.vhd

Similarly, here are four temporary files for publishing operations which were not cleaned up properly. Again, if there are no running tasks, you can safely delete these files.

/mnt/repository/Unidesk/Layered Images:

total 142595488

-rw-r–r– 1 root root 37246370304 Dec 19 18:33 Windows 10 Standard V2_237.vhd

-rw-r–r– 1 root root 37246370304 Dec 19 17:58 Windows 10 Standard V2_50.vhd

-rw-r–r– 1 root root 37147780096 Dec 5 13:07 Windows 10 Standard V2.vhd

-rw-r–r– 1 root root 38611949568 Oct 16 09:31 Windows 10 Test V2.vhd

If you happen to delete any of these files while a task is running, the task will fail. But subsequent asks will run normally.

Related:

Leave a Reply