Older documents not available anymore

[Daniel]

Hi,

Just noted a problem within my LetoDMS installation today. I recently upgraded to version 3.3.3 but didn't noted any problem. Now i wanted to check an old document and it just shows "Document deleted". The file on the filesystem is still present and the database entries are looking correctly for me. Each entry in tblDocumentContent has it's corresponding file entry.

If i upload everything looks fine. Only doucments before the upgrade to 3.3.3 are gone.

Any idea how to restore the associations to the files without rolling back to 3.3.0?

Thank you in advance and best Regards
Daniel

[Daniel]

Just restored my 3.3.0 installation and all the documents are accessible again. Only the one that i added with 3.3.3 is shown as deleted.

I checked the install source again and found no update package for the database. Did i miss something during the update?

Btw: I just replaced the installation files, i didn't touch the data directory, the conf directory or the database.

If there is any fix let me know and i try it out on my development instance.

Regards

[steinm]

Just restored my 3.3.0 installation and all the documents are accessible again. Only the one that i added with 3.3.3 is shown as deleted.

I checked the install source again and found no update package for the database. Did i miss something during the update?

Btw: I just replaced the installation files, i didn't touch the data directory, the conf directory or the database.

If there is any fix let me know and i try it out on my development instance.

On what value is maxDirID set? If is != 0 the layout of the documents on disk has changed to overcome the limit of 31998 subdirs per directory (for ext3). In such a case a second layer of subdirs is used. Your new documents will most likely be in a directory content/1048576/<x>/<docdir>. The easiest would be to set maxDirID to 0 and move these dirs back into content/1048576

Uwe

[Daniel]

Just restored my 3.3.0 installation and all the documents are accessible again. Only the one that i added with 3.3.3 is shown as deleted.

I checked the install source again and found no update package for the database. Did i miss something during the update?

Btw: I just replaced the installation files, i didn't touch the data directory, the conf directory or the database.

If there is any fix let me know and i try it out on my development instance.

On what value is maxDirID set? If is != 0 the layout of the documents on disk has changed to overcome the limit of 31998 subdirs per directory (for ext3). In such a case a second layer of subdirs is used. Your new documents will most likely be in a directory content/1048576/<x>/<docdir>. The easiest would be to set maxDirID to 0 and move these dirs back into content/1048576

Uwe

Hi Uwe,

The setting is currently 32700.

PHP Code:

contentOffsetDir="1048576" maxDirID="32700" 


Currently i have 492 Files within the DMS. The filesystem is ext4.

What i don't understand, why it works again with 3.3.0? Is there a change in 3.3.3 that affects the handling of files?

Regards
Daniel

[steinm]

The setting is currently 32700.

PHP Code:

contentOffsetDir="1048576" maxDirID="32700" 


Currently i have 492 Files within the DMS. The filesystem is ext4.

What i don't understand, why it works again with 3.3.0? Is there a change in 3.3.3 that affects the handling of files?

The 'multi level content directory' was introduced in 3.3.0. So indeed, it should have shown up in that version already. There was a bug which was fixed in 3.3.3. That might be the reason for the different (but correct) behaviour in 3.3.3. If you need help to fix the content directory, let me know. I guess the new documents are just put into the directory 1048576/1. Moving them out of there into the parent directory and setting maxDirID to 0 should fix it.

Uwe

[Daniel]

The setting is currently 32700.

PHP Code:

contentOffsetDir="1048576" maxDirID="32700" 


Currently i have 492 Files within the DMS. The filesystem is ext4.

What i don't understand, why it works again with 3.3.0? Is there a change in 3.3.3 that affects the handling of files?

The 'multi level content directory' was introduced in 3.3.0. So indeed, it should have shown up in that version already. There was a bug which was fixed in 3.3.3. That might be the reason for the different (but correct) behaviour in 3.3.3. If you need help to fix the content directory, let me know. I guess the new documents are just put into the directory 1048576/1. Moving them out of there into the parent directory and setting maxDirID to 0 should fix it.

Uwe

Thanks Uwe. I will remigrate my test system to 3.3.3 and see what happens. Let you know the outcome.

If we can solve it this way it may be a good idea to put it somewhere to the FAQ's as other people may also run into this issue.

Daniel

---

Ok, tried it out. Works like a charm, will migrate my productive system to 3.3.3 again.

Thank you for your help in this.
Daniel