<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>NTFS on KnightLi Blog</title>
        <link>https://www.knightli.com/en/tags/ntfs/</link>
        <description>Recent content in NTFS on KnightLi Blog</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en</language>
        <lastBuildDate>Sat, 02 May 2026 10:46:20 +0800</lastBuildDate><atom:link href="https://www.knightli.com/en/tags/ntfs/index.xml" rel="self" type="application/rss+xml" /><item>
        <title>Linux 7.0 and 7.1 NTFS Driver Changes Explained</title>
        <link>https://www.knightli.com/en/2026/05/02/linux-7-0-7-1-ntfs-driver/</link>
        <pubDate>Sat, 02 May 2026 10:46:20 +0800</pubDate>
        
        <guid>https://www.knightli.com/en/2026/05/02/linux-7-0-7-1-ntfs-driver/</guid>
        <description>&lt;p&gt;After Linux 7.0, Linux 7.1 entered the next feature merge window. One notable change is a new NTFS kernel driver.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;New&amp;rdquo; does not mean Linux is supporting NTFS for the first time, nor does it mean &lt;code&gt;ntfs3&lt;/code&gt; is being replaced. More precisely, Linux 7.1 adds a new optional in-kernel NTFS read-write driver. It is based on the old in-kernel &lt;code&gt;ntfs&lt;/code&gt; driver, modernized and extended with more complete write support.&lt;/p&gt;
&lt;h2 id=&#34;quick-take&#34;&gt;Quick Take
&lt;/h2&gt;&lt;p&gt;Linux now has three main NTFS paths:&lt;/p&gt;
&lt;table&gt;
  &lt;thead&gt;
      &lt;tr&gt;
          &lt;th&gt;Option&lt;/th&gt;
          &lt;th&gt;Location&lt;/th&gt;
          &lt;th&gt;Read-write support&lt;/th&gt;
          &lt;th&gt;Best fit&lt;/th&gt;
      &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
      &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;ntfs-3g&lt;/code&gt;&lt;/td&gt;
          &lt;td&gt;User-space FUSE&lt;/td&gt;
          &lt;td&gt;Read-write&lt;/td&gt;
          &lt;td&gt;Stability first; long-time distro default&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;ntfs3&lt;/code&gt;&lt;/td&gt;
          &lt;td&gt;Kernel-space&lt;/td&gt;
          &lt;td&gt;Read-write&lt;/td&gt;
          &lt;td&gt;More direct kernel integration and performance&lt;/td&gt;
      &lt;/tr&gt;
      &lt;tr&gt;
          &lt;td&gt;New &lt;code&gt;ntfs&lt;/code&gt;&lt;/td&gt;
          &lt;td&gt;Kernel-space&lt;/td&gt;
          &lt;td&gt;Read-write&lt;/td&gt;
          &lt;td&gt;Optional implementation added in Linux 7.1&lt;/td&gt;
      &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;This is not a forced migration. It simply adds another option. Most users can keep following their distribution defaults for now.&lt;/p&gt;
&lt;h2 id=&#34;how-70-and-71-relate&#34;&gt;How 7.0 and 7.1 Relate
&lt;/h2&gt;&lt;p&gt;Linux 7.0 only marks the move into the 7.x kernel series. It does not mean NTFS support was suddenly rewritten in 7.0. The NTFS-related change appears in the Linux 7.1 feature cycle.&lt;/p&gt;
&lt;p&gt;NTFS remains important for Linux desktop users because dual-boot systems, external drives, USB drives, and Windows data disks often use it. The hard part is writes: if a file-system driver has a bug, user data can be affected directly. That is why NTFS driver changes are treated carefully.&lt;/p&gt;
&lt;h2 id=&#34;ntfs-3g-ntfs3-and-the-new-ntfs&#34;&gt;&lt;code&gt;ntfs-3g&lt;/code&gt;, &lt;code&gt;ntfs3&lt;/code&gt;, and the New &lt;code&gt;ntfs&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;ntfs-3g&lt;/code&gt; is a user-space FUSE driver. It has long handled NTFS read-write support on Linux. It may not always be the fastest option, but it is mature, compatible, and well documented.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;ntfs3&lt;/code&gt; is the in-kernel NTFS driver contributed by Paragon Software and already merged into Linux. It has a shorter path, integrates more directly with VFS, and can offer better performance. But file-system drivers require strong maintenance discipline, and &lt;code&gt;ntfs3&lt;/code&gt; has seen discussion around maintenance pace and code quality after merging.&lt;/p&gt;
&lt;p&gt;The new Linux 7.1 &lt;code&gt;ntfs&lt;/code&gt; driver is maintained by Namjae Jeon. It is not written from scratch; it modernizes the old kernel &lt;code&gt;ntfs&lt;/code&gt; driver, adds write support, and coexists with &lt;code&gt;ntfs3&lt;/code&gt; as another optional implementation.&lt;/p&gt;
&lt;p&gt;In short:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code&gt;ntfs-3g&lt;/code&gt;: conservative, mature, user-space.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ntfs3&lt;/code&gt;: existing in-kernel mainline option.&lt;/li&gt;
&lt;li&gt;New &lt;code&gt;ntfs&lt;/code&gt;: new in-kernel option in 7.1, still worth watching.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;which-one-to-use&#34;&gt;Which One to Use
&lt;/h2&gt;&lt;p&gt;There is no need to switch immediately. A conservative order is:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Keep using the distribution default for important data, usually &lt;code&gt;ntfs-3g&lt;/code&gt; or a tested &lt;code&gt;ntfs3&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Try &lt;code&gt;ntfs3&lt;/code&gt; when performance matters.&lt;/li&gt;
&lt;li&gt;Test the new &lt;code&gt;ntfs&lt;/code&gt; driver on temporary, test, or recoverable data first.&lt;/li&gt;
&lt;li&gt;Back up important NTFS partitions before writing.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;To mount with &lt;code&gt;ntfs3&lt;/code&gt; manually:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo mount -t ntfs3 /dev/sdX1 /mnt/ntfs
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;For temporary read-only access:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo mount -o ro /dev/sdX1 /mnt/ntfs
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;To check which driver is being used:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;span class=&#34;lnt&#34;&gt;2
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;findmnt -T /mnt/ntfs
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;mount &lt;span class=&#34;p&#34;&gt;|&lt;/span&gt; grep ntfs
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;h2 id=&#34;dual-boot-notes&#34;&gt;Dual-Boot Notes
&lt;/h2&gt;&lt;p&gt;If an NTFS partition comes from a Windows system disk, make sure Windows is fully shut down before writing to it. Fast Startup and hibernation can leave the NTFS volume in an unfinished state, and Linux writes may then cause consistency problems.&lt;/p&gt;
&lt;p&gt;Check these first:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Disable Windows Fast Startup.&lt;/li&gt;
&lt;li&gt;Make sure the partition is not hibernated.&lt;/li&gt;
&lt;li&gt;Confirm BitLocker or other encryption is not blocking access.&lt;/li&gt;
&lt;li&gt;Safely eject external drives from Windows.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;These rules apply whether you use &lt;code&gt;ntfs-3g&lt;/code&gt;, &lt;code&gt;ntfs3&lt;/code&gt;, or the new &lt;code&gt;ntfs&lt;/code&gt; driver.&lt;/p&gt;
&lt;h2 id=&#34;why-multiple-ntfs-drivers-exist&#34;&gt;Why Multiple NTFS Drivers Exist
&lt;/h2&gt;&lt;p&gt;Multiple implementations for the same file system are not unusual in Linux. Old, new, vendor, and community implementations can coexist until maintenance status and real-world feedback make the preferred path clear.&lt;/p&gt;
&lt;p&gt;NTFS is especially suited to a conservative approach:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;User data risk is high.&lt;/li&gt;
&lt;li&gt;Compatibility cases are complex.&lt;/li&gt;
&lt;li&gt;Implementations differ in performance and stability tradeoffs.&lt;/li&gt;
&lt;li&gt;Distributions need time to validate defaults.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;So the new Linux 7.1 &lt;code&gt;ntfs&lt;/code&gt; driver does not immediately obsolete &lt;code&gt;ntfs-3g&lt;/code&gt; or &lt;code&gt;ntfs3&lt;/code&gt;. It gives the kernel community another maintainable option.&lt;/p&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;The new Linux 7.1 &lt;code&gt;ntfs&lt;/code&gt; driver is an optional in-kernel NTFS read-write implementation. It coexists with &lt;code&gt;ntfs-3g&lt;/code&gt; and &lt;code&gt;ntfs3&lt;/code&gt;; it does not directly replace either.&lt;/p&gt;
&lt;p&gt;Regular users can keep using distribution defaults. Users who want to test performance or kernel file-system changes can watch &lt;code&gt;ntfs3&lt;/code&gt; and the new &lt;code&gt;ntfs&lt;/code&gt;, but important data should be backed up before switching drivers.&lt;/p&gt;
</description>
        </item>
        
    </channel>
</rss>
