... so I've put my external drive internal and no more KP with my slice zpool.
It's clearly an issue with USB that only happens in 10.9.
nodarkthings wrote:Instead, folder icons won't show
> xattr -l /Volumes/tank/testfolder/'Icon^M' | grep ':$'
com.apple.FinderInfo:
com.apple.ResourceFork:
RJVB wrote:nodarkthings wrote:Instead, folder icons won't show
What folder icons? You mean when you set a custom icon via copy/paste in the Finder's GetInfo dialogs or even when copying the source folder's Icon'$'\r' file (using `ditto --rsrc` to be certain)? In the former case the resulting 'Icon'$'\r'' file will not get the resource fork in my quick testing but it does in the latter case:
- Code: Select all
> xattr -l /Volumes/tank/testfolder/'Icon^M' | grep ':$'
com.apple.FinderInfo:
com.apple.ResourceFork:
However, I don't think the resource fork is required; I can use both the above methods to set a folder icon on a folder on an NTFS volume mounted with Paragon's NTFS-for-Mac driver. In fact, the resource fork isn't preserved when I use ditto - AT LEAST NOT as the usual xattr. I'd have to mount the share on Linux to see if another "trick" is used to store resource forks with that driver.
For me folder icons are really icing on the cake; USB stability is definitely not.
Do you have an "old" enclosure or external that is USB2-only and definitely doesn't support UAS(P)? I have seen hangs under Linux when I do large, high-bandwidth transfers over the USB3 port in one of my notebooks. It doesn't KP but I still need to reboot the system to unblock the situation so it boils down a similar annoyance. If transfer rates over the bus have increased significantly in ZFS 2.2x the KP could be a result of the inappropriate handling of the bus reacting in an unexpected manner?
nodarkthings wrote:Yes, it's an old USB2 dock (and I don't have a clue of what UAS(P) is ) so I guess your hypothesis about 2.2.x bandwidth could matter (but why is it working in 10.11 and 10.14, then? )
RJVB wrote:Evidently you can mix and match ZFS 2.1 with 2.2 on different machines. I prefer to avoid it because I don't want to see continuous messages about pools that can be upgraded, or run the risk that a pool I create on 1 system won't import on the other. But I just saw that I might get that even with 2.1.6 because someone backported 2.2 features that aren't available in ZoL 2.1.x (like Blake3 checksums).
Return to OpenZFS on OS X Development
Users browsing this forum: No registered users and 5 guests