Deleted files stay in repository?

[flood78]

Hello,

This is maybe a stupid question, but why when I delete a file, it is still in the repository folder? This, even when I empty the trash (Purge Trash).

I was trying OpenKM for the first time, imported a big folder and finally I decided that I will not keep it.
So I delete it but all the files was still in the repository folder /opt/OpenKM/repository/repository/datastore
I did some test with only one file and it's the same all the time...
1. is there a way to do a cleanup?
2. is it deleted automatically someday?



Thanks to clear me on that point.

[jllort]

It's a jackrabbit problem, the garbage is still on repository. In migration process it'll not be migrated. I think newer jackrabbit version that we've got in OpenKM 5.0 has not this problem, for some reason jackrabbit people was decided to maintaining deleted files, but that can not be recovered, reason why mantaining has no sense. In newer version I think it's yet solved.

[flood78]

Ok, but will the new files overwrite the old one or we loose the space forever? It's pretty weird... i don't understand the logic in this.
Do I miss a step when using OpenKM?

[jllort]

I think you're confused, when i file is definitively deleted can not be recovered, but in older jackrabbit version ( present in OpenKM 4.x and older ) continues consuming space. When document is definitively deleted not exists for anything.

Each new file consumes new space.

[Odera]

Hello,

This thread caught my eye because I want to retain/recover deleted files. IMHO all deleted dirs/files should be visible and recoverable by the Admin (simply marked "Deleted" in the DB). Any chance to make this a configurable feature?

[jllort]

Yes it can be done, it's not complicate, it could be a simply change in delete logic that could be a move to administrator trash.

But it's not good idea arrived some moment to delete some documents definitively ... garvage in your repository is garvage

[pavila]

This was already fixed in OpenKM 5.0 (and 5.0.1, of course).

[marthin.vandyk.cod]

Hi,

The same thing is happening with me still. Purging the files but it stays the repository? There is a scheduled task running from what I can see in the logs, but it is throwing an error. Googling there are reports that it is informational only, but not sure about it regarding the symptom I am experiencing:

Code: Select all

02:34:11,905 INFO  [MultiIndex] Unable to delete obsolete index: _x

How would we verify that the Trash will be cleared out? From browsing the repository it does not seem to be.

We are using OpenKM-5.1.7_JBoss-4.2.3.GA.zip on Ubuntu 10.04.3 LTS.

Many thanks.

rgds
Marthin

[pavila]

By default, OpenKM is configured to use a file DataStore located at $JBOSS_HOME/repository/repository/datastore. Simply make a "find -type f | wc -l" from this directory to get the number of document in repository. Delete a couple of them, wait to the night daemon which purge the orphan datastore files. and run the "find -type f | wc -l" again. You should see less files.

[marthin.vandyk.cod]

Perfect, thanks for the hint. I will do the test and provide result.

[CycloneBird]

Hello there,

I also have this problem with the files still in the repository after purging the trash. Is there a way to get rid of them?

I am using OpenKM 5.1 With Windows XP.

Thanks

[pavila]

As commented previously in this thread (and in other threads in this forum) the orphaned document reference cleanup process is excuted every midnight and this process will take care of the deleted documents and will remove from the Datastore. If you want to force the execution of this process, run from administration scripting:

Code: Select all

new com.openkm.core.DataStoreGarbageCollector().run();

If after that the documents are still in the datastore, please post here the steps to reproduce the issue and I will add this to our bug tracking system (http://issues.openkm.com/).