mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
[Issue]: Jellyfin delete season folder after library scan #5943
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#5943
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pafade89 on GitHub (Jun 6, 2024).
Please describe your bug
After adding my existing series and performing a library scan, Jellyfin deleted all seasons of the series. Since these are anime, I thought I was affected by a current bug #11954. However, that wasn't the problem, as the behavior still occurs even after updating to version 10.9.5. My current solution is to mnt my NAS with read only.
Reproduction Steps
Jellyfin Version
10.9.0
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@gnattu commented on GitHub (Jun 6, 2024):
Check your version again, are you running on 10.9.5?
@pafade89 commented on GitHub (Jun 6, 2024):
@Shadowghost commented on GitHub (Jun 6, 2024):
I checked all the possible code paths leading to this log message and I can't see how this could have been triggered on 10.9.5 without someone manually calling the DeleteItem API endpoint. E.g. going to the series -> three dot menu -> delete item on the WebUI
@pafade89 commented on GitHub (Jun 6, 2024):
Thanks for quick reply.
I have checked everything again and shut down all LXCs that work with the Jellyfin API.
Same behaviour
I am testing this by manually placing the data in the mounted directory and then initiating a library scan through the web UI.
@Shadowghost commented on GitHub (Jun 6, 2024):
Are you by any chance using the tvdb plugin?
https://github.com/jellyfin/jellyfin-plugin-tvdb/pull/153 was merged but not released, fixing a similar bug in there
@pafade89 commented on GitHub (Jun 6, 2024):
I have now removed the stable plugin repository and deleted TVDB plugin. Now my series with episodes remain intact/not deleted and the messages in the log are gone. Thank you very much.
When will this fix be implemented and released in the stable version of Jellyfin TheTVDB Plugin?
@pafade89 commented on GitHub (Jun 6, 2024):
When I deinstall the tvdbb plugin and restart jellyfin it looks like the following:
If I now restart jellyfin again it looks like this:
Without removing the stable default repository it is not possible to deinstall the tvdb plugin.
Im wondering that a metadata plugin can delete files and reinstall completely automatically. Is this wanted?
@Shadowghost commented on GitHub (Jun 6, 2024):
Inside
system.xmlin your config folder should be the stanza<RemoveOldPlugins>set this to true, restart, uninstall the plugin again and restart again. Any future plugin update will now remove old versions.You can always remove old versions manually by deleting the respective directories in the
pluginsfolder@pafade89 commented on GitHub (Jun 6, 2024):
That worked, thank you very much. However, one question remains:
Im wondering that a metadata plugin can delete files completely automatically. Is this wanted/necessary?
@Shadowghost commented on GitHub (Jun 6, 2024):
Plugins can do more or less anything the server can, so it is intended behaviour that they can do it but it's up to the plugin to use it properly/at all.
@pafade89 commented on GitHub (Jun 6, 2024):
Okay, thank you very much for your time and quick reply. I hope the update comes as soon as possible to prevent further data loss.