Since 2026-11-22 the pod's root filesystem persists and /tmp is on
overlayfs. There stat reports the overlay device (st_dev 0xb3) while
/proc/locks prints the device of the upper filesystem (00:84), so lock_id
never matched the scratch token.lock and arbiter/start failed with "A
serves but does not hold token.lock" although A held the lock. Production's
arena is on tmpfs (/dev/shm/llama-vram), where both agree. Put the scratch
arenas there too (/dev/shm/fork-validate.<suffix of the scratch dir>,
removed by finish()); logs and the rest of the scratch stay in /tmp.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PZz44SLQvTXMyWGio6t9DZ