Provide a safe guest workflow for formatting and mounting volumes #127

New issue

Open

opened 2026-09-15 06:55:34 +00:00 by a73x · 0 comments

a73x commented

2026-09-15 06:55:34 +00:00

Owner

Volumes arrive as raw block devices starting at /dev/vdc. docs/volumes.md currently shows manual mkfs and mount commands; reusing a claim requires preserving its existing filesystem.

Outcome

Users can initialize a fresh volume and mount an existing volume across boots without accidentally formatting retained data.

Acceptance criteria

Document separate fresh-volume initialization and existing-volume reuse workflows.
Provide a supported cloud-init recipe or opt-in guest setup mechanism, with clear filesystem and image prerequisites.
Formatting requires explicit initialization intent and refuses an existing filesystem/signature.
Persist mounts using a stable filesystem identifier such as UUID, with defined behavior when a disk is absent.
Verify that a marker survives guest reboot and attachment to a replacement VM, including multiple attached volumes.

This does not require the host agent to format guest filesystems. Related: #122; docs/volumes.md; internal/smoke/volume.go.

Volumes arrive as raw block devices starting at /dev/vdc. docs/volumes.md currently shows manual mkfs and mount commands; reusing a claim requires preserving its existing filesystem. ## Outcome Users can initialize a fresh volume and mount an existing volume across boots without accidentally formatting retained data. ## Acceptance criteria - Document separate fresh-volume initialization and existing-volume reuse workflows. - Provide a supported cloud-init recipe or opt-in guest setup mechanism, with clear filesystem and image prerequisites. - Formatting requires explicit initialization intent and refuses an existing filesystem/signature. - Persist mounts using a stable filesystem identifier such as UUID, with defined behavior when a disk is absent. - Verify that a marker survives guest reboot and attachment to a replacement VM, including multiple attached volumes. This does not require the host agent to format guest filesystems. Related: #122; docs/volumes.md; internal/smoke/volume.go.