fix(mft): demote IOCP-fallback chain messages from WARN to INFO#579
Merged
Conversation
The two intermediate messages of the read fallback cascade ('IOCP
inline read failed — trying fallback strategies' and 'Fallback 1
($MFT file) failed — trying unbuffered volume I/O') fired at WARN,
piercing quiet (WARN-default) subscribers on every run that walked the
chain — flagged by the content-service team as upstream mis-leveling.
The cascade is designed, automatically-handled resilience: a normal
run should stay silent, and -v/verbose reveals the chain when
debugging. Both messages are now INFO with byte-identical text (log
greps keep working). A chain that exhausts every fallback still
propagates a real error to the caller.
githubrobbi
enabled auto-merge
July 23, 2026 14:27
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
1 participant
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.
Flagged by the content-service team: the two intermediate messages of the MFT read fallback cascade (
IOCP inline read failed — trying fallback strategiesandFallback 1 ($MFT file) failed — trying unbuffered volume I/O) fired at WARN, piercing quiet WARN-default subscribers on every run that walked the chain.The cascade is designed, automatically-handled resilience — a normal run should stay silent, and
-v/verbose reveals the chain when debugging. Both messages are now INFO with byte-identical text so existing log greps keep matching. A chain that exhausts every fallback still propagates a realErrto the caller — that remains the operator-actionable signal.Failed to get MFT extents, using fallbackstays WARN deliberately: an extent-query failure on an open volume is genuinely unusual, unlike the (pre-#578) every-run snapshot chain.Cherry-picked from the tail of #578's branch — the original commit missed that PR's merge window.