Original DR workshop: authentication, capacity and RUN handover

Use only the guarded disposable lab and synthetic observations. Never perform
these operations on banking or other production systems as part of this exercise.

1. Predict before replay
Fill backing / target / path A / path B / map capacity after each operation:
file truncate, target offline/reopen, first rescan, second rescan, explicit resize.
Identify which operation changes the layer and which command observes it.
Expected host snapshots: 64/64/64, 96/64/64, 96/96/64, 96/96/96 MiB.
The file grows before target presentation changes. No filesystem is created.

2. Negative and positive authentication
Explain why discovery succeeds but the first normal login fails. Identify the
error code, message, session absence and disk absence. Then find both successful
logins. Error 24 plus the authorization message is observed; an arbitrary nonzero
exit is not sufficient proof that CHAP rejected the wrong password.

3. Capacity proof
Calculate the byte increment: 100663296 - 67108864 = 33554432 = 32 MiB.
Locate the old marker check and new marker offset, 83886080 bytes (80 MiB).
Explain why a read at offset zero alone would not exercise newly added space.
List two things this evidence does not prove: full-filesystem integrity,
application completion, online-array continuity or crash durability are valid.

4. Fictional maintenance decision
Portal B reconnects with the new credential; A fails. Application access remains
through B. Describe a targeted check, what must remain available, a stop condition
and the evidence needed before declaring redundancy restored. Do not propose
removing CHAP or simultaneously disconnecting both portals to meet a deadline.
A target's supported rotation behavior must be validated before choosing sequence.

5. English meeting note, complete using observations
"Block growth is confirmed at [bytes] on [paths] paths and the map. We verified
[marker checks]. Authentication evidence covers [scope]. Application acceptance
is pending [criteria], owned by [role] with the next review at [time]."
This is a fictional communication exercise, not a procedure of a financial institution.

6. Peer review and closure
Ask another learner to identify an unsupported conclusion in the proposed note.
Check target/account/node/map cleanup, restored configuration and the QEMU PID
exit. Keep version and script-hash evidence. Record unanswered questions for the
storage, application and security owners. A successful lab does not replace
human review or the service's acceptance criteria.
