From: Martin Wilck <mwilck-l3A5Bk7waGM@public.gmane.org>
To: Cathy Zhou <cathy.zhou-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
si-wei liu <si-wei.liu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: Vasanth Vemula <vasanth.vemula-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Subject: Re: iscsi netboot failure in case of multiple interfaces
Date: Fri, 17 Nov 2017 20:11:12 +0100 [thread overview]
Message-ID: <1510945872.16284.37.camel@suse.de> (raw)
In-Reply-To: <0a3f48bc-d110-e163-22a5-795c2d554297-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On Fri, 2017-11-17 at 10:34 -0800, Cathy Zhou wrote:
> Martin,
>
> Thanks. I will take a detail look of the diff you sent. But a brief
> browse of it raised one question: assuming we solely use iscsid and
> iscsiadm instead of iscsistart, wouldn't iscsid be started outside
> of
> iscsiroot.sh? Otherwise, the restart/stop/start of iscsid for one
> interface could interfere with another iscsiroot instance for
> another
> interface?
Yes, certainly, the iscsid service should be started only once.
Please note that I'm not the author of the patch I linked, and that
this link I sent was also just a starting point:
https://github.com/danimo/dracut/commits/obs_from_git/modules.d/95iscsi
Note also that this branch is quite a bit behind upstream dracut in
other areas, so porting the iSCSI changes may not be trivial.
Regards,
Martin
next prev parent reply other threads:[~2017-11-17 19:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 18:55 iscsi netboot failure in case of multiple interfaces Cathy Zhou
[not found] ` <3d6d6a40-692f-6c7f-fadd-ef6ccaab510d-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-11-13 18:43 ` Cathy Zhou
[not found] ` <98407a21-3e1d-6355-1ba5-f732afb674d7-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-11-15 13:12 ` Martin Wilck
[not found] ` <1510751540.17501.55.camel-l3A5Bk7waGM@public.gmane.org>
2017-11-15 19:17 ` Cathy Zhou
[not found] ` <d15c3567-509e-7bcd-62e9-6930b203753b-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-11-15 19:47 ` si-wei liu
[not found] ` <08997d6f-0b94-af50-d407-0c4803a70697-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-11-16 13:03 ` Martin Wilck
[not found] ` <1510837385.10823.6.camel-l3A5Bk7waGM@public.gmane.org>
2017-11-17 18:34 ` Cathy Zhou
[not found] ` <0a3f48bc-d110-e163-22a5-795c2d554297-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-11-17 19:11 ` Martin Wilck [this message]
[not found] ` <1510945872.16284.37.camel-l3A5Bk7waGM@public.gmane.org>
2017-11-18 0:09 ` si-wei liu
[not found] ` <70c4311d-ef4b-ee59-712d-930e173e289e-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-11-18 0:17 ` Martin Wilck
[not found] ` <1510964277.7555.4.camel-l3A5Bk7waGM@public.gmane.org>
2017-11-18 0:42 ` si-wei liu
[not found] ` <c8e88ebe-4a91-738a-d1c4-067e9f0c4df6-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-11-21 21:34 ` Martin Wilck
[not found] ` <1511300063.25459.148.camel-l3A5Bk7waGM@public.gmane.org>
2017-11-21 21:58 ` si-wei liu
[not found] ` <90870cf5-a5a0-6a2f-4568-4998b69d4aa3-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-11-21 22:03 ` Martin Wilck
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=1510945872.16284.37.camel@suse.de \
--to=mwilck-l3a5bk7wagm@public.gmane.org \
--cc=cathy.zhou-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=si-wei.liu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=vasanth.vemula-QHcLZuEGTsvQT0dZR+AlfA@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 NNTP newsgroup(s).