Coutar
March 21, 2019, 9:48pm
1
Hi,
I’ve recently rebuilt by OMV hence a new docker and a new sonarr.
But this time, I’ve set the config for sonarr to be a CIFS share located on a NAS.
this folder has been set with guest write/read access.
Mounted on OMV using remote mount, PUID and PGID are correct, but when starting sonarr, it kept complaining with the following error
[v2.0.0.5301] NzbDrone.Core.Datastore.CorruptDatabaseException: Database file: /config/nzbdrone.db is corrupt, restore from backup if available. See: https://github.com/Sonarr/Sonarr/wiki/FAQ#i-am-getting-an-error-database-disk-image-is-malformed —> System.Data.SQLite.SQLiteException: database is locked
database is locked
I’ve googled around, but everyone that had the same problem seems to have config folder within the same container as sonarr.
I’ve even set PGID and PUID to be 0 as root, still to no avail.
please help. Thanks
Don’t do that, SQLite over network shares is going to be a bad time.
opened 05:32AM - 01 May 17 UTC
closed 02:17PM - 18 Nov 20 UTC
bug
priority:medium
platform: windows
platform: linux
Sonarr currently uses WAL mode for journals with SQLite. WAL mode has some adva… ntages, but one major disadvantage is that it *can not* safely be used over non-local filesystems (https://sqlite.org/wal.html); docker for windows and other virtualization systems using CIFS mounted host paths often fail with sqlite locking or corruption errors when using WAL with sqlite file on host shared paths.
Providing an option to disable WAL mode (perhaps using standard DELETE mode) for transactions would be very useful for virtualizing Sonarr, or other cases where the config files and sqlite databases need to live on a SMB/CIFS/NFS path.
Could we have some sort of config file option or command line option that disables WAL mode journaling throughout the program?
This was already addressed for OSX in #167 - may as well just make it an advanced option, so we can set it when needed, and by default on OSX.
It’s a corrupt database, it doesn’t matter where you’re storing it. Restoring a backup is your best bet, but you may be able to repair it manually.
system
Closed
May 21, 2019, 12:40pm
4
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.