It has been while since I used raw device names ever since I got in habit of labeling the partitions; I create a large, single partition even when using the whole disk in a pool.
By chance are/were you using "/etc/fstab" to mount file systems?
@parvXm For better or worse, I was running off a ZFS pool created by the guided installer.
Trying to get the devices relabeled in the pool has proven to be quite a pain in the ass
@bentsukun @rtyler Tried a few ways of setting up devices for #zfs on #netbsd - raw devices, numbered dk wedges, and named wedges with /etc/rc.d/devpubd (by default on netbsd-9 devpubd runs _after_ zfs, which means an additional reboot to an autoconfigured system), and named wedges have ended up working well, even in the case of renumbering devices
Oh, and concatenating mixed size disks into something that _looks lke_ a viable zfs setup, but thats another story :) https://netbsd0.blogspot.com/2022/05/the-journey-to-zfs-raidz1-with.html
@rtyler that shouldn't happen. Zfs has metadata and the device name doesn't matter per say. Devices can move around and it should be fine. Now I have had issues with zfs where if I replaced a drive, but left the old drive in the machine, the kernel would find the old drive and some of the new drives, but not all of them and not boot. The solution was to remove.thd old drives when booting so zfs wouldn't be confused.
The short is that zfs just uses the first drives it finds, even if there is an actual configuration that would work.
Welcome to hacky.town, a small Mastodon server for free and open source data hackers