Jorgen Lundman

[02df13125fe160520e76f0670179c4c80d34ddf0](https://github.com/openzfsonosx/openzfs/commit/02df13125fe160520e76f0670179c4c80d34ddf0) https://openzfsonosx.org/forum/viewtopic.php?f=20&t=3677&p=11754#p11754

All the ZFS active threads are waiting in `zio_wait()` for IO to complete. It is as if the device stopped responding. Can you coax it into speaking again using `zpool...

It's just how it works, they both handle 256 char names, just the size of char is different meaning hfs has potentially more room due to how utf8 does multibyte...

UTF16 was the first, inefficient, encoding system before the cool new UTF8 came out.. that'd be a step backwards :)

Leaving this as a feature that we might get around to eventually. It seems MSDOS handles long names transparently so that is an option.

Could we get some concrete examples, copy paste in filenames that fail. The dataset property values of normalization, casesensitivity. And panic stack.

OK yes, that very easily caused a panic, it would write over the space given when it decomposed the character at the end. Hopefully these two will help: https://git.io/JnsCZ https://git.io/JnsiT...

I attempted to check if Catalina worked last week, but found that VMWare Fusion does not work with it yet. I've been waiting for a fix for fusion :)

OK, so in Catalina it appears our `zfs.fs` is not being used, this means the devdisk mounts will fail - so you are better off having devdisk=off for now. `diskarbitrationd.log`:...

OK, turns out we should have a `/Library/Filesystems/zfs.fs/Contents/Resources/fsck_zfs`. We do compile one in `cmd/fsck_zfs` which is more or less just `/bin/true`. With that in the bundle, everything appears to function...