Hello everyone,
I'm currently using dcm4chee along with S3 as the storage backend for DICOM files. Occasionally, I run into issues when trying to open a study. When I investigate the image file in S3, I find that it has a delete marker.
The image instance still appears in dcm4chee, but when I follow its path in S3, the object is marked as deleted. Fortunately, I have versioning enabled in S3, so I'm able to recover the file. However, I can't figure out why this is happening in the first place.
Has anyone experienced something similar or have any ideas on what could be causing these delete markers?
Hi everyone,
Just following up on my previous messages from a few days ago regarding deleted objects in S3 that still appear in dcm4chee.
I'm still trying to understand what might be causing these delete markers to appear on some DICOM files — especially since versioning is enabled and the corresponding instances remain in the database.
Could this be the result of a failed internal process (like compression, migration, or cleanup)? Or is there something else I might be overlooking?
Any insights or similar experiences would be greatly appreciated. Thanks in advance!
Best regards,