From: Mark Harmstone <mark@harmstone.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: WinBtrfs v1.10
Date: Tue, 1 Sep 2026 22:24:59 +0100 [thread overview]
Message-ID: <4cdce5a0-e717-41d6-ab68-ab6a85646028@harmstone.com> (raw)
Hello everybody,
I've released version 1.10 of WinBtrfs, the btrfs kernel driver for
Windows - this is the first release in more than two years.
https://github.com/maharmstone/btrfs
In this version:
* Added support for writing free-space bitmaps (reading was already
supported)
* Added support for writing compressed inline files (reading was already
supported)
* Improved handling of removable devices
* Tightened up error recovery on OOMs and ENOSPCs
* Fixed crash when moving files across subvolumes, such as to the
Recycle Bin
* Fixed crash when many files created simultaneously, e.g. by Steam
* Fixed extent tree corruption when writing to snapshots
* Fixed preallocation issues (fixes rclone)
* Fixed deadlock when querying hard links
* Fixed memory corruption relating to watching the Registry
* Fixed disk usage statistics for multi-device volumes
* Fixed FSCTL_DUPLICATE_EXTENTS_TO_FILE sent from 32-bit userspace
* Refactored to use same struct and constant definitions as on Linux
Thanks
Mark
reply other threads:[~2026-09-01 21:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4cdce5a0-e717-41d6-ab68-ab6a85646028@harmstone.com \
--to=mark@harmstone.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).