How to deal with zombie oids?

[Flo9520]

Hello,

I am currently facing the issue that my data got somehow corrupted. The StorageManager tries to load an entity wih an Oid that it can't find leading to a crash on application startup.

The stacktrace:

Caused by: org.eclipse.store.storage.exceptions.StorageExceptionConsistency: No entity found for objectId 1000000000000530805
	at org.eclipse.store.storage.types.StorageChannel$EntityCollectorByOid.accept(StorageChannel.java:758)
	at org.eclipse.serializer.persistence.binary.types.LoadItemsChain$ChannelHashing$ChainItemObjectIdSet.iterate(LoadItemsChain.java:280)
	at org.eclipse.store.storage.types.StorageChannel$Default.collectLoadByOids(StorageChannel.java:552)
	at org.eclipse.store.storage.types.StorageRequestTaskLoadByOids$Default.internalProcessBy(StorageRequestTaskLoadByOids.java:52)
	at org.eclipse.store.storage.types.StorageRequestTaskLoadByOids$Default.internalProcessBy(StorageRequestTaskLoadByOids.java:22)
	at org.eclipse.store.storage.types.StorageChannelTask$Abstract.processBy(StorageChannelTask.java:244)
	at org.eclipse.store.storage.types.StorageChannel$Default.work(StorageChannel.java:399)
	at org.eclipse.store.storage.types.StorageChannel$Default.run(StorageChannel.java:471)
	at java.base/java.lang.Thread.run(Thread.java:1583)

From what I read this should never happen and is a bug. I was not able to identify any bug in my service since it is not very complex and only has some CRUD stuff in it.

So my next idea was to just run the garbage collection manually but the garbage collection does pretty much the same check, marks the oid as zombie and continues. The default impl of org.eclipse.store.storage.types.StorageGCZombieOidHandler (which is supposed to handle such an event) also does nothing.

Has anybody else had this issue and found the root cause or maybe a way to deal with it so I can start my application again without overwriting the Exception?