-
Notifications
You must be signed in to change notification settings - Fork 52
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.
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
btrfs hack: shrink the allocated size #2076
Open
ader1990
wants to merge
1
commit into
main
Choose a base branch
from
ader1990/btrfs-free-size-approximation-fix
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
ader1990
force-pushed
the
ader1990/btrfs-free-size-approximation-fix
branch
from
July 5, 2024 08:22
48fb339
to
737e771
Compare
ader1990
force-pushed
the
ader1990/btrfs-free-size-approximation-fix
branch
from
August 14, 2024 15:00
737e771
to
26e50d0
Compare
ader1990
force-pushed
the
ader1990/btrfs-free-size-approximation-fix
branch
from
August 14, 2024 15:03
26e50d0
to
bcea0e8
Compare
ader1990
force-pushed
the
ader1990/btrfs-free-size-approximation-fix
branch
from
August 14, 2024 21:09
bcea0e8
to
ffeedd9
Compare
ader1990
force-pushed
the
ader1990/btrfs-free-size-approximation-fix
branch
from
August 20, 2024 09:39
551858a
to
af97417
Compare
Note here for the actual OS/Linux kernel being used by the github actions:
|
ader1990
force-pushed
the
ader1990/btrfs-free-size-approximation-fix
branch
from
September 5, 2024 12:55
af97417
to
6600f9a
Compare
We are using read-only btrfs compressed for the /usr partition, and sometimes the free space shown by `btrfs fi usage` and the `df` IS diverging, with `df` showing the free space from the `btrfs fi usage`'s `Device unallocated. I have found a way to fix the allocation, by decreasing the size to more than the btrfs filesystem allows, but curiosly the allocation is getting reset during the failed attempt and the issue is fixed. This is of course, a _HACK_, and can at any time produce unwanted behaviours. Note that the issue cannot be reliably reproduced. See Flatcar issue: flatcar/Flatcar#1473 See issue upstream: https://bugzilla.kernel.org/show_bug.cgi?id=219167 Signed-off-by: Adrian Vladu <[email protected]>
ader1990
force-pushed
the
ader1990/btrfs-free-size-approximation-fix
branch
from
September 5, 2024 12:56
6600f9a
to
51d5509
Compare
ader1990
changed the title
build_image: btrfs: minimize allocation
btrfs hack: shrink the allocated size
Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
btrfs hack: shrink the allocated size
We are using read-only btrfs compressed for the /usr partition,
and sometimes the free space shown by
btrfs fi usage
and thedf
IS diverging,with
df
showing the free space from thebtrfs fi usage
's `Device unallocated.I have found a way to fix the allocation, by decreasing the size to more than the btrfs
filesystem allows, but curiosly the allocation is getting reset during the failed
attempt and the issue is fixed.
This is of course, a HACK, and can at any time produce unwanted behaviours.
Note that the issue cannot be reliably reproduced.
See Flatcar issue: flatcar/Flatcar#1473
See issue upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=219167