Expunge - doesn't fully expunge? Possible bug in DSpace version 9.1

[Katy Earl]

Hi,

I am trying to understand the expunge feature in DSpace and why the assetstore doesn't empty after expunging and running bin/dspace cleanup. It seems there are many artifacts left behind even though cleanup tells me that there aren't. 

I needed to wipe my test instance of DSpace and used a CSV file to expunge contents of each collection/community and then deleted each collection and community and then went to the command line and ran bin/dspace cleanup. Before doing the expunge, my assetstore was 11GB. After running expunge and cleanup, the assetstore was 7GB. I looked through a few of the remaining bitstreams and I could see PDFs. I could look further, if it helps, to see if it is only imported documents or also full text or thumbnails. Not sure that would make a difference?

Is this expected? I am concerned about system bloat. This was just a test instance, our real instance is about 100x the size. I don't want to potentially have 700GB worth of data that I don't want... That is a lot of disk space to take up unnecessarily.

Best,

Katy