[GH-ISSUE #264] rootfs space explosion #74

Closed
opened 2026-10-29 14:19:13 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @cheney-xiaobo on GitHub (Sep 8, 2026).
Original GitHub issue: https://github.com/kvcache-ai/AgentENV/issues/264

Affected component

Snapshot / template builder

Problem statement

When continuously overwriting a file inside the sandbox, the upper.data file under firecracker‑work/agentenv‑fc‑xx for overlaybd keeps growing and can reach up to 10 GB. If multiple pause/resume operations are superimposed in this scenario, the overall rootfs footprint can become extremely large, then snapshot may can not finish(because snapshot will not compact rootfs overbd.commit)

Use case

in firecracker write 1G file 10 times,then pause sandbox/resume sandbox, continue many time

Current behavior and workarounds

before compact work the rootfs overlaybd.commit may reach 10GB

Desired behavior

maybe there should be compact before snapshot or there is some other good way to solution this issue

Proposed approach

No response

Compatibility and operational impact

API/config changes:
add manual compact method or do compact before snapshot with many layer

Snapshot or storage format changes:

New host/runtime requirements:

Upgrade and rollback considerations:

Alternatives considered

or change the HybridLogStructured mode

Non-goals

No response

Contribution

I can implement it

Pre-submission checklist

  • I searched existing issues and discussions and did not find a duplicate.
  • I described a concrete problem and use case, not only a proposed technology.
  • I understand that acceptance of the problem does not imply approval of a particular implementation.
Originally created by @cheney-xiaobo on GitHub (Sep 8, 2026). Original GitHub issue: https://github.com/kvcache-ai/AgentENV/issues/264 ### Affected component Snapshot / template builder ### Problem statement When continuously overwriting a file inside the sandbox, the `upper.data` file under `firecracker‑work/agentenv‑fc‑xx` for overlaybd keeps growing and can reach up to 10 GB. If multiple pause/resume operations are superimposed in this scenario, the overall rootfs footprint can become extremely large, then snapshot may can not finish(because snapshot will not compact rootfs overbd.commit) ### Use case in firecracker write 1G file 10 times,then pause sandbox/resume sandbox, continue many time ### Current behavior and workarounds before compact work the rootfs overlaybd.commit may reach 10GB ### Desired behavior maybe there should be compact before snapshot or there is some other good way to solution this issue ### Proposed approach _No response_ ### Compatibility and operational impact API/config changes: add manual compact method or do compact before snapshot with many layer Snapshot or storage format changes: New host/runtime requirements: Upgrade and rollback considerations: ### Alternatives considered or change the HybridLogStructured mode ### Non-goals _No response_ ### Contribution I can implement it ### Pre-submission checklist - [x] I searched existing issues and discussions and did not find a duplicate. - [x] I described a concrete problem and use case, not only a proposed technology. - [x] I understand that acceptance of the problem does not imply approval of a particular implementation.
bsakaguchi 2026-10-29 14:19:13 +00:00
Author
Owner

@yingdi-shan commented on GitHub (Sep 8, 2026):

We have a built-in compaction mechanism after 32 pause/resumes. We are working on optimizing it in issue #183.

<!-- gh-comment-id:5586921565 --> @yingdi-shan commented on GitHub (Sep 8, 2026): We have a built-in compaction mechanism after 32 pause/resumes. We are working on optimizing it in issue #183.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kvcache-ai/AgentENV#74
No description provided.