So far, I could not find the related “problematic asset” and assign it to a specific blob on the file system. Now I run the job Repair - Reconcile componen database from blob store
I hoped the job would help an solve the issue. It didn’t my initial job Delete unused manifests and images still dont work.
But
The reconcile job printed the blob ID on the file system. Now my big question. Is it safe to delete those blobs on the file system level?
Output from the reconcile job:
*SYSTEM com.sonatype.nexus.blobstore.restore.internal.datastore.DockerRestoreBlobStrategy - Skipping as asset already exists, blob store: default, repository: docker-hosted, path: /v2/-/blobs/sha256:098cb24285eb179125c9118cab8b75f60edb80c3f0b23a160a4d79d8f8fa91a3, blob name: /v2/-/blobs/sha256:098cb24285eb179125c9118cab8b75f60edb80c3f0b23a160a4d79d8f8fa91a3, blob id: 5e1e0482-22ef-4d5c-8ff0-df6d6da2cfc7
With the blob ID I was able to find them:
find ./* -name "*5e1e0482-22ef-4d5c-8ff0-df6d6da2cfc7*"
./blobs/default/content/vol-13/chap-30/5e1e0482-22ef-4d5c-8ff0-df6d6da2cfc7.properties
./blobs/default/content/vol-13/chap-30/5e1e0482-22ef-4d5c-8ff0-df6d6da2cfc7.bytes
Any opinions? Or did someone already tried it?