Document content of version 1 is missing

[atari freak]

hey,
i just updated my 4.3 to 5.0.3 (quickinstallation with mysql config).
everything worked fine until i get this error (Document deleted...)

what i remember doing:

1. working with no problem
2. renaming a type on Document name (change ÜBung zu Übung) -> Error Contact Admin.. hmm, thats me..)
3. can read and upload Documents again with no problem. Document of 2. was renamed successfull.
4. change a username
5. selected a docroot for her in admin/user settings)
6. logged in as this user with admin function "change user" ( tried loggin in and out too...)
7. access error, because on / accessrights where set to no
8. go back to admin account
9. change root-DMS setting to read only
10. change user again (as in 6)
11. login working
12. access user files, but not opening a file (...)
13. reindexing users home-folder (as set in 5)
14. try to open a file: error

since then i can not open any file.
I hoped it was only on that file but its globaly on all my documents.

I tried chmod 777 on data-Folder already. Not helping :-(

Anything else I can try?

[atari freak]

just answering myself:

DO NOT CHANGE maxDirID="0"in your setings!

I had this and i changed it to default 37200 which is BAD!

I guess this SHOULD be changed in settings.xml.template:
- maxDirID: Maximum number of sub-directories per parent directory. Default: 32700.

In settings.xml its this:

- maxDirID: Maximum number of sub-directories per parent directory. Default: 0, use 31998 (maximum number of dirs in ext3) for a multi level content directory.

and below there is this line in both files:

<server coreDir="" luceneClassDir="" contentOffsetDir="1048576" maxDirID="0" updateNotifyTime="86400" extraPath="" maxExecutionTime="30" cmdTimeout="1"/>

so, default of maxDirID is what?
and why do this afect document access?

[Uwe Steinmann]

maxDirID has been introduced because some file systems have a limit on subdirectories. As each document has its own subdirectory on disk, this would limit the maximum number of documents. Setting maxDirID to something != 0 will create at most maxDirID subdirs for documents but forces a two level hierarchy. The first document will be put into directory 1/1, the second into 1/2 on so on untill
1/maxDirID. The document maxDirID+1 will then be in 2/1 . This will allow pow(maxDirID, 2) documents.

Best is to use ext4 and keep maxDirID at 0.

You are right, claiming that 32760 is the default is a bad idea. I'll fix that.