2024-07-07, 02:14 AM
I have been having some difficulty with MergeVersions which I linked back to a problem with library.db. Due to some mounting problems, my default folder path for my Movie and TV directories had changed, so I updated the respective folders for each library to the new mount location (we'll call the move /media1/ -> /media2/ for reference), making sure to remove the old folder in the process. However once MergeVersions ran, it created duplicate entries for every single file (so a file with 2 versions now had 4 versions, 2 pointing to an invalid location). So I split the versions again and uninstalled MergeVersions, and the duplicates went away.
After that I did a full rescan on each library (using replace all metadata), cleared the cache, and optimized the db. Reinstalled MergeVersions again, and the same thing happens. I ended up opening library.db in DB Browser which MergeVersions was calling from, and found all of the original entries pointing to /media1/ in addition to /media2/. So while the nonexistent old files do not appear in Jellyfin, they clearly still exist within library.db in addition to the new ones, and MergeVersions is using library.db to determine which files have multiple versions.
It's worth mentioning I've run all scheduled tasks and done the full scan on every library, and it still doesn't clean up those nonexistent entries in library.db. For reference I am running Jellyfin 10.9.7 debian build. How can I clean up these entries so that MergeVersions and other plugins will not create duplicates referencing the old nonexistent path? I'd rather not have to edit these entries manually in DB Browser out of fear of screwing something up.
After that I did a full rescan on each library (using replace all metadata), cleared the cache, and optimized the db. Reinstalled MergeVersions again, and the same thing happens. I ended up opening library.db in DB Browser which MergeVersions was calling from, and found all of the original entries pointing to /media1/ in addition to /media2/. So while the nonexistent old files do not appear in Jellyfin, they clearly still exist within library.db in addition to the new ones, and MergeVersions is using library.db to determine which files have multiple versions.
It's worth mentioning I've run all scheduled tasks and done the full scan on every library, and it still doesn't clean up those nonexistent entries in library.db. For reference I am running Jellyfin 10.9.7 debian build. How can I clean up these entries so that MergeVersions and other plugins will not create duplicates referencing the old nonexistent path? I'd rather not have to edit these entries manually in DB Browser out of fear of screwing something up.