The Linux kernel 7.1-rc2 introduces a revamped NTFS driver that marks a significant leap forward for users needing native Windows filesystem support. This new driver, built upon the foundations of the original read-only NTFS driver, offers substantially more features and higher performance than the Paragon NTFS3 driver, which had been the standard for the past few years. It also vastly outperforms the older NTFS-3G FUSE-based solution. Below, we answer common questions about this update, its fixes, and what it means for Linux users.
What makes the new NTFS driver in Linux 7.1-rc2 different from the Paragon NTFS3 driver?
The new NTFS driver is a complete rewrite based on the original read-only kernel driver, but now fully read-write. Compared to the Paragon NTFS3 driver, it offers better performance and a more extensive set of features. The Paragon driver, while functional, had limitations in speed and compatibility with newer NTFS structures. The new driver leverages upstream kernel improvements and includes more robust handling of advanced NTFS features such as compression, sparse files, and extended attributes. Early benchmarks show noticeable gains in read and write throughput, particularly on large files and fragmented volumes. Additionally, the new driver integrates more seamlessly with the rest of the kernel’s filesystem layer, reducing maintenance overhead and improving long-term reliability.
How does the new driver compare to the original read-only NTFS driver in the kernel?
The original NTFS driver was purely read-only, meaning users could access files but not create, modify, or delete them. The new driver in Linux 7.1-rc2 provides full read-write support, eliminating the need for third-party tools for basic write operations. Performance has also been dramatically improved—the old driver was slow and lacked support for many modern NTFS features. The new driver is not just a read-write upgrade; it’s a ground-up reimplementation that uses modern kernel APIs, resulting in faster metadata operations and better handling of write caching. For users who previously had to rely on NTFS-3G or Paragon for writing, this single driver now covers all use cases with minimal overhead.
What specific fixes were included in Linux 7.1-rc2 for the NTFS driver?
The -rc2 release brought several important fixes to the new NTFS driver. These include corrections for memory leaks under heavy write loads, improved handling of corrupted NTFS journal files, and a fix for a race condition that could cause data corruption during concurrent write operations. Additionally, the driver now properly enforces file size limits on volumes with large cluster sizes and resolves an issue where the driver would sometimes fail to mount drives that had unclean dismounts (i.e., without the $LogFile being zeroed). The developers also patched a bug related to the creation of sparse files on volumes with specific allocation policies. These fixes collectively enhance stability and data integrity, making the driver suitable for production environments.
Is the new NTFS driver better than the NTFS-3G FUSE driver?
Yes, the new kernel driver is a significant improvement over the NTFS-3G FUSE (Filesystem in Userspace) driver. NTFS-3G operated in user space, which introduced context-switching overhead and limited cache efficiency. The new driver runs directly in kernel space, enabling much faster I/O operations—especially for small random reads and writes. While NTFS-3G was widely used due to its broad feature support, the new driver now matches or exceeds that feature set while offering lower latency and better CPU utilization. Additionally, because it’s built into the kernel, there’s no need to install and manage a separate FUSE package. The only minor trade‑off is that NTFS-3G may still support some rare or experimental NTFS extensions, but for the vast majority of users, the new driver is the superior choice.
What are the key performance improvements expected from the new NTFS driver?
Performance gains stem from the driver being fully integrated into the VFS (Virtual File System) layer and using modern kernel memory management. Users can expect up to 20–30% better sequential read speeds compared to the Paragon NTFS3 driver, and as much as 50% improvement over NTFS-3G for write workloads. The driver also handles concurrent access more efficiently, with reduced lock contention. For large file operations (e.g., copying multi‑gigabyte ISO files), the throughput is nearly on par with native ext4 performance. Moreover, the new driver includes smarter caching that reduces disk I/O for repeated reads. These improvements are especially valuable for desktop users who frequently exchange files with Windows systems, as well as for dual‑boot setups where the same NTFS partition is accessed by both operating systems.
Will the new NTFS driver become the default in stable kernel releases?
Given the positive reception and the fixes applied in 7.1-rc2, it is highly likely that the new NTFS driver will become the default in the stable Linux kernel 7.1 release. The Linux kernel maintainers have expressed confidence in its stability, and it already offers better performance and feature coverage than the Paragon NTFS3 driver. However, users who prefer the Paragon driver will likely still be able to enable it as a kernel configuration option. The new driver is being actively developed, and its inclusion as default would mark the end of reliance on external FUSE or out‑of‑tree drivers for NTFS access. The upcoming release is expected to solidify this driver as the go‑to solution for NTFS on Linux.