Dennis Olsson <DOlsson(a)WEB.de> changed:
What |Removed |Added
--- Comment #41 from Dennis Olsson <DOlsson(a)WEB.de> 2012-03-11 22:48:47 CET ---
It sounds like you want /etc/init.d/boot.open-iscsi to
be modified to only try
to start the iscsi daemon if it is not already running, as per attachment (id=450703).
Correct (see also comment 39 for reason why).
Do you also want changes to /etc/init.d/open-iscsi
from the previous attachment (id=450697) [details]?
Yes, also correct.
The removal of "/etc/init.d/boot.open-iscsi" in this attachment must be ignored
(as per Hannes comment 36), while this script is *needed*, although it then
needs the fix above to work correctly in cases, where iSCSI is used on systems,
where the root file system is not located on an iSCSI device.
Lastly, are the patches that Hannes suggested already
handled? It looks like
one of them is, from comment #8, but not sure about the one from comment #7.
You will have to ask Hannes about this.
As far as I am concerned, these patches are unrelated to my original report (as
far as I can overview).
And what about /etc/sysconfig/initrd? I am really not
sure about adding such a
template to fix this problem, when only the "root_iscsi=1" option is needed
The "initrd" template suggested in attachment (id=450695) covers other cases
then just using an iSCSI device without having the root file system on an iSCSI
This template is the sum of my experience with "mkinitrd" over time, where I
have been forced to overwrite various oddities found with "mkinitrd", the iSCSI
case as reported here just being the lastest.
Just to fix the reported iSCSI problem, the template is probably "an overkill",
but then again the template covers more than just the iSCSI issue fix, so why
not include all of it? ;-)
Notice the fix to "mkinitrd" itself, too, in the attachment (id=450695) --
There is a rather annoying bug in "mkinitrd" that needs to be fixed!
See also bug 717590, which was created to keep track of this "follow up" bug.
This bug also contains a newer and better patch to fix this bug.
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.