---
title: "Comment by Mateo Ruiz on \"Why rm Doesn't Free Disk Space in Linux (and How to Fix)\" | Hashnode"
description: "The useful production lesson here is that rm changes namespace state, not necessarily storage state. That also explains why df vs du is such a valuable diagnost"
url: "https://hashnode.com/posts/linux-rm-not-freeing-disk-space/6abb688a8b1942efb7c8c8f1/comment/6abf789a7d2d1b1222b37d3b"
---

[Discussion](https://hashnode.com/posts/linux-rm-not-freeing-disk-space/6abb688a8b1942efb7c8c8f1)

Comment [Why rm Doesn't Free Disk Space in Linux (and How to Fix)](https://hashnode.com/posts/linux-rm-not-freeing-disk-space/6abb688a8b1942efb7c8c8f1)

[Mateo Ruiz](https://hashnode.com/@mateoruiz)

[Oct 2](https://hashnode.com/posts/linux-rm-not-freeing-disk-space/6abb688a8b1942efb7c8c8f1/comment/6abf789a7d2d1b1222b37d3b)

The useful production lesson here is that `rm` changes namespace state, not necessarily storage state. That also explains why `df` vs `du` is such a valuable diagnostic combination: when they disagree significantly, deleted-but-open files are one of the first things worth checking.

I’d also treat truncating `/proc/<pid>/fd/<fd>` as an emergency recovery technique rather than the normal fix. The safer long-term solution is getting the application’s log lifecycle right log rotation, reopening descriptors, and monitoring filesystem headroom so a runaway log doesn’t turn into a 2 AM storage incident in the first place.
