Dcm4chee deleting dicom entries.

78 views
Skip to first unread message

Andreiver Mateus

unread,
May 13, 2025, 9:52:38 AMMay 13
to dcm4che

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? 

Andreiver Mateus

unread,
May 13, 2025, 9:57:56 AMMay 13
to dcm4che
Also, what processes could lead to the automatic deletion of image files without removing the corresponding instance from the database?

Andreiver Mateus

unread,
May 13, 2025, 10:11:48 AMMay 13
to dcm4che

Is it possible that this deletion is caused by a process in dcm4chee, but the process failed and the image was lost? Could it be related to tasks like compression or others?

Andreiver Mateus

unread,
May 19, 2025, 7:41:00 AMMay 19
to dcm4che

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,

Reply all
Reply to author
Forward
0 new messages