FailedProxy/Varaverk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bring the seed docs in line with Phase 3

Browse Source
This commit is contained in:
Gmer4Lfe
2026-08-17 10:24:41 -04:00
parent 7c957d96be
commit 42711ff9ac
4 changed files with 25 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Rsync/README-Rsync.md
+11 -6
View File
@@ -104,18 +104,23 @@ For full profile definitions see `Manual-Rsync.md`.
| Script | Role | When It Runs |
|--------|------|-------------|
| `rsync.sh` | Core transfer engine — profile resolution, pre-flights, container management, transfer, bandwidth logging | Called by orchestrators; directly for manual syncs |
| `media_seed.sh` | First-fill of a new partner — loops every `DAILY_SYNC_SHARES` entry through `rsync.sh --seed` | Dispatched detached by partnership onboard Step 13; restartable from the Partnership tab |
| `media_seed.sh` | First-fill of a new partner — loops every `DAILY_SYNC_SHARES` entry through `rsync.sh --seed` | Phase 3 — dispatched by `partnership_onboard.sh --phase3-only`, triggered from the Partnership tab |
`media_seed.sh` is the one script here that is expected to run for weeks. A first seed of
HOST1's library is ~28 TB against a 12.5 MB/s `--bwlimit`, which is why onboard dispatches it
rather than waiting on it, and why the Partnership tab gives it a Stop button — `rsync.sh` runs
`--inplace --partial`, so stopping costs the file in flight, not the share.
HOST1's library is ~28 TB against a 12.5 MB/s `--bwlimit`, which is why it is a phase of its own
rather than a step inside the onboard, and why the Partnership tab gives it a Stop button —
`rsync.sh` runs `--inplace --partial`, so stopping costs the file in flight, not the share.
It answers to `MEDIA_SEED_ENABLED` in `master.conf` — a Tier 2 toggle beside the per-orchestrator
ones, still under Tier 1 `RSYNC_ENABLED`. Off means onboard finishes without ever dispatching it,
for a partner being filled from a moved disk or one that already holds the library. An unset
ones, still under Tier 1 `RSYNC_ENABLED`. **Off means there is no Phase 3 at all** and onboarding
is two phases: the toggle removes the phase rather than disabling a button. Use it for a partner
being filled from a moved disk or one that already holds the library. An unset
`MEDIA_SEED_ENABLED` reads as on, so a conf that predates the toggle keeps its behaviour.
Phase 3 also sets the gate posture it needs and leaves it there: Tier 1 open so `rsync.sh` will
move anything at all, every Tier 2 gate closed so the scheduled orchestrators are not competing
for the same link and the same disks for the weeks the seed takes.
---
## ━━━ HOW THE SCRIPTS RELATE ━━━