This repository has been archived by the owner on Jan 4, 2022. It is now read-only.
kube-spawn: enlarge storage pool for each cloned image #70
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dongsupark
force-pushed
the
dongsu/enlarge-storage-pool
branch
2 times, most recently
from
efcb953
to
d84dcb2
Compare
Enlarge the storage pool that is actually a btrfs volume backed by /var/lib/machines.raw. Every btrfs volume would need more space for its metadata as much as the volume grows through CoW operations. /var/lib/machines should have more space than its original image size. Otherwise /var/lib/machines could become full when files start to be written to nspawn containers. Unfortunately it's a temporary workaround. How much space we should add more to the image might depend on estimation during run-time operations. In the long run, systemd itself should be able to reserve more space for the storage pool, every time when it pulls an image to store in the pool. Fixes #66
|
I'm going to merge it, as this fix is necessary for testing other parts. If any problem happens regarding storage pools, feel free to file issues. |
2 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enlarge the storage pool that is actually a btrfs volume backed by
/var/lib/machines.raw. Every btrfs volume would need more space for its metadata as much as the volume grows through CoW operations./var/lib/machinesshould have more space than its original image size. Otherwise/var/lib/machinescould become full when files start to be written to nspawn containers.In short, it's equivalent to the following command sequence:
Unfortunately it's a temporary workaround. How much space we should add more to the image might depend on estimation during run-time operations. In the long run, systemd itself should be able to reserve more space for the storage pool, every time when it pulls an image to store in the pool.
Fixes #66