Hi, we installed the Nexus3 OSS version. We have 250 GB of disk space for the one and only default blob store. I created now a first cleanup rule and applied it to 2 of our 8 repositories. Then I started the task to compact the blob store. Unfortunately this task is now running already for almost 3 days and it has not finished yet. I am not sure if it has released any disk space yet either. Is there any rule of thumb how long such a compact run might take? How can I find out if the task might be stuck? Does the compact task releases disk space incrementally or when the task has finished? Thanks a lot. Maik

I believe space is released incrementally, but running for three days doesn’t sound right with that smallish amount of binaries. Have you looked at the logs? Tasks produce task-specific log files, so you should be able to check when it last reported doing any work.

There will be a task-specific log file in the /log/tasks folder.

Nexus3 compact blob store task is running already 3 days

Sonatype Nexus Repository

maik.ebert.paysafe (Maik Ebert) October 5, 2021, 7:47am 4

It looked like those Nexus tasks were stuck.
We restarted Nexus.
Now its working as expected.

Thank you guys.

Topic		Replies	Views
Task "Admin - Compact blob store" seems extremely slow Sonatype Nexus Repository	3	1900	June 22, 2020
How to use ADMIN- Compact Blob store Task and for disc clean up Sonatype Nexus Repository	9	20003	July 29, 2020
Blob stores consuming disk space Sonatype Nexus Repository scheduled-task , nexus-repository	1	8295	April 22, 2021
Task not running (especially cleanup service, compact blobstore) Sonatype Nexus Repository	4	2299	April 21, 2021
Task "Compact Blob Store" does not reclaim disk space Sonatype Nexus Repository	6	2910	July 17, 2025

Nexus3 compact blob store task is running already 3 days

Related topics