I was able to create the pool just fine to create one that looks like:
- Code: Select all
$ zpool status
pool: zbackup
state: ONLINE
scan: scrub repaired 0B in 00:00:01 with 0 errors on Thu Jul 13 13:11:40 2023
config:
NAME STATE READ WRITE CKSUM
zbackup ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
media-431C99C5-1F98-A74A-AEE9-2BC6B5B4B278 ONLINE 0 0 0
media-639ACDB8-6F1D-BB4A-9B99-ACA606BB680E ONLINE 0 0 0
/Users/haravikk/Desktop/disk3.img ONLINE 0 0 0
/Users/haravikk/Desktop/disk4.img ONLINE 0 0 0
errors: No known data errors
$ zpool list -v
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
zbackup 7.27T 610K 7.27T - - 0% 0% 1.00x ONLINE -
raidz2-0 7.27T 610K 7.27T - - 0% 0.00% - ONLINE
media-431C99C5-1F98-A74A-AEE9-2BC6B5B4B278 1.82T - - - - - - - ONLINE
media-639ACDB8-6F1D-BB4A-9B99-ACA606BB680E 1.82T - - - - - - - ONLINE
/Users/haravikk/Desktop/disk3.img 1.82T - - - - - - - ONLINE
/Users/haravikk/Desktop/disk4.img 1.82T - - - - - - - ONLINE
However, the moment I try to offline either of the two sparse files I get an immediate kernel panic. The command I used to offline was:
- Code: Select all
$ zpool offline zbackup /Users/haravikk/Desktop/disk4.img
It doesn't matter which of the two sparse files I offline. I've also tried exporting the pool and moving a file, but I get the same result during import. It seems the moment the pool is in a degraded state a kernel panic is triggered, which doesn't bode well if I were to have an actually failed drive (it would be impossible to replace it as the kernel panic would occur before I could run zpool replace).
In case it's useful, here are the properties for the pool:
- Code: Select all
$ zpool get all zbackup
NAME PROPERTY VALUE SOURCE
zbackup size 7.27T -
zbackup capacity 0% -
zbackup altroot - default
zbackup health ONLINE -
zbackup guid 9167587832427214874 -
zbackup version - default
zbackup bootfs - default
zbackup delegation on default
zbackup autoreplace off default
zbackup cachefile - default
zbackup failmode wait default
zbackup listsnapshots off default
zbackup autoexpand on local
zbackup dedupratio 1.00x -
zbackup free 7.27T -
zbackup allocated 610K -
zbackup readonly off -
zbackup ashift 9 local
zbackup comment - default
zbackup expandsize - -
zbackup freeing 0 -
zbackup fragmentation 0% -
zbackup leaked 0 -
zbackup multihost off default
zbackup checkpoint - -
zbackup load_guid 11601007956795242925 -
zbackup autotrim off default
zbackup compatibility off default
zbackup feature@async_destroy enabled local
zbackup feature@empty_bpobj enabled local
zbackup feature@lz4_compress active local
zbackup feature@multi_vdev_crash_dump enabled local
zbackup feature@spacemap_histogram active local
zbackup feature@enabled_txg active local
zbackup feature@hole_birth active local
zbackup feature@extensible_dataset active local
zbackup feature@embedded_data active local
zbackup feature@bookmarks enabled local
zbackup feature@filesystem_limits enabled local
zbackup feature@large_blocks enabled local
zbackup feature@large_dnode enabled local
zbackup feature@sha512 enabled local
zbackup feature@skein enabled local
zbackup feature@edonr enabled local
zbackup feature@userobj_accounting enabled local
zbackup feature@encryption enabled local
zbackup feature@project_quota enabled local
zbackup feature@device_removal enabled local
zbackup feature@obsolete_counts enabled local
zbackup feature@zpool_checkpoint enabled local
zbackup feature@spacemap_v2 active local
zbackup feature@allocation_classes enabled local
zbackup feature@resilver_defer enabled local
zbackup feature@bookmark_v2 enabled local
zbackup feature@redaction_bookmarks enabled local
zbackup feature@redacted_datasets enabled local
zbackup feature@bookmark_written enabled local
zbackup feature@log_spacemap active local
zbackup feature@livelist enabled local
zbackup feature@device_rebuild enabled local
zbackup feature@zstd_compress active local
zbackup feature@draid enabled local
zbackup feature@zilsaxattr enabled local
zbackup feature@head_errlog active local
zbackup feature@blake3 enabled local
And here is the command I used to create the pool:
- Code: Select all
sudo zpool create -f \
-m none \
-o ashift=9 \
-o autoexpand=on \
-o feature@encryption=enabled \
-O relatime=on \
-O casesensitivity=insensitive \
-O compression=zstd \
-O dnodesize=auto \
-O normalization=formD \
-O xattr=sa \
-O com.apple.browse=off \
-O com.apple.ignoreowner=off \
-O com.apple.mimic=hfs \
-O com.apple.devdisk=on \
-O canmount=off \
-O readonly=on \
zbackup raidz2 disk3 disk4 disk3.img disk4.img
I'm attaching a zipped set of multiple kernel panics, though they look pretty much identical to my eye as someone who has no clue.
I'm running ZFS v2.1.6 on macOS High Sierra on an older (2009) Mac Mini for testing, so I'm unable to test v2.1.7rc2 for comparison (as there only currently seem to be releases for Catalina and Ventura). The system is a mostly fresh install (fully updated, very little extra installed).