<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Filesystems on Shubham Singh</title>
    <link>https://1shubham7.blog/tags/filesystems/</link>
    <description>Recent content in Filesystems on Shubham Singh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://1shubham7.blog/tags/filesystems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I deleted a huge file but the disk usage didn&#39;t go down.</title>
      <link>https://1shubham7.blog/deleted-file-disk/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/deleted-file-disk/</guid>
      <description>Why rm on an open file frees nothing: a file is an inode, a name is only a link to it, and the blocks stay allocated until the link count is zero and every file descriptor is closed. Where df and du part ways, how to find the process holding the file, how to make it let go, and what the same problem looks like on a Kubernetes node.</description>
    </item>
    
  </channel>
</rss>
