Releases: linux-apfs/linux-apfs-rw
v0.3.10
Transactions are now committed regularly, so it should no longer be
strictly necessary to unmount the filesystem cleanly for writes to take
effect. It's still recommended, of course.
The release also fixes two bugs. One was a big performance regression
from 0.3.9, seen when deleting large numbers of files. The other was
that mounts would go read-only if two snapshots were attempted with the
same name.
Support is added for the new 6.10 kernel version, with a patch by Woody
Suwalski.
v0.3.9
This release fixes the build for the soon to be released 6.9 kernel.
Support is tentatively added for the new 0x80 incompatible volume
feature, which appears simple enough so far and isn't causing any
problems.
A console warning that showed up during compressed file reads on recent
kernels is now fixed.
Support is improved for tiny filesystems of under 100 MiB, though they
remain awkward to test due to fragmentation issues.
The behaviour of apfs_modified_by is tweaked to better match the
official driver.
Free queues should now be much harder to fill up. The most important
change here is that files are now deleted across multiple transactions.
v0.3.8
This release reworks ephemeral objects to support larger containers of up to ~7.8 TiB, and to allow the creation of checkpoint mapping blocks.
Also the build is no longer broken for the new 6.8 kernel, thanks to a patch by Woody Suwalski.
v0.3.7
This is a small release that fixes the dkms build, recently broken by
the implementation of version reporting. From now on I will run a dkms
build before each new tag.
The release also lifts the ban on filesystems with half-written backup
superblocks, a problem that some users appear to have encountered
already.
v0.3.6
This release heavily reworks the node defragmentation and split logic to
fix a handful of rarely triggered data corruption bugs. The new version
is easier to understand and hopefully more robust.
Support is added for containers with a size of up to ~6.7 TiB, improving
the previous maximum of ~1.3 TiB. The next release will probably keep
pushing this limit.
Changes are made to the way that subvolume "devices" are reported. Now
we are closer to matching the behaviour of btrfs and userland tools like
Nautilus are far less confused.
The driver version information is now provided by both the on-disk
filesystem metadata and by modinfo. This may be useful for responding to
bugs at some point.
A few small issues with snapshot reporting have been addressed, as well
as an mmap-related warning in recent kernel versions.
Finally, support is added for the 6.7 kernel version (released today),
contributed by Woody Suwalski.
v0.3.5
This release adds support for reading compressed files of arbitrary
on-disk size, which is becoming more and more necessary in recent ipsw
images.
A number of bugs are addressed for systems with little ram, reported by
Gilgamesh via email.
Support is added for the 6.6 kernel version, mainly thanks to Woody
Suwalski. I'm afraid the driver sometimes triggers a warning for recent
kernels, but I didn't manage to fix it in time for the new upstream
release, and it's better to at least get things to build.
v0.3.4
v0.3.3
This release fixes builds for kernels below 5.3, which have all been
broken for a while. So far development has only been focused on Linux
5.3, and I've relied on reporters to find out about issues on other
versions. From now on I will at least run builds for a range of kernels
before each release, so hopefully this won't happen again.
v0.3.2
This release improves error messages, which will hopefully make it
easier to communicate with bug reporters. A number of bugs are also
addressed, most importantly a missing check on the node count limit for
the free queues, which could trigger reports of corruption in some rare
cases (no data loss though, as far as I can see).
Support is added for the 6.3 kernel version, courtesy of Woody Suwalski.
I was hoping to wait until encryption was ready before making a release,
but I'm not finding much time for apfs these days so that could take a
while. In the meantime, it's better to get this stuff out the door.
v0.3.1
Snapshots and clones seem to be working properly now, though testing has
been somewhat limited. As far as I know (I could definitely be wrong),
this is the last thing that was needed to fully support writes to
unencrypted volumes, so it's an important change that warrants a new
release. Everything remains experimental, of course.