--- type: reference title: Media Relayout description: "Census, plan and apply the movie, TV, music and audiobook libraries: the gates, the refusals, the rollback." tags: [dankserver, media-server, jellyfin, plex, procedure] timestamp: 2026-10-30T00:00:00Z --- # Media Relayout The movie library on [[Entropy Volume]] arrived as release folders — `Some.Movie.2019.1080p.WiKiTaLx.x265-FOO/` with the video inside named after the release. [[Jellyfin]] matches a movie by folder and file name, so the release noise cost posters, extras and versions. These scripts turn that library into the shape its media server reads — the movies, the TV packs, the TV that turns up in the movie share, the music library, and the audiobooks, whose only reader is Plex — and nothing else in the repo touches a media file. | Script | Touches media? | Output | |---|---|---| | `scripts/media-census.py` | reads headers and the servers' own DBs, never writes | `enum`, `probed`, and one authority TSV per library | | `scripts/media-plan.py` | no — TSVs in, TSVs out | the plan + the exception report | | `scripts/media-apply.py` | **renames, never copies**; sweeps only what a run emptied | the moves, plus a journal | | `scripts/media-tv.py` | no — TSV out | a plan that moves TV into the TV library | | `scripts/media-shows.py` | no — TSV out | a plan that re-files the TV library itself | | `scripts/media-music.py` | no — TSV out | a plan that re-files the music library by its tags | | `scripts/media-audiobooks.py` | no — TSV out | a plan that re-files the audiobooks by the book Plex matched | | `scripts/media-verify.py` | no — reads the servers' DBs read-only | the verdict that every journaled move landed | The seams are `tests/media_relayout.bats`, `tests/media_shows.bats`, `tests/media_music.bats`, `tests/media_audiobooks.bats` and `tests/media_verify.bats`; the movie and TV target contracts are quoted from [jellyfin.org/docs/general/server/media/movies](https://jellyfin.org/docs/general/server/media/movies) in `media-plan.py`'s docstring. ## Procedure Run the census on the machine that mounts the library. `probe` is the slow step (a header read per container) and is `nice`d — it is safe beside a live service because it never competes for the GPU and never writes inside the library. ```bash C=scripts/media-census.py $C enumerate --root /mnt/entropy/Movies --out /tmp/media-enum.tsv $C probe --enum /tmp/media-enum.tsv --out /tmp/media-probed.tsv --jobs 6 $C plex --root /mnt/entropy/Movies --out /tmp/plex-movies.tsv ``` `plex` reads the Plex metadata cache (`--db` defaults to the path the [[Plex]] container bind-mounts at `/var/lib/plexmediaserver`) with plain `mode=ro`: a live server is never locked or written, and plain ro is also what makes a scan's uncheckpointed rows visible. The same rule as `scripts/media-verify.py` — see *Proving the move landed*. Then plan — this reads only the three TSVs, so it costs seconds and can run anywhere, including a laptop: ```bash scripts/media-plan.py --root /mnt/entropy/Movies \ --enum /tmp/media-enum.tsv --probed /tmp/media-probed.tsv \ --plex /tmp/plex-movies.tsv --out /tmp/jf-plan.tsv --exceptions /tmp/jf-exceptions.txt ``` **Read `/tmp/jf-exceptions.txt` before applying.** It is not a log: every line is a file the plan could not name a film for, a pile that needs a README, or a collision it refused. The printed gate lines are the go/no-go: `problems`, `bad-names`, `occupied`, `double-claim`, `left-unmoved` must all be 0 and `unplanned=0` must appear in the report. Any non-zero number means a file that would be filed wrong, and the plan is not run until it is understood. ```bash scripts/media-apply.py apply --plan /tmp/jf-plan.tsv --root /mnt/entropy/Movies # dry, writes nothing scripts/media-apply.py apply --plan /tmp/jf-plan.tsv --root /mnt/entropy/Movies --apply scripts/media-apply.py verify --plan /tmp/jf-plan.tsv --journal /mnt/entropy/media-relayout.jsonl scripts/media-apply.py sweep --journal /mnt/entropy/media-relayout.jsonl --root /mnt/entropy/Movies # dry scripts/media-apply.py sweep --journal /mnt/entropy/media-relayout.jsonl --root /mnt/entropy/Movies --apply scripts/media-apply.py rollback --journal /mnt/entropy/media-relayout.jsonl --root /mnt/entropy/Movies --apply ``` An apply also leaves the release folders it emptied standing where they were — hundreds of them at the library root — which is what `sweep` removes, dry-run first, from the same journal. After it lands, both servers need a scan or the change is invisible. [[Plex]] and [[Jellyfin]] own the exact requests; two laws hold at this step: `204` is acceptance and anything else queued nothing — re-issue the identical request rather than diagnosing — and ONE accepted refresh is the whole procedure, because a second while a scan runs moves `Scan Media Library` to `Cancelling` and every later `204` is accepted and then discarded. ### Proving the move landed A scan answers `204` whether or not it finds anything, so proof is the journal replayed against both servers' own tables: every `move` row has a row at its `dst`, and **zero** rows still name its `src`. `scripts/media-verify.py` is that replay: it opens each database read-only (there is no `sqlite3` binary on these hosts or inside either container) and exits non-zero while a row is stale. Both libraries live in WAL mode, so the tool opens them plain `mode=ro`: `immutable=1` promises sqlite the file never changes, which skips the write-ahead log — a scanner's own uncheckpointed rows then read as missing, and a read beside a running scan can fail as "database disk image is malformed". `immutable` stays only the fallback for a database whose `-shm` cannot be read. ```bash scripts/media-verify.py --journal /mnt/entropy/media-relayout-music.jsonl \ --db-kind jellyfin --ignore-ext jpg,jpeg,png,log,cue,toc,nfo,txt,m3u,accurip ``` "No row at the destination" is not one verdict but four. **never indexed**: the server indexes no file of that extension (its own extension census says so) — a sidecar, not a lost film. **gone**: the file sits at neither src nor dst, because a later pass or the server's own extension sweep renamed it. **phantom**: a row still naming src while the file has left src. **REAL**: no row at dst *and* the file still at src — the only class that is this relayout's own damage. Phantoms are normal for both servers (Plex carries thousands that predate any relayout); re-scan to clear them and never read them as loss. `media-verify.py` prints this split itself — `on disk at dst, no row names it`, `REAL — file still at src`, `gone — at neither path` — so nobody hand-stats a thousand paths to find out whether a film is lost or merely unindexed. The owning server decides whether a pass can convict anything: Plex's roots are its `sections` rows joined to their location rows (`Movies`, `TVShows`, `Music`, `Audiobooks`, `LiveRecording`) and Jellyfin holds no audiobook library at all, so the audiobook journal verifies with `--db-kind plex` or it proves nothing. Three doors that look right and are not: `GET /search?query=` matches metadata titles, never file paths; `?path=` on `/library/sections/N/all` makes Plex's HTTPD close without a single byte; and the same HTTPD drops requests that carry no `Accept` and client-identifier header (see the scan block above for the form that works). ## TV in the movie library A box set that arrives in the movie share stays there until someone moves it: `media-plan.py` refuses to file TV and parks each series in `_TV needs a TV library - `. `scripts/media-tv.py` is the mover. It walks the movie library itself (no census needed), groups episode-shaped names by series, and writes a plan in the executor's own format: ```bash scripts/media-tv.py --root /mnt/entropy/Movies --library /mnt/entropy/TVShows \ --out /mnt/entropy/media-tv-plan.tsv scripts/media-apply.py apply --plan /mnt/entropy/media-tv-plan.tsv --root /mnt/entropy scripts/media-apply.py apply --plan /mnt/entropy/media-tv-plan.tsv --root /mnt/entropy \ --journal /mnt/entropy/media-relayout-tv.jsonl --apply scripts/media-apply.py sweep --journal /mnt/entropy/media-relayout-tv.jsonl \ --root /mnt/entropy --apply ``` The shape it writes is the one both matchers read — `Monk (2002)/Season 05/ Monk - S05E03 - Mr. Monk and the Big Game.mkv` — keeping the file's own name, because the publisher's spelling beats a re-derivation, with the year taken from the box-set folder. What it refuses it prints and leaves alone: - fewer than `--min` (5) files under one series name: one file named `Part 2` is a film, not a series; - an episode whose name states no season number — no invented `Season 01`; - a destination two files both claim: the executor refuses the whole plan before its first rename, and only Frank decides which copy is the keeper. - an episode the destination library already holds at the same byte count. The movie share once carried a second copy of a whole box set — same episode list, every byte count identical. The mover leaves such a series in place and says so; a duplicate is deleted or kept by Frank, never copied into one library by a tool. A sidecar that shares an episode's own name (`.srt`, `.nfo`) moves with it. Below the threshold the mover prints and leaves, so a lone downloaded episode of a real show stays in the movie library on purpose. Filing one by hand is the same executor on a hand-written plan and the same journal; the trap is the series year. Read it from the file's own name or the folder it owns, never from the title whose bonus folder it happens to be parked in — `The Cleveland Show S03E07` inside `Die Hard (1988)/extras/` is not a 1988 show. A name whose marker is `Part 2` is a film and stays put. ## The TV library's own relayout `/mnt/entropy/TVShows` is scene packs rather than a library, and Jellyfin has already matched and numbered most of it. `scripts/media-shows.py` re-files that library into the shape Jellyfin reads, with **tvdb as the name authority**: () [tvdbid-NNNN]/Season NN/ () - SxxEyy - .ext It never guesses: every series name, episode number and title it writes traces to an authority, and what has none is parked for a human to read. ```bash # 1. The authority: Jellyfin's own matched rows — each carries the series' TMDb # and Tvdb ids and the title the row holds (the DB opens read-only). python3 scripts/media-census.py jellyfin --root /mnt/entropy/TVShows \ --out /tmp/tv_titles.tsv # 2. What is on disk (stat only), and the runtimes the film arm needs. python3 scripts/media-census.py enumerate --root /mnt/entropy/TVShows \ --out /tmp/tv_enum.tsv python3 scripts/media-census.py probe --root /mnt/entropy/TVShows \ --enum /tmp/tv_enum.tsv --jobs 6 --out /tmp/tv_probed.tsv # The probe is the slow step: ffprobe reads both ends of every file. So re-use # the last one — a duration belongs to the file, not to its name: re-key the # previous census through that pass's own journal (`src` -> `dst`) instead of # seeking the array again. It is also the only column the film arm reads, and # only for a file with no marker and no provider row (4,794 of 58,551 today, # all of them covered by a re-key that costs seconds, not an hour). # 3. The plan. --tmdb needs TMDB_API_KEY — the v3 key in ~/.config/secrets/tmdb, # which travels as the `api_key` query parameter. Only a v4 request token is # accepted as a Bearer header, and the wrong shape answers 401 on EVERY call, # which the summary line flags as NOT provider-complete. --tvdb reads its # `api_key=` line from ~/.config/secrets/tvdb, never argv. Both write the SAME # cache file, so the plan is reproducible offline afterwards: run it once to # fill the cache, and quote the second run. # Paths are only strings to a dry run, so this step can run on the workstation # against scp'd TSVs — which is where the two provider secrets live. python3 scripts/media-shows.py --root /mnt/entropy/TVShows --enum /tmp/tv_enum.tsv \ --titles /tmp/tv_titles.tsv --probed /tmp/tv_probed.tsv \ --tmdb-cache /mnt/entropy/media-tv-names.json --tmdb --tvdb \ --park /mnt/entropy/media-park/TVShows \ --out /mnt/entropy/media-relayout-shows2-plan.tsv \ --exceptions /mnt/entropy/media-relayout-shows2-exceptions.txt # 4. Read the exceptions file FIRST — it is the review, not a log. Same executor # as above, but on this arm's OWN journal, NAMED PER PASS: the journal of an # applied pass is its unwind record, so a second pass that reuses the name # destroys the only map back. scripts/media-apply.py apply --plan /mnt/entropy/media-relayout-shows2-plan.tsv \ --root /mnt/entropy --journal /mnt/entropy/media-relayout-shows2.jsonl --apply ``` Evidence, strongest first — the order the planner believes things: - the **episode marker the file's own name states** (`S01E02-E03`, `1x04`); - the **`Season NN` folder it sits in and the number its name leads with inside it**: `Season 19/01 Charles Barkley, Nirvana.avi` is S19E01; - the **provider row**: which episode the file IS, and the numbering of a file whose own name says nothing; - the **row's tvdb id, else its TMDb id carried through TMDb's external ids, else an exact tvdb name search**: that id names the SERIES FOLDER and supplies the episode title, because a name the server read off a folder is not a show name. The folder CARRIES the id: `[tvdbid-NNNN]` is what Jellyfin's Tvdb agent and Plex's scanner both read, so a show whose title is ambiguous resolves by number instead of by a human guessing which folder is which. The id rides the folder only — a file name gets 180 characters and the episode title needs the room. - a **bonus folder** anywhere above the file, or Jellyfin's `ExtraType` → the series' canonical extra folder; - a runtime over `SHORT_MAX` makes it film-shaped, and it leaves for `--movies` only when the movie provider's title is a run of words the FILE itself states and its year agrees with the file's: the query is only what `title_of` salvaged from a release name, and the first hit for a short one is a near miss — a 1963 Bond film for the word "russia", *Special Edition I* for a file saying *Edition III*. Else it parks. Four refusals carry the design: what the planner will NOT do is the point of it. - **Folders resolve a series; they never invent one.** A folder's words may resolve a file to a series a provider has already named — `(CBB) Tengen Toppa Gurren Lagann - The Complete Series (BD 1080p)` names the registered *Tengen Toppa Gurren Lagann* — but a bonus subfolder is not a show. An early run made `…/03. Extra/01. NCOP/NCOP 01.mkv` into a root series called `01 NCOP`. - **A scraped row does not outrank the filesystem.** Jellyfin numbers multi-season packs badly: every file under `SNL 16-20/Season 16..19` carries season 16 episode 20, and one Gundam row says season 2004. The folder, then the file's own leading number, win. - **A season that is a YEAR is the date matcher, not a season.** Jellyfin files specials by airdate, so a row can arrive saying `season 2002`; that is not a season and it never becomes a folder. The one authority on such a row is tvdb's episode list read backwards: the title the row carries names the (season, episode) tvdb gives it. A title tvdb gives to two episodes names nothing, and the file parks with the reason it always carried. `Season 00` IS a legal season — specials live there — so a row that really says 0 files there instead of parking. - **A season tvdb's own list contradicts gets no tvdb title.** An anime pack numbered by its release group books `S05E01` in a season tvdb does not hold, or books more episodes there than tvdb lists: the slot its number points at is a different episode, and dressing it in that episode's title is a confident lie. The file still renames to the standard shape; the title does not ride, and the series is listed under *seasons whose numbering tvdb contradicts* in the exceptions. A season holding FEWER files than tvdb lists stays plausible — a partial pack is the normal shape. Neither reading holds for a list tvdb cut off at its own page limit: the default episode query answers at most 500 rows and states no total, and One Piece, Crayon Shin-chan and Detective Conan each answer exactly 500 while holding over a thousand — a page bounds nothing above itself, so it contradicts nothing. **A provider name is evidence only when an id backs it.** Jellyfin names a Series after the folder it scanned, so a library filed by release folders ends up with one Series item per box set — `24 (2001) Season 1`, `Modern Family S05` — and copying those names verbatim launders folder junk into the contract. The planner resolves each series to its tvdb id and writes tvdb's name and year; the merged identity is also what turns a box set split across five release folders into ONE folder, and what makes two files claiming one episode MEET in the duplicate rule. A series no id resolves keeps the provider's words and is listed under *no tvdb identity* in the exceptions — that list, not a rename, is the review. **The review pile lives outside the library.** Files parked inside `/mnt/entropy/TVShows` were indexed as one show named `_unsorted`, and that show's rows then looked like evidence. So a row whose series is the hidden top-level folder the file itself sits in is dropped — and the folder is matched with its leading underscore stripped, because the server *displays* `_unsorted` as `unsorted`: compare the spelled names and the pile survives the relayout as a visible series folder that real files get renamed into. `--park` outside the root makes the next plan re-file the pile instead of skipping it. Inside a hidden top-level folder a file's own words may MATCH a registered show, never invent one. Release-group folder names are the one thing no provider can read, so the pending TVShows naming plan files 179 top-level directories (9,931 files) under the junk name they arrived with. A TVDB id map can name them, under the ladder's own acceptance rule: a hit counts only when TVDB's spelling equals the cleaned query, or differs from it by punctuation alone — the same letters are not a guess. Everything else is a choice for Frank, and the map is never applied unreviewed: `/mnt/entropy/media-relayout-shows-tvdb-proposal.tsv` carries one row per folder with `verdict` = `EXACT` / `PUNCT` / `NEAR` / `NONE` and a `note` naming the two traps — a folder marked `(US)` that matches the UK original, and several folders mapping to one id, which is a MERGE whose duplicate episodes the executor will refuse until a keeper is chosen. ## The music and audiobook arms Each is a page of its own, because each reads a different authority and refuses for a different reason: [[Media Music Relayout]] files by Jellyfin's track tags, [[Media Audiobook Relayout]] by Plex's chapter rows. Both share this page's executor, the one-journal-per-arm law, the sweep and the rollback. ## Laws - **A moved file is a 404 in [[Plex]] until its section is rescanned.** The database keeps the release-folder path, so playback fails `Couldn't find the file to stream` while the scanner works through the section. Never read such a 404 as a lost file: the file is where the journal says it is. - **Plex's matched title outranks the filename**, and a Plex year of `0` means *indexed but never matched* — trusting it named folders `Title (0)`, which is a Jellyfin item with no year, no poster and no identity. A year that is not a plausible year is no information. - **`<>:"/\|?*` never survive a name.** Plex's own title for *V/H/S/2* is `V/H/S/2`; kept verbatim it became `Movies/V/H/S/2 (2013)/` — a tree five levels deep that neither matcher reads as a movie. - **A folder inside a movie's folder is bonus territory even when its name is misspelled.** `Saboteur (1942)/Exrtas/Saboteur - A Closer Look` is a typo for `Extras`; the vocabulary rule never fired, the featurette became a movie folder, and its words then out-scored the real film and drew that box set's other extras into it. The rule that replaced it needs no metadata: the folder holding the longest film owns the shorter video filed under it, unless that file's own name carries a different year — which is another film speaking. - **Matching words are split on everything that is not a letter or a digit.** Splitting on separators but not on `/` left tokens like `(1960)/extras` that no other name could ever agree with, so a film could not be found by the folder holding it, and extras drifted into a neighbour. A bare number counts only when it could be a release year, so `1080` and `2160` never pose as agreement between two names. - **Compare two media libraries with the series engine, never a path substring.** Filtering paths for `monk` also returns *Monkey Dust*, and letting whichever file a walk happens to reach first stand for an episode paired two libraries into a fake duplicate — the same sloppiness pointed the other way deletes a file that is unique. The comparison is `media-titles.ep_of` on both sides: series, season, episode, bytes, and a hash before anything is trashed. - **A deletion is staged on the item's own filesystem.** The trash rule names `~/.AGENTTRASH`, but `/home` and `/mnt/entropy` are different devices: a 31 GiB stage there is a copy rather than a rename, it has to fit in the 187 GiB of free space, and `rename(2)` refuses it anyway. Trash goes beside the item — `/mnt/entropy/.AGENTTRASH/-/` — so it costs one inode change and rolls back exactly like the move that made it. - **A file whose name carries no words is bonus material, not a folder.** `.Extra 1 ( 1H 27min multisub ).mkv` parses to `1`; a movie folder named `1` is not a movie. It becomes a review line telling a human to name the file. - **The executor renames and nothing else.** `rename(2)` cannot cross a filesystem, so a plan that would is refused rather than silently copying tens of terabytes. - **The journal is a write-ahead log: the intent is fsynced before the rename.** An interrupted run therefore leaves only two states — an intent whose move happened, and an intent whose move never ran — and the next run finishes the job without moving anything twice. A file that moved with no journal line did not move through this tool, and the tool refuses to guess on its behalf. - **The journal lives BESIDE the library root, never inside it** (default: `media-relayout.jsonl` next to the root): a log inside the library is a file Jellyfin indexes. - **Refusals are all-or-nothing.** An occupied target, a vanished source or a duplicate destination stops the run *before the first rename*, so the operator fixes one thing and re-runs instead of untangling a half-applied plan. `--force` relaxes only the opinion guards; it never permits overwriting. - **A sweep deletes only what the journal proves the run emptied.** A folder is eligible when a journalled file moved out of it or out of something under it, it now holds nothing but empty directories, no journalled destination lives beneath it, and it is not a folder the run created. A folder nobody moved — someone's placeholder — cannot be selected at all, and a symlink anywhere inside disqualifies the subtree, because the thing behind a link is not this tool's to delete. Every removal is journalled as `rmdir` and `rollback` recreates the folder, so the sweep is undone by the same command as the moves. Proof carries downward: inside a folder the journal proves emptied, every empty directory goes with it. A release's `Screens/` or `Sample/` is never a move source itself, so it can hold an emptied parent until the next sweep. A failed `rmdir` is not a removal: only a folder that is really gone leaves scope, so the next sweep finishes what a permission problem stopped. - **An episode-shaped name marks a SERIES, not a film — and the series is the name BEFORE the marker.** `Monk - S05E03 - Mr. Monk and the Big Game` is series `Monk`. Keyed on the whole title instead, every episode became a group of one, never reaching the five-episode size that calls something a series — a whole box set filed as one folder per episode. The threshold still earns its keep: a lone film named `Part 2` stays a film. Episodes of a series are parked in `_TV needs a TV library - ` for a human to move to a TV source — the movie tool never files TV. - **One journal is one undo.** The TV move runs on its own journal, and with `--root` set to the share that holds BOTH libraries: the executor refuses any path outside `--root`, and a journal shared with the movie relayout would undo both runs when only one of them is wanted. - **Sidecar metadata does not follow a rename, because it lives on another filesystem.** The media servers write `.nfo` and artwork through the [[Media Metadata View]] (NVMe upper layer); this tool moves bytes on the raw array path, so where that view is mounted a sweep or a move must be followed by `scripts/media-view.sh reap --apply` — stranded sidecars become ghost folders that both servers browse and report as content. Whether this host mounts the view at all is stated on that page; `media-apply.py` stays silent when it does not. - **Nothing deletes through the metadata view.** A delete there writes an overlayfs whiteout in the upper layer, which hides the array's copy without removing it; the file returns when the view is unmounted. Deletions in this pipeline happen on the raw path only, which is what the journal can undo. - **The music album key is case-folded; the folder name is not.** `Master Of Puppets` and `Master of Puppets` are one album to the matcher, so the spelling that reaches the folder is the one most tracks carry. Taking it from whichever row sorted first made the folder name depend on row order, and re-planning an already-filed library renamed albums that were already in place. - **An occupied path is never a destination**, not even when its occupant is scheduled to leave: the executor refuses an occupied target, so a plan that aims at one fails after the renames that were supposed to clear it. A file standing where the contract puts it is a keep, and a file already carrying a collision suffix keeps that suffix — otherwise the plan is a shuffle, not a fixed point, and a re-run moves albums that are already right. - **`media-census.py music` reads the `BaseItemProviders` table, not the item's JSON.** This Jellyfin build carries an empty `ProviderIds` inside `BaseItems.Data` for albums, so a census that parses the JSON finds no MusicBrainz or Spotify id on any album and reads as "the library is untagged". ## Rollback One command, from the journal of the run: `media-apply.py rollback --journal …/media-relayout.jsonl --apply`. It recreates any folder a sweep removed, restores every source path, removes only the folders that run created *and that are now empty*, and refuses everything if any moved file cannot be accounted for. A rolled-back journal refuses to roll back twice. **Roll a chain back newest journal first, or the tool refuses.** Each pass re-files what an earlier one moved, so a journal is a clean inverse only until something downstream touches its files; `ls -l /mnt/entropy/media-relayout*.jsonl` is the order. Refusing is the tool working: on 2026-10-31 the movie journal could not restore files the later TV passes had re-filed, and the stray journal could not restore files Jellyfin's extension sweep had renamed. Roll back what still inverts and leave the rest as the current state — never force it. ## See Also [[Jellyfin]], [[Plex]], [[Media Metadata View]], [[Entropy Volume]], [[Testing Policy]], [[Storage Policy]] ## Citations - Jellyfin Movie documentation — folder/file naming, extras subfolders, `Movie (2013) - 216p.mkv` version and `- 4K.mkv` handling: