Problem using the new sqlite index db

[Aaper]

Description
We use the newst filebrowser version (1.2.1) in a large environment with many folders and files on different shares

Expected behaviour
The filebrowser is expected to work reliable like the older versions

What is happening instead?
When the size of the db increases, the filebrowser isn't able to start anymore. The only workaround is to use the config entry

server:
  cacheDirCleanup: true
  indexSqlConfig:
    disableReuse: true

so it creates a new db every time it restarts. But after a while of running the db is so big that the frontend isn't working anymore and only shows Http 504 codes
Additional context
The index db is about 12GB in size

How to reproduce?

Files

[gtsteffaniak]

thanks for opening this issue, can you provide any logs when you say "filebrowser isn't able to start anymore" ?

And you mention the workaround above, but if theres a situation the db us unusable on startup, a new sqlite database is automatically created and should show in logs a message about a corrupted database.

12GB in size is quite large, can you enable debug logging and show whats happening?