I would still prefer to be able to do this with the initial zpool create though if possible. $ sudo zpool import -d /dev/disk/by-id -aN Create your zpool with /dev/sdX devices first, then do this: $ sudo zpool export tank
I found a thread for zfsonlinux on Github that suggested a workaround. Is there a way to force zpool on 16.04 to respect my drive references when creating a pool? Or alternatively, are my misgivings about what its doing here misplaced? Update: Workaround It looks like zpool followed the symlinks, rather than referencing them. I get this with zpool status: NAME STATE READ WRITE CKSUM
Drives aren't always in the same order in /dev when a machine reboots, and if you have other drives in the machine the pool may fail to mount correctly.įor example, running zpool status on a 14.04 box I get this: NAME STATE READ WRITE CKSUMĪta-Hitachi_HDS722020ALA330_ ONLINE 0 0 0Īta-Hitachi_HUA722020ALA330_ ONLINE 0 0 0īut when I create a new pool on 16.04 with this (abbreviated): zpool create pool raidz \ When creating pools, I always reference drives by their serials in /dev/disk/by-id/ (or /dev/disk/gpt on FreeBSD) for resiliency. I'm giving the bundled OpenZFS on Ubuntu 16.04 Xenial a try.
0 kommentar(er)
