<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Block Devices on Nalar</title>
    <link>https://nalar.dev/tags/block-devices/</link>
    <description>Recent content in Block Devices on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/block-devices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Linux Filesystem Tools Report Different Types</title>
      <link>https://nalar.dev/why-linux-filesystem-tools-report-different-types/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/why-linux-filesystem-tools-report-different-types/</guid>
      <description>&lt;p&gt;A disk partition can contain an ext4 filesystem while a process sees an &lt;code&gt;overlay&lt;/code&gt; filesystem at &lt;code&gt;/&lt;/code&gt;. Meanwhile, &lt;code&gt;/proc/filesystems&lt;/code&gt; may list &lt;code&gt;tmpfs&lt;/code&gt; and &lt;code&gt;nfs&lt;/code&gt;, neither of which needs a local partition. These are not conflicting answers. They describe different parts of the Linux storage stack.&lt;/p&gt;&#xA;&lt;p&gt;The distinction matters when identifying a volume, investigating an unexpected mount, or checking which filesystem handles an application&amp;rsquo;s path. A filesystem signature on a device is not the same thing as a mounted filesystem in a process&amp;rsquo;s namespace.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
