WinBtrfs 1.10: Novinky v kontroleři pro práci s Btrfs v Windows

Systémy Windows a Linux používají odlišné systémy souborů, což představuje problém, když potřebujete přistupovat k disku vytvořenému pro druhý systém z prvního. precisely to solve part of this, there is WinBtrfs, a driver that allows Windows to work with the Btrfs file system used in Linux. The project has just been updated. WinBtrfs 1.10 is now available, more than two years after the previous version. Although it does not change what the driver does completely, it does come with several new features. For example, you can write free space maps and compressed files stored directly in the file system's metadata. There are also improvements for removable devices and for recovering from moments when the machine runs out of memory or disk space. Additionally, this version also fixes many accumulated bugs over the years. And, given that we are in 2026, Claude, the AI from Anthropic, was used during the search for bugs and code review. However, the developers clarify that the WinBtrfs 1.10 code was written without using AI.

WinBtrfs 1.10: Novinky v kontroleři pro práci s Btrfs v Windows

Co je WinBtrfs a pro čemu slouží?

Btrfs is a file system created primarily for the Linux ecosystem. The problem is that Windows does not offer native full support for Btrfs. That's where WinBtrfs comes in. This project works as a driver for Microsoft Windows that allows reading and writing to Btrfs file systems from within the operating system. It is compatible with Windows XP and later versions, so it has been acting as an intermediary between the two worlds for quite some time. To give you an idea, if you have a disk formatted in Btrfs and need to use it from Windows, WinBtrfs allows the system to understand what's inside and work with those files. The dream of being able to run Linux on Apple's Mac much closer: a new kernel patch adds support for USB4/Thunderbolt on M1, M2, and M3

Zpět k původnímu kódu Btrfs

The Btrfs team recently recovered over 600 lines of code that had been deleted. Without them, some data could potentially be lost without the user even realizing it. To give you an idea, the problem was related to a Btrfs function responsible for detecting changes made to memory before the file system can control them correctly. During the development of Linux 7.2, it was thought that this protection was no longer needed because the changes made to the kernel's memory management had already solved the situations that made it necessary. However, the tests conducted have shown that this was not the case. And here's the problem that has forced a step back: all this can lead to data loss without the user even knowing it. The danger here is that the user could continue working with the system, unaware that data is being lost.