Deleted documents are not removed from filesystem

[podz]

Hi,
I tried to find an answer in the administration part of the wiki, but no luck. I uploaded a few test documents, then deleted them but they do not get removed from the filesystem - even though I specified to delete all versions of this document.

-rw-r–r–  1 root root  311727 Dec 17 19:10 17e7e1b4-6f20-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root  311727 Dec 17 20:44 3034f867-6f2d-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root 2942605 Dec 17 17:17 305b4ae7-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     549 Dec 17 17:17 307c8e8f-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     690 Dec 17 17:17 308f0525-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     577 Dec 17 17:17 3091eb57-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root    1577 Dec 17 17:17 3093e729-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     293 Dec 17 17:17 3095e2fb-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     750 Dec 17 17:17 3098a21d-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     910 Dec 17 17:17 309a76df-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     682 Dec 17 17:17 309c72b1-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     537 Dec 17 17:17 309e4773-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     322 Dec 17 17:17 30a21805-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     652 Dec 17 17:17 30a43ae7-6f10-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root     138 Dec 17 17:39 5b03fabb-6f13-11da-8590-a36a31280dee.bin
-rw-r–r–  1 root root      13 Dec 17 17:41 94654f94-6f13-11da-8590-a36a31280dee.bin

I am a bit concerned about the disk usage growing and growing if deleted documents don't really get removed. Is this by design or is it a bug?

[a5sk4s]

I'm seeing the same problem with the server running on Windows XP / Tomcat 5.5.  This is a concern.  What is the status of it?

Thanks,

Andreas

[derek]

Hi,

I will be adding a scheduled job to the server to cleanup the unused content.  Unfortunately, due to the way that the version store handled content properties, it was not possible to do it reliably before.  One of the patches that execute upon upgrade to 1.2 will make it possible to identify all the content references in the metadata.

Regards

[derek]

http://www.alfresco.org/jira/browse/AR-34

The contentStoreCleanerTrigger bean from config/alfresco/scheduled-jobs-context.xml can be overridden to schedule the content for move to the content.deleted content store.

Regards