mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
[Issue]: Every time my libraries are scanned, the same items are "removed" #5987
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#5987
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 @SteveDinn on GitHub (Jun 10, 2024).
Please describe your bug
Each time a scheduled library scan is run, I see the same entries in my logs that certain items are being "removed". One would naturally assume that once items are removed, they would not have to be removed again as part of subsequent scans.
I don't know particularly how I got these particular items in my library in the first place as they are not media files, but "studio" items. It might be because they all appear to have accented or otherwise non-standard characters in their names (see attached logs)?
Reproduction Steps
I don't have precise replication steps for this issue because I didn't do something specific that made it happen, I just noticed it when inspecting the server's logs.
Jellyfin Version
10.9.0
if other:
10.9.6
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
@jellyfin-bot commented on GitHub (Jun 10, 2024):
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
@SteveDinn commented on GitHub (Jun 10, 2024):
For what it's worth, the file or directory that the logs are referencing do not appear to exist, i.e.,
/config/metadata/Studio/Versátil Cinema.@millallo commented on GitHub (Jun 12, 2024):
same problem on every scan:
@gummykage commented on GitHub (Jun 12, 2024):
Having same issue.
@PhilAllmighty commented on GitHub (Jun 15, 2024):
same
@simoncaron commented on GitHub (Jun 17, 2024):
I'm seeing something similar in the logs on my instance too on 10.9.6 (docker version).
Studios are logged as deleted on each scan. One common thing about all the studios I see is that they all have non-ASCII characters in their names, most of the time "é" in my case:
@ghdoca commented on GitHub (Sep 4, 2024):
Same issue here. Problematic Non-ASCII characters:
Emby.Server.Implementations.Library.LibraryManager: Removing item, Type: "Studio", Name: "Deutscher Filmförderfonds", Path: Emby.Server.Implementations.Library.LibraryManager: Removing item, Type: "Studio", Name: "France 2 Cinéma", Path: "/config/metadata/Studio/France 2 Cinéma"
Emby.Server.Implementations.Library.LibraryManager: Removing item, Type: "Studio", Name: "France 3 Cinéma", Path: "/config/metadata/Studio/France 3 Cinéma"
Emby.Server.Implementations.Library.Validators.StudiosValidator: Deleting dead "Studio" "" "Fünfte Babelsberg Film"
@StaticRocket commented on GitHub (Sep 28, 2024):
Adding this just to note it is not directly related to non-ascii characters:
Getting this on every scan as well. Ah, but in this case it is a MusicArtist not a Studio.
@vzvl commented on GitHub (Sep 30, 2024):
Same here. Upon every library scan the same non-existing files are being removed. I am wondering if this has to something with jellyseerr and the *arr suite writing to the library folders or is this a metadata problem, i.e. retrieving false metadata for existing files (e.g. Rings of Power episodes) and then deleting the wrong meta data again?
[10:47:23] [INF] [51] Emby.Server.Implementations.Library.LibraryManager: Removing item, Type: Episode, Name: The Making of The Rings of Power - Episode 5, Path: , Id: 71640c2b-73ca-cf40-9900-6a8a000be7fe[10:47:23] [INF] [51] Emby.Server.Implementations.Library.LibraryManager: Removing item, Type: Episode, Name: The Making of The Rings of Power - Episode 6, Path: , Id: 168f980d-7de6-bebe-c317-e0367c129b41[10:47:23] [INF] [51] Emby.Server.Implementations.Library.LibraryManager: Removing item, Type: Episode, Name: The Making of The Rings of Power - Episode 7, Path: , Id: 6ca2264a-adf4-da7f-d6e0-7182a77d2ec9[10:47:23] [INF] [51] Emby.Server.Implementations.Library.LibraryManager: Removing item, Type: Episode, Name: The Making of The Rings of Power - Episode 8, Path: , Id: 1dbd2b48-aa73-a7a3-94ad-4695ca7164ac@brianjmurrell commented on GitHub (Oct 28, 2024):
I am also seeing this with
Type: Episodefiles. Here's how many times JF has removed just a single one:Just noticing that I see it with
Type: Seriesalso.I'm on JF 10.10.0.
@jwestrom commented on GitHub (Jan 16, 2025):
I've also noticed this behvaiour on version 10.10.3
@jellyfin-bot commented on GitHub (May 17, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jwestrom commented on GitHub (May 18, 2025):
This is still an issue in 10.10.6
@Vesan-git commented on GitHub (Aug 16, 2025):
Same on version 10.10.7. Lot's of things are "removed" after a simple rescan.
@jellyfin-bot commented on GitHub (Dec 15, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.