- Feb 25, 2011
- 16,991
- 1,620
- 126
Stock Ubuntu 16 server (CLI, systemd.) apt-get upgrade/update to latest everything.
Configured a VM today as a file server, booting from a smallish vmdk, with a single large iSCSI LUN from the SAN for mass storage. Then created a zpool out of the LUN, because folks the server is for want journaling and snapshotting. (Yay ZFS.)
Everything worked right at first, but when I reboot the VM, the zpool doesn't get mounted. I can see in /var/log/syslog that the zfs services are trying to auto-import the pool, which is not there yet. 4 seconds later (timestamps) iscsid kicks in, logs into the target, and multipath creates the /dev/mapper virtual device.
I've "worked around" the problem by adding this to /etc/rc.local:
...but it leaves a bad taste in my mouth. Unfortunately, I can't find much online about service load order for Ubuntu 16. Anybody have any ideas?
Configured a VM today as a file server, booting from a smallish vmdk, with a single large iSCSI LUN from the SAN for mass storage. Then created a zpool out of the LUN, because folks the server is for want journaling and snapshotting. (Yay ZFS.)
Everything worked right at first, but when I reboot the VM, the zpool doesn't get mounted. I can see in /var/log/syslog that the zfs services are trying to auto-import the pool, which is not there yet. 4 seconds later (timestamps) iscsid kicks in, logs into the target, and multipath creates the /dev/mapper virtual device.
I've "worked around" the problem by adding this to /etc/rc.local:
Code:
sleep 10
zpool import [poolname]
zfs mount -a...but it leaves a bad taste in my mouth. Unfortunately, I can't find much online about service load order for Ubuntu 16. Anybody have any ideas?
Facebook
Twitter