S3: Zoned storage
Question: What changes when the host owns zone reuse?
Time: 30 minutes. Prerequisites: completed setup. See qualification and limitations before running.
Mechanism
- Writes must respect zone boundaries and the current write pointer.
- Append returns the location chosen within a zone.
- Reset makes a zone reusable; finish only closes its writable space.
Predict
After one append, predict the state and write pointer. Does finish erase data?
Write down a predicted state or counter change before executing the commands.
Run
Host terminal, unless a command is explicitly labelled Guest. Source and
export the identity fields from connection.env. These labs overwrite the
explicit disposable namespace. Use a fresh VM for each independent arm.
bash labs/bin/preflight.sh labs/guest/lab-s3-zns.sh /dev/nvme0n1
Check your evidence
- Readback matches the bytes appended before reset.
- State and write pointer follow the specified sequence.
- The invalid write fails with the expected status; reset restores empty.
The host runner retrieves raw receipts and preserves the guest exit status. Keep unsuccessful attempts; do not replace them with a later successful log.
Interpret
Which responsibilities move into a filesystem that writes zones?
Explain the mechanism and the measurement boundary. A throughput number by itself is not evidence that the intended feature was exercised.
Recover
- No namespace: verify CONFIG_BLK_DEV_ZONED and controller identity.
- Unexpected state: preserve the receipt, then reset only the test zone.
- A generic I/O error alone does not identify a write-pointer violation.
Save the receipt before resetting the VM.
Materials and source
Slides, scripts and worksheet.
Videos are not yet recorded. The frozen public source is
1918eb9795ba.
The FEMU Manual explains the implementation and supported properties.