|
Description
|
The iscsi initaitor code generates events on the first connection to the
target device. When the target device node is dead, the access from the intiator
fails with ENOENT and when the target device node is available the access is
successfull, but the iscsi initiator code does not generate events on
the target device availability.
This behaviour create problem for the ZFS configurations created on iscsi devices.
A ZFS mirrored pool is created from iscsi targets which are coming from
different nodes. When one target node goes down, the ZFS marks the pool as
degraded and it is not able to detect the device even when target node is up.
The ZFS behavior is that when a disk comes back online, it is notified by a
hotplug event which the ZFS recieves and takes proper action.
The lack of proper events by iscsi initiator prevents ZFS to autodetect and
requires manual intervention to inform ZFS that device is online.
See comments section on the observation regarding the event generation.
|