JMoVS

Thanks @rottegift - this is indeed a draft and needs thorough testing and potentially more work - now marked as draft!

I think the relevant line in disk utility GUI is "connection type" which is "USB" for other disks and in the zvol case is "image"

on CLI, diskutil info, it might be related to `protocol type USB` vs `Disk Image`

it also shows up as "solid state disk", which in my case it clearly isn't - it's on a 100% HDD pool. So that could also be adjusted.

I think we have an answer to the code comment here: https://github.com/openzfsonosx/openzfs/blob/4696d5527d0a9a18dad4a9c3cd23300903fdfdaf/module/os/macos/zfs/zvolIO.cpp#L128 We should switch this from "file" to whatever non-file is called. Virtual is fine (virtual, synthesized etc) -...

Looking into https://opensource.apple.com/source/IOStorageFamily/IOStorageFamily-260.100.1/IOStorageProtocolCharacteristics.h.auto.html I see the following options for us to change to: - kIOPropertyPhysicalInterconnectTypeVirtual ~According to Apple:~ Their documentation/code comments are messed up I think... ``` kIOPropertyInterconnectFileKey his key...

Here another panic, just minutes after importing the pool: https://gist.github.com/JMoVS/688585ca6495d33f48dd45f587c7dc6e

and one more after import: ``` panic(cpu 7 caller 0xfffffe0019c40888): Kernel data abort. at pc 0xfffffe00185a9e10, lr 0xcfa77e00185c2ddc (saved state: 0xfffffe3fe9882f10) x0: 0x0000000000000000 x1: 0xfffffe4002fc1ac0 x2: 0x0000000000000000 x3: 0xfffffe3fe9883128 x4:...

I can no longer import the pool without panicing: ``` panic(cpu 5 caller 0xfffffe0023c40888): Kernel data abort. at pc 0xfffffe00225a9e10, lr 0xed8b7e00225c2ddc (saved state: 0xfffffe3feaf52f10) x0: 0x0000000000000000 x1: 0xfffffe4002f61d00 x2:...

import -n panic: https://gist.github.com/JMoVS/20f3247c0dfa05b745cdfec83ac91b79