On Thu, Mar 03, 2016 at 10:16:45PM +0200, Erez Zilber wrote: > Hi, > > I'm running iSCSI boot for RHEL & SUSE nodes. Sometimes, after > iscsistart is called, errors on the iSCSI target side occur (e.g. temp > network disconnection) and the iSCSI connection is disconnected. In > the boot log, it looks like this (on a RHEL node): > > connection1:0: detected conn error (1020) > > And then, of course, the node fails to boot. > > I would expect that iscsid would handle this and reconnect, but I > don't see in the boot log that iscsid was started. I also took a look > at /usr/share/dracut/modules.d/95iscsi/iscsiroot, but didn't find > iscsid there.
No, if the connection fails during boot I don't think it's covered as you found out. Of course if you're booting from iSCSI, a network disruption while the iSCSI boot firmware or bootloader is running is also probably fatal. > Is it possible to run iscsid as part of initrd, before iscsistart is executed? Transitioning iscsid from the initrd is problematic. Processes started in the initrd don't have the right view of the filesystem, aren't in the proper security context, etc. If we kill the initrd started process and restart, there's still a time gap. And iscsistart does not play well with a running iscsid. iscsistart basically runs the internals of iscsid, and feeds itself commands over a unix socket. If iscsid is running it already has the socket bound, the commands will go to iscsid, and the final command tells iscsid to exit. I've looked at switching iscsistart to use socketpair(2) to prevent that and possibly let multiple iscsistarts run in parallel. - Chris -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
