Instruction 04-sonarr-naming-and-library-hygiene: Reading

Sonarr is not merely a downloader; it maintains a database that maps a series, season, episode, quality, and release history to files in a managed library. Good naming makes that relationship visible even when the database, application, or backup catalog is unavailable. A durable episode name normally includes a recognizable series title, season and episode numbering, an episode title when available, quality information, and release-group information when Sonarr can parse it. Including the series year in the series folder is especially useful when two productions share a title. The exact template is a policy choice, but consistency is more important than cosmetic preferences.

The download directory and library root must be treated as separate logical roles. A download client owns its active and completed job paths. Sonarr imports from those paths into a root folder that it manages. Pointing both applications at the same undifferentiated directory can leave release folders in the library, expose partial downloads to media servers, and make cleanup unsafe. In a container deployment, the paths visible inside each container may differ from host paths; Sonarr must still be able to resolve the path reported by the download client. Remote path mappings are translation rules for genuinely different path views, not a general repair for poor volume layout.

Import behavior depends on filesystem topology and download state. A completed torrent that must continue seeding is commonly hardlinked into the library when the source and destination are on the same filesystem and hardlinks are enabled. If hardlinking is impossible, import may copy the file, consuming additional storage. A completed non-seeding download can often be moved. Moving within one filesystem can be effectively instantaneous because only directory metadata changes, while moving across filesystems normally becomes a copy followed by source removal. Operators should validate mount points and link counts instead of assuming an import method from how quickly it appeared.

Renaming should be performed through Sonarr when the files belong to a managed series. An external bulk rename can leave Sonarr's stored path stale until a scan, can erase release metadata, and can create collisions. Before any production rename, preview the proposed names, confirm that multi-episode files remain identifiable, check free space and backups, and test one series. Naming tokens cannot recover information that was never parsed, so preserving the original release title in history and retaining release-group and quality tokens are useful safeguards.

Library hygiene also means detecting orphaned season folders, duplicate episode identities, unexpected extensions, samples, files stored directly under a root, and paths that differ only by case. No single filename audit proves that media content is correct; filenames provide evidence, while Sonarr's episode mapping, media analysis, and operator review establish confidence. The lab therefore uses harmless text fixtures to practice classification and previewing without touching a real Sonarr instance or media library.