Issues with external drives

[Michael]

Hi. I have external thunderbolt storage with zfs filesystem on it. When I am disconnecting cable from pc without

Code: Select all

zfs export

command, macOS becomes unresponsive and after some time freezes completely.

Code: Select all

zpool status

responds about suspended pool,

Code: Select all

zpool export/import/clear

commands don't work because of "Suspended pool I/O". Even

Code: Select all

diskutil

freezes in both gui and cli.
Is this intended behavior? If not, I can provide additional information.

I am using O3X 2.2.3, MacOS 15.2 Apple M1.

[Michael]

Looks like this happened because of the InvariantDisks daemon, which was not running. But now I have another issue. After creating a zpool, two zpools are created instead.

Code: Select all

sudo zpool import
   pool: zfstest2
     id: 7842314823970971036
  state: ONLINE
 action: The pool can be imported using its name or numeric identifier.
 config:

   zfstest2                                                            ONLINE
     arm-io@10F00000-usb-drd0@82280000-usb-drd0-port-ss@00200000-@5:0  ONLINE

   pool: zfstest2
     id: 540551148505718693
  state: ONLINE
 action: The pool can be imported using its name or numeric identifier.
 config:

   zfstest2                                     ONLINE
     media-92DD62B1-8958-154F-A7BB-136A4F558D30  ONLINE

They have different storage and, as I understand, they represent /dev/disk4 and /dev/disk4s1 in my test setup.

Code: Select all

/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *480.1 GB   disk4
   1:                        ZFS zfstest2               480.1 GB   disk4s1
   2: 6A945A3B-1DD2-11B2-99A6-080020736631               8.4 MB     disk4s9

Because of it I can't import pool by name and there are probably another issues:

Code: Select all

sudo zpool import zfstest2
cannot import 'zfstest2': more than one matching pool
import by numeric ID instead

And again, is this an intended behavior or something is going wrong?

[Michael]

The issue has been resolved. I had not used ZFS or O3X before, so I may have made a mistake, or something indeed went wrong. Either way, the problem was eventually solved after performing a couple of zpool destroy commands and erasing the disks. It might be better to use /var/run/disk/by-id links with the zpool create command instead of relying on /dev/disk identifiers.

[nodarkthings]

I'm not using external drives for ZFS, but I think you HAVE TO do

Code: Select all

zpool export yourpoolname

before disconnecting your drive!