Skip to content

Feat/clone from snapshot #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xujihui1985 merged 2 commits into from
Mar 14, 2026
Merged

Feat/clone from snapshot #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eccd76a
feat: add design doc
xujihui1985 Mar 8, 2026
f008191
feat: implement clone from snapshot
xujihui1985 Mar 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,24 @@ For R2, add:
--r2-account-id <account-id>
```

## Clone From Snapshot

Create a new export lineage from a published remote snapshot. Before the first snapshot, reads are seeded from the source snapshot lazily. The first snapshot of the cloned export uploads a full base blob for the target export and becomes generation `1`.

```bash
cargo run -- clone \
--export-id vm02 \
--cache-dir /var/lib/nbd-server/vm02 \
--bucket my-bucket \
--prefix exports/vm02 \
--source-prefix exports/vm01 \
--source-snapshot-id 2 \
--listen 127.0.0.1:10810 \
--admin-sock /tmp/nbd-server-vm02.sock
```

Clone always resolves against a published remote snapshot. If a running `vm01` process has local dirty writes, those writes are ignored by clone.

## Attach With `nbd-client`

The server speaks fixed-newstyle NBD and supports `OPT_GO` for a single export named exactly like `--export-id`.
Expand Down
Loading
Loading