<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>File Systems on Nalar</title>
    <link>https://nalar.dev/tags/file-systems/</link>
    <description>Recent content in File Systems on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/file-systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why a File Can Be Too Large for an Empty USB Drive</title>
      <link>https://nalar.dev/tech/why-a-file-can-be-too-large-for-an-empty-usb-drive/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/tech/why-a-file-can-be-too-large-for-an-empty-usb-drive/</guid>
      <description>&lt;p&gt;A USB drive can show tens or hundreds of gigabytes of free space and still refuse to accept a single large video, archive, or backup file. The error may say that the file is too large for the destination even though the drive clearly has enough room.&lt;/p&gt;&#xA;&lt;p&gt;The apparent contradiction comes from confusing two different limits: &lt;strong&gt;how much data the drive can hold in total&lt;/strong&gt; and &lt;strong&gt;how large one individual file is allowed to be&lt;/strong&gt;. The second limit is controlled largely by the drive&amp;rsquo;s file system, not by its remaining capacity.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
