Skip to content

Fix: Prevent disk space exhaustion when /mnt is not a separate mount point#57

Open
smallprogram wants to merge 1 commit intoeasimon:masterfrom
smallprogram:master
Open

Fix: Prevent disk space exhaustion when /mnt is not a separate mount point#57
smallprogram wants to merge 1 commit intoeasimon:masterfrom
smallprogram:master

Conversation

@smallprogram
Copy link
Copy Markdown

This PR fixes a critical issue where the action causes root filesystem exhaustion on GitHub runners that don't have /mnt as a separate mount point.

On some GitHub runners, /mnt is not a separate filesystem but just a directory on the root partition. The current implementation blindly creates two large LVM physical volumes:

  1. /pv.img on the root filesystem
  2. /mnt/tmp-pv.img which also ends up on the root filesystem

…point


This PR fixes a critical issue where the action causes root filesystem exhaustion on GitHub runners that don't have `/mnt` as a separate mount point.

On some GitHub runners, `/mnt` is not a separate filesystem but just a directory on the root partition. The current implementation blindly creates two large LVM physical volumes:
1. `/pv.img` on the root filesystem
2. `/mnt/tmp-pv.img` which also ends up on the root filesystem
fawazahmed0 added a commit to fawazahmed0/maximize-build-space that referenced this pull request Jan 30, 2026
@andrey-khropov
Copy link
Copy Markdown

Related: actions/runner-images#13587

@smallprogram
Copy link
Copy Markdown
Author

request review @easimon

@James-Mart
Copy link
Copy Markdown

This is also affecting my team as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants