mirror of
https://github.com/openzfs/zfs.git
synced 2025-10-01 02:46:29 +00:00
e7b3766a69
After much contemplation I can't see a clean way to use udev entirely in-tree for testing. This patch removed a horrible horrible hack which would copy the needed udev bits in to place on your system to make it work. That however is simply not acceptable, nothing you in in-tree should ever ever ever install something on your system. Since I could not come up with a clean way to use udev in-tree. The fix is to simply parse the zdev config file and create the needed symlinks in a sub-diretory or your working tree. This is not as clean as using udev but it does work perfectly well for in-tree testing.
22 lines
478 B
Bash
22 lines
478 B
Bash
#!/bin/bash
|
|
#
|
|
# Dragon (White Box) Raid-Z2 Configuration (7x10(8+2))
|
|
#
|
|
|
|
RANKS=7
|
|
CHANNELS=10
|
|
|
|
zpool_create() {
|
|
udev_setup ${ETCDIR}/zfs/zdev.conf.dragon.example
|
|
udev_raidz2_setup ${RANKS} ${CHANNELS}
|
|
|
|
msg ${ZPOOL} create ${FORCE_FLAG} ${ZPOOL_NAME} ${RAIDZ2S[*]}
|
|
${ZPOOL} create ${FORCE_FLAG} ${ZPOOL_NAME} ${RAIDZ2S[*]} || exit 1
|
|
}
|
|
|
|
zpool_destroy() {
|
|
msg ${ZPOOL} destroy ${ZPOOL_NAME}
|
|
${ZPOOL} destroy ${ZPOOL_NAME}
|
|
udev_cleanup ${ETCDIR}/zfs/zdev.conf.dragon.example
|
|
}
|