feat(alertd): inode exhaustion check#496
Open
passcod wants to merge 1 commit into
Open
Conversation
Fixed-inode filesystems (ext4, xfs, vfat, tmpfs, …) can run out of inodes while df still shows free bytes, after which writes fail with ENOSPC. Reads df -P -i -T and warns at 85% / fails at 95% inodes used on the worst mount. btrfs (dynamic inodes, no meaningful count) and any filesystem reporting a zero inode total are excluded — btrfs space pressure is covered by the btrfs check. Linux-only. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
🤖 New host-level alertd healthcheck
inodes.Fixed-inode filesystems (ext4, xfs, vfat, tmpfs, …) carve a set number of inodes at mkfs time. A workload that creates lots of small files can exhaust them while
dfstill shows free bytes — then writes fail with ENOSPC, invisible to the existingdisk_free(bytes) check.Reads
df -P -i -Tand warns at 85% / fails at 95% inodes used on the worst mount. btrfs allocates inodes dynamically and reports no meaningful count, so it's excluded (its space pressure is thebtrfscheck's job); any filesystem reporting a zero inode total is skipped for the same reason. Linux-only.The df parser (column split, space-containing mountpoints rejoined, btrfs/zero-total filtered) is a pure function with tests.