e2fsck: preen inline data no attr#268
Open
danielzgtg wants to merge 1 commit into
Open
Conversation
I don't like being forcibly dropped into an emergency shell to truncate pidfiles and other temporary files every time my tablet uncleanly shuts down. This seems safe. The only thing that should be erased is the size. The removed inline data flag is remembered by the extent flag being absent. There is no data to lose because there are no extents/blocks, and the system.data attribute is already diagnosed missing. Signed-off-by: Daniel Tang <danielzgtg.opensource@gmail.com>
danielzgtg
force-pushed
the
feat/e2fsckPreenInlineTruncate
branch
from
February 1, 2026 22:49
2294493 to
9bfec06
Compare
This file contains hidden or 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
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.
I don't like being forcibly dropped into an emergency shell to truncate pidfiles and other temporary files every time my tablet uncleanly shuts down.
This seems safe. The only thing that should be erased is the size. The removed inline data flag is remembered by the extent flag being absent. There is no data to lose because there are no extents/blocks, and the system.data attribute is already diagnosed missing.