[PR #434] [CLOSED] fix(snapshot): rebase live disks after compaction #435

New issue

Closed

opened 2026-10-29 14:23:23 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-29 14:23:23 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/AgentENV/pull/434
Author: @Park-Jiyeonn
Created: 10/24/2026
Status: ❌ Closed

Base: main ← Head: fix/live-snapshot-layer-rebase

📝 Commits (1)

592fcf3 fix(snapshot): rebase live disks after compaction

📊 Changes

11 files changed (+618 additions, -22 deletions)

View changed files

📝 docs/src/concepts/snapshots/create.md (+5 -0)
📝 src/sandbox/firecracker/overlaybd_snapshot.rs (+89 -6)
📝 src/sandbox/firecracker/sandbox.rs (+9 -0)
📝 src/sandbox/ublk/device.rs (+12 -1)
📝 storage/overlaybd/src/image/image_file.rs (+254 -4)
📝 storage/overlaybd/src/lsmt/file/stack.rs (+1 -1)
📝 storage/ublk-daemon/src/client.rs (+33 -1)
📝 storage/ublk-daemon/src/protocol.rs (+6 -1)
📝 storage/ublk-daemon/src/server.rs (+50 -4)
📝 storage/ublk-daemon/tests/ublk_daemon_test.rs (+59 -1)
📝 tests/integration/snapshot.rs (+100 -3)

📄 Description

Why

Snapshots were compacted, but the running disk kept adding layers and could still hit the limit.

Design and behavior changes

Switch the live disk to the compacted layers while keeping its writable upper. Check the layer limit before sealing. Older snapshots stay unchanged.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/kvcache-ai/AgentENV/pull/434 **Author:** [@Park-Jiyeonn](https://github.com/Park-Jiyeonn) **Created:** 10/24/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/live-snapshot-layer-rebase` --- ### 📝 Commits (1) - [`592fcf3`](https://github.com/kvcache-ai/AgentENV/commit/592fcf3c5fcecdddc6b8d09dd13db59c1b7aa0b3) fix(snapshot): rebase live disks after compaction ### 📊 Changes **11 files changed** (+618 additions, -22 deletions) <details> <summary>View changed files</summary> 📝 `docs/src/concepts/snapshots/create.md` (+5 -0) 📝 `src/sandbox/firecracker/overlaybd_snapshot.rs` (+89 -6) 📝 `src/sandbox/firecracker/sandbox.rs` (+9 -0) 📝 `src/sandbox/ublk/device.rs` (+12 -1) 📝 `storage/overlaybd/src/image/image_file.rs` (+254 -4) 📝 `storage/overlaybd/src/lsmt/file/stack.rs` (+1 -1) 📝 `storage/ublk-daemon/src/client.rs` (+33 -1) 📝 `storage/ublk-daemon/src/protocol.rs` (+6 -1) 📝 `storage/ublk-daemon/src/server.rs` (+50 -4) 📝 `storage/ublk-daemon/tests/ublk_daemon_test.rs` (+59 -1) 📝 `tests/integration/snapshot.rs` (+100 -3) </details> ### 📄 Description ## Why Snapshots were compacted, but the running disk kept adding layers and could still hit the limit. ## Design and behavior changes Switch the live disk to the compacted layers while keeping its writable upper. Check the layer limit before sealing. Older snapshots stay unchanged. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-29 14:23:23 +00:00