Announcing macFUSE 4.10.1 Posted on 27 Mar 2025
Release Notes
-
Update
libfuse3to version 3.17.1Some macOS specific features require FUSE API extensions that break compatibility with the vanilla FUSE API. Setting the compile-time flag
FUSE_DARWIN_ENABLE_EXTENSIONSto 0, when building a file system, disables those API extensions. By default, the macOS specific API extensions are enabled.Please note:
- The macOS specific
libfuse3API extensions might not be stable, yet. This means thatlibfuse3file systems that are built for macFUSE 4.10.1 might need to be updated to work with future macFUSE releases.
- The macOS specific
-
Add support for arbitrary file system block sizes
The macOS kernel imposes no restrictions on the block size of a file system, neither should we. macFUSE supports file system block sizes between 128 B and 1 MB. The specified I/O size (
-oiosize=...) is rounded down to the next multiple of the file system block size, if necessary.The device block size (
-oblocksize=...) needs to be a power of two and may not exceed 4 KB on Intel Macs and 16 KB Apple Silicon Macs. -
Address code signing issue. The bundled download helper
ksurlneeds to be code signed individually to make its origin transparent. In previous releases,ksurlwas only code signed indirectly as component of the update tool. For details, see macfuse/macfuse#1062. -
Declare the maximum size of extended attributes.
pathconf(..., _PC_XATTR_SIZE_BITS)returns the number of bits that are required to store the maximum extended attribute size in bytes, in our case 25, which equals a maximum extended attribute size of 33,554,431 bytes (~ 32 MB).
