initramfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: si-wei liu <si-wei.liu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Lee Duncan
	<leeman.duncan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Cathy Zhou <cathy.zhou-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: open-iscsi <open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC dracut 1/1] unexpected boot failure due to races between iscsistart for multiple interfaces
Date: Thu, 21 Dec 2017 22:20:40 -0800	[thread overview]
Message-ID: <ed8d3e69-1e22-356e-efd6-a2f4b277d43b@oracle.com> (raw)
In-Reply-To: <C94AC86B-C41E-4B3A-B375-3405E25BD45D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>



On 12/21/2017 05:03 PM, Lee Duncan wrote:
> That seems like the wrong approach to me. iscsiadm/iscsid were designed for this. The iscsistart script was designed for sing, one-shot use, and is not used in dracut now at all, AFAIK.
The latter is not true, unfortunately. Distros like OpenSUSE and SLES 
does move to iscsiadm to manage sessions for their dracut fork,  
however, the upstream dracut still uses iscsistart now. The context is 
that it might take a while for the SUSE patches to be upstream ready, 
hence we need an interim that addressed the particular iSCSI boot issue 
when dealing with multiple interfaces, until iscsiadm dracut patches 
become avail. Please see:

https://www.spinics.net/lists/linux-initramfs/msg04502.html
https://www.spinics.net/lists/linux-initramfs/msg04505.html
https://www.spinics.net/lists/linux-initramfs/msg04506.html


Thanks,
-Siwei

>
> —
> Lee Duncan
>

      parent reply	other threads:[~2017-12-22  6:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 20:14 [RFC dracut 1/1] unexpected boot failure due to races between iscsistart for multiple interfaces cathy.zhou-QHcLZuEGTsvQT0dZR+AlfA
     [not found] ` <1512418484-3948-1-git-send-email-cathy.zhou-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-12-08 19:09   ` Cathy Zhou
     [not found] ` <9326cbf7-b533-4cf2-baac-6699ee5dc4d6@googlegroups.com>
     [not found]   ` <a759d3d3-5c21-4a28-a205-1390561abc2a@googlegroups.com>
     [not found]     ` <213a0c37-587e-7375-341b-680faa752cde@oracle.com>
     [not found]       ` <B00ADBFE-F00B-4BCD-A7FE-0FEFE2A64F9D@gmail.com>
     [not found]         ` <B00ADBFE-F00B-4BCD-A7FE-0FEFE2A64F9D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-21 18:54           ` Cathy Zhou
     [not found]             ` <29030bdf-e65a-dc01-ee1e-48498dafdc8f-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-12-22  1:03               ` Lee Duncan
     [not found]                 ` <C94AC86B-C41E-4B3A-B375-3405E25BD45D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-22  6:20                   ` si-wei liu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed8d3e69-1e22-356e-efd6-a2f4b277d43b@oracle.com \
    --to=si-wei.liu-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=cathy.zhou-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=leeman.duncan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).