With the help of many users evaluating and reporting issues, OpenZFS on Windows becomes better and better with very short cycles between release candidates on the way to a release
Correct permissions of mount object (access_denied error with delete)
Work on partitioning disks (incomplete)
SecurityDescriptor work
rc4
mountmgr would deadlock with Avast installed
Change signal to userland to Windows API
Additional mount/unmount changes.
Fixed VSS blocker again
remainig but known problem for zpool import (pool not found)
In Windows 24H2 there seems to be some sort of partition background monitoring active that does an undo of "unknown" partition modifications. A current workaround is to use Active@disk editor (free) to modify sector 200.00 from value 45 to 15
Some apps ask for filesystem type. If not fat*, ntfs or Refs they refuse to work ex start the application from a ZFS pool. As long as Microsoft (or OSX) does not add ZFS (or btrfs) to the list of valid filesystems there is a need of an overrun option.
There is an additional ZFS property for ZFS on OSX and Windows "com.apple.mimic" (property was introduced with ZFS on OSX). Up to rc7 the default was off (=ZFS). This had the effect that some apps do not start from a ZFS pool unless you set com.apple.mimic manually to ntfs. The new behaviour on rc8 is that the default is "ntfs" unless you manually set another property for com.apple.mimic for a "it just works" behaviour.
Setting a different value for com.apple.mimic is possible but only needed in special use cases.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.