Thanks for the scripts, but I would like to avoid hardcoding pool names
anywhere. Due to specific roles of my ZFS servers it is possible to export all
zpools at iSCSI stop and import all visible pools at iSCSI start. So, I end up
with following modifications:
/lib/svc/method/iscsi-initiator:
30 ноября 2016 г. 17:45:53 CET, "Дмитрий Глушенок" пишет:
>The 'reboot' works, but it kills all processes at once (including
>iscsid), leaving no chances for ZFS to flush write cache. And I suspect
>that with current iscsi/initiator SMF service implementation the same
>happens
The 'reboot' works, but it kills all processes at once (including iscsid),
leaving no chances for ZFS to flush write cache. And I suspect that with
current iscsi/initiator SMF service implementation the same happens (but for
some reason sync(), which is being called by 'reboot' after killing
> Does anybody uses ZFS over iSCSI?
>
> There is problem with reboots as iscsi-initiator service does not
> taking care of ZFS while shutting down. It leads to zpool goes into
> UNAVAIL state and then first sync() issued gets blocked with following
> stack:
We have a significant ZFS-over-iSCSI