From a5603d8f01e15906e5727ffbe091c920f1884edc Mon Sep 17 00:00:00 2001 From: Frank Date: Mon, 2 Nov 2026 18:52:13 -0800 Subject: [PATCH] - --- serverAppConfigs-docs/Dankserver/Jellyfin.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/serverAppConfigs-docs/Dankserver/Jellyfin.md b/serverAppConfigs-docs/Dankserver/Jellyfin.md index 6c322e2..14ed8c0 100644 --- a/serverAppConfigs-docs/Dankserver/Jellyfin.md +++ b/serverAppConfigs-docs/Dankserver/Jellyfin.md @@ -64,6 +64,17 @@ everything filed there is invisible to Jellyfin by configuration, not by fault: a recursive refresh answers 204, burns CPU for minutes and indexes nothing, because it never looks there. Check coverage before re-scanning. +**Which read proves an item is indexed: the folder view, never the recursive type +list.** `GET /Items?IncludeItemTypes=Movie&Recursive=true` answered 2,101 items on +2026-11-03 while `GET /Items?ParentId=` listed 2,548 children — every +folder on disk — and the eight folders the recursive read "lost" (three `Gundam 00 +Special Edition`, five `Sailor Moon Memorial`) each answer as `Type: Movie` through +`SearchTerm` and sit in the folder listing. The two reads are not interchangeable, so +the recursive list is a wrong instrument for "did the refresh index what I moved": its +shortfall is grouping, not missing media, and acting on it starts a scan that fixes +nothing. Verify per item — `ParentId` listing or `SearchTerm` — and use the recursive +count only as a trend line. + **Failure signature:** `System.IO.IOException: Read-only file system : '/data/Movies//movie.nfo'` means the container is binding the raw array instead of the view — always a fault on this host since the 2026-10-31 cutover. -- 2.54.0