diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/protocols.org | 25 | ||||
| -rw-r--r-- | docs/session-context.org | 70 |
2 files changed, 95 insertions, 0 deletions
diff --git a/docs/protocols.org b/docs/protocols.org index c17987e..1dee40f 100644 --- a/docs/protocols.org +++ b/docs/protocols.org @@ -221,6 +221,31 @@ When Craig says this phrase: - Say: "I don't see '[workflow-name]' yet. Create it using create-workflow process?" - If yes: Run create-workflow to define it, then use immediately (validates new workflow) +** Long-Running Process Status Updates + +When monitoring a long-running process (rsync, large downloads, builds, etc.), provide status updates every 5 minutes. + +***Format:*** +#+begin_example +**14:32** - Rsync in progress: 312GB of 640GB transferred (~49%), ETA ~25 min +**14:37** - Rsync continuing: 389GB of 640GB (~61%), ETA ~18 min +#+end_example + +***Guidelines:*** +- Check in approximately every 5 minutes +- Include current time (run =date= to get accurate time) +- Brief description of what's happening +- Progress indication (percentage, files transferred, etc.) +- ETA when possible (even a ballpark estimate is helpful) +- Format doesn't need to be strict - just be descriptive +- If ETA cannot be determined, omit it rather than guessing wildly + +***Why This Matters:*** +- Craig may be working on other things while waiting +- Status updates provide confidence the process is still running +- ETAs help with planning (e.g., "I have time for coffee" vs "stay close") +- If something stalls, the updates make it obvious + ** "Wrap it up" / "That's a wrap" / "Let's call it a wrap" When Craig says any of these phrases (or variations), execute wrap-up workflow: diff --git a/docs/session-context.org b/docs/session-context.org new file mode 100644 index 0000000..ce60fd3 --- /dev/null +++ b/docs/session-context.org @@ -0,0 +1,70 @@ +#+TITLE: Session Context +#+DATE: 2026-01-19 + +* Current Session: Monday 2026-01-19 13:12 CST + +** Summary + +Diagnosed journald issue on ratio (slow shutdown), fixed for future installs, rebuilt ISO. + +** What We Completed + +*** Committed Previous Session Changes +- scripts/full-test.sh (new) - comprehensive install tests +- scripts/build-release - added --full-test option +- custom/install-archzfs - deploys zfssnapshot/zfsrollback to target +- assets/cogito-hardware-specs.txt +- Commit: c57f1a1 + +*** Added wget to Target System +- Added wget to pacstrap package list in install-archzfs +- Commit: a6fa09b + +*** Diagnosed Slow Shutdown on ratio +- SSHed into ratio (root / cmjdase1n) +- Found journald wasn't creating journal files +- Root cause: journald starts ~650ms BEFORE ZFS mounts /var/log +- Journal files created in tmpfs, then hidden when ZFS mounts over it +- No logs from problematic shutdown (lost due to this issue) + +*** Fixed journald for ZFS (on ratio) +Applied two drop-in configs: +- /etc/systemd/journald.conf.d/persistent.conf - enables persistent storage +- /etc/systemd/system/systemd-journal-flush.service.d/zfs.conf - waits for zfs-mount.service + +*** Added journald Fix to install-archzfs +- Added same drop-in configs to configure_system() function +- Future installs will have proper journal persistence +- Commit: 24ede61 + +*** Built and Distributed New ISO +- ISO: archzfs-vmlinuz-6.12.66-lts-2026-01-19-x86_64.iso (5.2GB) +- Sanity test: 13/13 passed +- Distributed to all targets: + - ~/Downloads/isos/ + - truenas.local:/mnt/vault/isos/ + - /dev/sda (ARCHZFS USB) + - /dev/sdb1 (Ventoy) + +** Commits This Session +- c57f1a1 Add comprehensive installation tests and ZFS script deployment +- a6fa09b Add wget to target system packages +- 24ede61 Fix journald on ZFS: wait for mounts, enable persistent storage + +** Technical Notes + +*** journald + ZFS Race Condition +- journald.socket starts at ~309ms +- zfs-mount.service completes at ~978ms +- Fix: Make systemd-journal-flush.service wait for zfs-mount.service +- This ensures logs flush to persistent storage after ZFS is mounted + +*** ratio Machine +- Host: ratio (192.168.86.48) +- Login: root / cmjdase1n +- journald fix applied manually +- Next reboot should capture proper shutdown logs + +** Next Steps +- Test ratio shutdown to see if issue is resolved (now have proper logs) +- If slow shutdown recurs, check journalctl -b -1 for details |