From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cathy Zhou Subject: Re: iscsi netboot failure in case of multiple interfaces Date: Wed, 15 Nov 2017 11:17:34 -0800 Message-ID: References: <3d6d6a40-692f-6c7f-fadd-ef6ccaab510d@oracle.com> <98407a21-3e1d-6355-1ba5-f732afb674d7@oracle.com> <1510751540.17501.55.camel@suse.de> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1510751540.17501.55.camel-l3A5Bk7waGM@public.gmane.org> Content-Language: en-US Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Martin Wilck , initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: Si-Wei , Vasanth Vemula Martin, Thank you very much for your insights. See inline: On 11/15/2017 5:12 AM, Martin Wilck wrote: > Hello Cathy, > > On Mon, 2017-11-13 at 10:43 -0800, Cathy Zhou wrote: >> Dracut experts, >> >> A gentle reminder ... Looking forward to gaining some insights on >> below >> questions. > I haven't analyzed your scenario in detail, but IMHO this is a long- > standing issue. dracut is using both iscsid and iscsistart, which is > wrong. iscsistart is meant for situations where iscsid is not > available. It starts iscsid at startup, and stops it again when done. > If proper iscsid is running, iscsiadm should be used rather than > iscsistart to activate sessions. I agree. I was confused when I saw both iscsid and iscsistart were started in dracut. That is why my proposal (a) was to stop the iscsid service first before it starts iscsistart service. It fixed our problem though I am not sure if it has some unexpected effect on some other scenario. > > In my experience, iscsistart will only work reliably if you have just a > single interface. Could you please elaborate on this? What issue you saw? It seems to me as long as iscsistart works without iscsid is running, multiple instances should also be fine? Thanks very much again - Cathy > > Martin >