---
title: "Discussion on \"Why a Deleted Linux File Can Still Consume Disk Space\" | Hashnode"
description: "Discussion on \"Why a Deleted Linux File Can Still Consume Disk Space\". Ran rm on a 50GB file but df still shows 100% full? Discover why unlinked open file descriptors keep disk blocks allocated."
url: "https://hashnode.com/posts/why-a-deleted-linux-file-can-still-consume-disk-space/6ad24b1a042b56ac7bf5afd5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why a Deleted Linux File Can Still Consume Disk Space](https://asepsayyad007.hashnode.dev/why-a-deleted-linux-file-can-still-consume-disk-space?utm_source=hashnode&utm_medium=feed)

Ran rm on a 50GB file but df still shows 100% full? Discover why unlinked open file descriptors keep disk blocks allocated.

Oct 16 · 20 min read · asepsayyad007.hashnode.dev  
Read the article

-   [#linux](https://hashnode.com/tag/linux)
-   [#ubuntu](https://hashnode.com/tag/ubuntu)
-   [#devops](https://hashnode.com/tag/devops)
-   [#command-line](https://hashnode.com/tag/command-line)
-   [#cloud-computing](https://hashnode.com/tag/cloud-computing)
-   [#administrator](https://hashnode.com/tag/administrator)

## Written by

[Asep Sayyad](https://hashnode.com/@asepsayyad007)

@asepsayyad007 · Aurangabad

  
[View profile](https://hashnode.com/@asepsayyad007)

Linux • DevOps • Self-Hosting • Open Source

Linux • DevOps • Open Source | Building AiroDrop—an Apple-like ecosystem for iPhone users on Windows. Sharing real-world projects, automation, and engineering lessons.

## Responses 1

Markdown supported · ⌘↵ to post

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/why-a-deleted-linux-file-can-still-consume-disk-space/6ad24b1a042b56ac7bf5afd5/comment/6ad2b877a305ffe6691885c7)

The 52GB debug.log example is a very realistic way to show why rm returning instantly means nothing while a process still holds the file descriptor. The df versus du mismatch is usually the first clue, so having that next to the triage playbook is handy. The O\_APPEND caveat is a good addition too, since truncating through the open descriptor behaves differently depending on how the writer opened the file.
