35 lines
1.0 KiB
Markdown
35 lines
1.0 KiB
Markdown
---
|
|
title: Media Pipeline Pitfalls
|
|
created: '2026-05-23'
|
|
updated: '2026-05-23'
|
|
type: tech
|
|
namespace: family
|
|
tags: [media-pipeline, pitfalls, torrents, infra]
|
|
related: "[[arr-stack-kraken]]"
|
|
---
|
|
|
|
# Media Pipeline Pitfalls
|
|
|
|
## Torrents — Do Not Rename Files
|
|
|
|
Never rename torrent source files or folders while a torrent is active.
|
|
Transmission tracks files by path. Renaming breaks the association and
|
|
causes re-download or stalled seeding.
|
|
|
|
## torrent-set-location Updates downloadDir
|
|
|
|
`torrent-set-location` in the Transmission RPC updates `downloadDir` in
|
|
the torrent metadata. Use this when moving completed files, not a manual
|
|
rename. Sequence:
|
|
|
|
1. Move files to new location on disk
|
|
2. Call `torrent-set-location` with the new path + `move=false`
|
|
3. Verify torrent goes back to seeding state
|
|
|
|
## General Rules
|
|
|
|
- Never touch source files/folders (media-pipeline USER.md rule)
|
|
- `resolve-manual` is emergency-only
|
|
- NFO files: do not create manually; let the pipeline handle them
|
|
- Never delete test files from the pipeline project
|