{"version":"2.1.319","anchor":"disk-check-reports-few-inodes-while-running","canonical_anchor":"disk-check-reports-few-inodes-while-running","heading":"Disk checks now report running out of inodes separately from low disk space","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/disk-check-reports-few-inodes-while-running","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Disk checks now report running out of inodes separately from low disk space\n\nDisk checks now tell low inodes apart from low disk space, while a command runs and when its large output is saved\n\n**What**\n\nAn inode is a slot the file system needs for every file. A disk can run out of inodes even when it still has free space. Claude Code's disk checks now report this case on its own:\n\n- While running: the disk check reports `few_inodes_while_running` when the result is `few_inodes`. Before, any such result was reported as `low_disk_while_running`.\n\n- Saving large output: when Bash command output piped into `tail` is saved, Claude Code now checks that a tool-results folder exists. It can give up with `few_inodes_at_end` and cleans up when saving fails. Before, there was only a disk-space check (`low_disk_at_end`). It also treats `tail` as getting all the output only when `allGoesIntoTail` is true.\n\n**Why**\n\nRunning out of inodes is no longer mixed up with running out of space. The note about saved output is also less likely to point at a file that does not exist.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}