iSCSI initiator: iscontrol cannot be stopped or killed

[Edward Tomasz Napierała]

On 0303T1445, Aafak Mohammad wrote:
> Problem: the iscontrol process starts normally and establishes
> a session and brings up a device, but it cannot be stopped.
> It does not react to a HUP signal, and neither to KILL.
> 
> The /dev/da0 device is operational and the remote disk remains
> normally accessible, regardless of how I try to (unsuccessfully)
> shutdown the iscontrol process. The ps reports the state of the
> process as "Ds", not doing anything. A ktrace does not show any
> reaction to a received signal. A restart seems to be necessary
> to break the iSCSI session.

Well, that's one of the reasons it's obsolete.  Could you try
to upgrade to 10.1 and try the new iSCSI initiator, iscsictl/iscsid?