https://bugzilla.novell.com/show_bug.cgi?id=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c36 Hannes Reinecke <hare@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|hare@suse.com | --- Comment #36 from Hannes Reinecke <hare@suse.com> 2011-10-10 11:43:49 UTC --- boot.open-iscsi is _NOT_ a NOOP. It is absolutely essential if you want to run with root on iSCSI. Problem here is that while the iSCSI connection works perfectly without any daemon, the error recovery logic does _not_. And we have to stop the daemon at the end of the initrd run as we're switching over to a new root fs, and can't have any daemons running which would still be referencing the old root fs. So between the time the iscsi daemon is stopped at the end of initrd run and the daemon being started from the 'normal' init scripts no iSCSI exception handling can take place. Any network interruption here will lead to an immediate system stall, with no chance of recovery other than reboot. Hence we should keep this window as small as possible. Now, as iscsi is normally dependent on the network setup, the daemon would be started rather late. The purpose of the boot.open-iscsi script is to start the daemon _as early as possible_, basically just after udev has started. Experience shows that the highest I/O traffic is during mounting / checking of the local filesystems, as then fs logs will be replayed etc. Which also means that any I/O exception is most likely to occur at this time. When we were to delete the boot.open-iscsi script no daemon would be running at this time and the system would stall. With daemon running the error recovery logic would relogin into the iSCSI target and the system boots as normal. -- 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.