[Bug 227848] Re: boot order wrong for iscsi
This bug was fixed in the package open-iscsi - 2.0.865-1ubuntu3.1 --- open-iscsi (2.0.865-1ubuntu3.1) hardy-proposed; urgency=low * Backport changes from jaunty to allow iscsi targets to be activated as network interfaces come on-line: - debian/open-iscsi.init: + Support for being called from ifup/ifdown scripts. + Refactor start functions: - move daemon start to startdaemon function. - don't exit if the daemon is already running during sanitychecks. Instead check in startdaemon if the daemon needs to be started. - only start automatic targets if necessary. LP: #227848. -- Steve LangasekWed, 17 Jun 2009 23:56:00 + ** Changed in: open-iscsi (Ubuntu Hardy) Status: Fix Committed => Fix Released -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Branch linked: lp:ubuntu/hardy-proposed/open-iscsi -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Branch linked: lp:ubuntu/karmic/open-iscsi -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Tags added: verification-done ** Tags removed: verification-needed -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Quick test lead me to believe that open-iscsi 2.0.865-1ubuntu3.1 from hardy-proposed work as explained by Steve. That is, the block device appear after the bonded Ethernet is brought up. It is too late for the file system on the iSCSI target to be mounted from /etc/fstab, but at least we do not have to restart the open-iscsi service for the iSCSI block device to show up. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 227848] Re: boot order wrong for iscsi
Chris Puttick wrote: > Consider me confused on the basis of my earlier comment showing how to > configure Hardy so that iscsi volume mounts works consistently. It > ain't broke, why fix it? That is because you are not accessing the iSCSI target through a bonded Ethernet interface. With plain Ethernet interface, it always work just fine. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Accepted open-iscsi into hardy-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: open-iscsi (Ubuntu Hardy) Status: In Progress => Fix Committed ** Tags added: verification-needed -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 227848] Re: boot order wrong for iscsi
Consider me confused on the basis of my earlier comment showing how to configure Hardy so that iscsi volume mounts works consistently. It ain't broke, why fix it? -- My employers website: http://thehumanjourney.net - opinions in this email are however very much my own and may not reflect that of my current employer, past employers, associates, friends, family, pets etc.. Documents attached to this email may be in ISO 26300 format: http://iso26300.info -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
I've uploaded a backported fix for the open-iscsi part of this to hardy- proposed, waiting now for review. ** Changed in: open-iscsi (Ubuntu Hardy) Status: Confirmed => In Progress -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
The biggest blocker for getting this fixed in hardy isn't bug #44194, but rather Debian bug #383073 and Debian bug #383123 that were fixed in a post-hardy merge of sysvinit. Without that fix, there's no way to trigger mounting iscsi devices after they've been made available, which is the problem to be solved: the network interfaces are only *guaranteed* to be up after S40networking, and nothing in hardy will trigger mounting of non-network-filesystem devices after that point. Fixing 44194 would let us cover all our bases for things such as iSCSI + wpa_supplicant, but that's not actually an interesting use case to the typical iSCSI user and not the problem being discussed here; fixing this bug without 44194 would not be a regression since /usr on iSCSI doesn't work today for anyone in hardy. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Changed in: open-iscsi (Ubuntu Intrepid) Status: In Progress => Won't Fix -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Note: Hardy 8.04.2 2.6.24-18-virtual #1 SMP (running on KVM virtual machine with dual guest CPU) /etc/network/interfaces (relevant part) auto eth1 iface eth1 inet static address 192.168.20.50 netmask 255.255.255.224 ISCSI auto connect and mount works with no modifications using the following: In /etc/iscsi/iscsid.conf set node.startup = automatic (manual is the default setting) In /etc/iscsi/nodes///default set node.conn[0].startup = automatic (manual is the default setting) Note that the target name and IP address would normally be the only entries in their respective directories, assuming you only have the one SAN target and volume. I guess if you have more you'd want to make the change in all of them :) In /etc/fstab add the following line(s). UUID /opt/ktdms/var/Documents/ auto _netdev 0 0 Note to get the UUID do blkid /dev/sd after you have connected your iscsi volume, manually or otherwise. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
I wouldn't recommend including this in Hardy, since it's known to break wpasupplicant (see bug 44194) and we haven't even sorted that out in Jaunty yet. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Is this going to be fixed in Hardy as well? Thanks in advance. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Changed in: open-iscsi (Ubuntu Hardy) Assignee: Mathias Gug (mathiaz) => (unassigned) -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Changed in: open-iscsi (Ubuntu Hardy) Assignee: (unassigned) => Mathias Gug (mathiaz) -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Changed in: open-iscsi (Ubuntu Hardy) Importance: Undecided => High Status: New => Confirmed Target: None => ubuntu-8.04.3 -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
This bug was fixed in the package open-iscsi - 2.0.870.1-0ubuntu1 --- open-iscsi (2.0.870.1-0ubuntu1) jaunty; urgency=low * New upstream release: - Support 2.6.26/27 kernels (LP: #289470). - Fix iscsid shutdown (LP: #181188). * Merge from Debian. Remaining Ubuntu changes: - Note: Debian version isn't 870~rc3 but 869.2 which leads to a big .diff.gz file. Only files in debian/ have been considered for this merge since debian hasn't patched the source. - debian/control, debian/rules, debian/open-iscsi-udeb*: + Add open-iscsi-udeb. - debian/open-iscsi.dirs: + rename dirs to open-iscsi.dirs because of open-iscsi-udeb addition. + drop network/if-up.d/ directory since we're using symlinks instead. + utilities installed in /bin,/sbin rather than /usr/bin,/usr/sbin. - debian/open-iscsi.init: + utilities installed in /bin,/sbin rather than /usr/bin,/usr/sbin. + lsb log messages. + Don't generate initiatorname name (moved to postinst). + Support for being called from ifup/ifdown scripts. + Refactor start functions: - move daemon start to startdaemon function. - call udevadm settle rather then udevsettle (which doesn't do anything useful). - don't exit if the daemon is already running during sanitychecks. Instead check in startdaemon if the daemon needs to be started. - only start automatic targets if necessary. - add waitfordevices function: called during rcS, waits for all automatic targets to be ready. Iscsi targets are considered as local block devices - they don't need to be marked with _netdev in fstab. (LP: #227848) - start targets if not run from rcS. + Check status of iscsid daemon in addition to listing the iscsi sessions when status action is called. + Add iscsid to the list of processes that should not be killed by sendsigs during shutdown (LP: #192080). + Add starttargets, stoptargets and restarttargets to usage message. - debian/rules: + Install utilities /bin,/sbin rather than /usr/bin,/usr/sbin. + Start open-iscsi at S25 (waiting for devices created by ifupdown calls and before local filesystems are checked and mounted) + stop at S41 (after local filesystems are unmounted). Don't use umountiscsi.sh script from debian. (LP: #192080). - debian/initiatorname.iscsi, debian/open-iscsi.postinst: + Generate the random initiatorname during postinstall rather than in the init script. + Don't ship a default initiatorname.iscsi file. - debian/open-iscsi.postinst: + fix init script ordering on upgrades. - debian/open-iscsi.links: + symlink open-iscsi init script in if-up.d and if-down.d directory so that the iscsi subsystem is started/stopped when network interfaces are configured. - debian/open-iscsi.postrm: + delete iscsi configuration when the package is purged. - utils/iscsi_discovery: De-bashify iscsi_discovery. - usr/idbm.c: Fix build failure with new glibc. LP: #299843. * Dropped: - Exit without error if /sys is not available. Otherwise, it's not possible to use this package as a build-dependency (in Debian). - Drop upstream url in long description now that it's in the Homepage field (in Debian). open-iscsi (2.0.870~rc3-0.3) unstable; urgency=low * Non-maintainer upload. * Do not exit with return code 1 in init script, because it breaks upgrades and is a policy violation (Closes: #503070) open-iscsi (2.0.870~rc3-0.2) unstable; urgency=low * Non-maintainer upload. * Drop patch from iscsistart.c which breaks booting from iscsi. (closes: #499508) * Drop patch from version.h which adds an outdated upstream version number. open-iscsi (2.0.870~rc3-0.1) unstable; urgency=low * Non-maintainer upload. * New upstream release - Adds support for Linux 2.6.26 (Closes: #499508) * Fix ">&" redirection bashism in open-iscsi initscript. open-iscsi (2.0.869.2-2.1) unstable; urgency=medium * Non-maintainer upload. * Fix bashism in debian/rules (Closes: #484427) - Move upstream URL to Homepage field. - Bump Standards-Version to 3.8.0. open-iscsi (2.0.869.2-2) unstable; urgency=low * Revert if-up.d approach for logging into automatic targets; just start open-iscsi at rcS.d/S45, and mount _netdev filesystems when open-iscsi is started. * Call udevsettle before mounting open-iscsi (2.0.869.2-1) unstable; urgency=low * New upstream release open-iscsi (2.0.869~rc4-1) experimental; urgency=low * init script: If /sys is not mounted return without error (Closes: #470434, #423368) * Merged changes by Andrew Moise <[EMAIL PROTECTED]> * Adding Andrew as Co-Maintainer * New upstream release (Closes: #474167) * Added flex and bison build-depends * Fixed up init scripts to attempt to handle automatic mounting and unmounting properly (Clo
[Bug 227848] Re: boot order wrong for iscsi
Thanks, Dustin; I've included this text in the release notes, along with a link to this bug. ** Changed in: ubuntu-release-notes Assignee: (unassigned) => Colin Watson (kamion) Status: New => Fix Released -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Suggestion of text for the Intrepid release note (from Etienne Goyer): File systems hosted on iSCSI targets may not be mounted automatically at boot time, even if they have an entry in /etc/fstab, if a bridged or bonded Ethernet interface is required to reach the iSCSI target. As a work-around, you would have to restart the open-iscsi service and manually mount the file system in question after system boot, once the required network interface have been brought up. Systems equipped with a plain Ethernet interface are not affected. :-Dustin -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
I'm lowering this bug from Critical to High, and un-milestoning it for Intrepid release. We're not going to be able to fix this comprehensively, and in a way that does not introduce regressions in time for Intrepid. Rather, I will prepare some text for the Intrepid release notes, helping awareness of the issue. :-Dustin ** Changed in: open-iscsi (Ubuntu Intrepid) Importance: Critical => High Target: ubuntu-8.10 => None -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
I forgot to mention that the bit of code to add to open-iscsi init script is from the Debian open-iscsi 2.0.869 package in unstable. So, we will get it for jaunty in the next sync anyway. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Dustin and myself worked on the bug today. We where able to fix the bug with the following changes: 1. Add the _netdev option to filesystem on iscsi target in /etc/fstab. We cannot do that retroactively for people who already have entries for file system on iscsi target in fstab, so this will need to be documented in the release note for open-iscsi (README.Debian). I filed bug #284107 to make sure we had the option from now on in the installer. 2. Change the boot order of open-iscsi from 25 to anything above 40, as networking is started at 40. Upstream Debian went 45. 3. Add the following bit of code to the open-iscsi init script, at the end of the start() function: -- log_daemon_msg "Mounting network filesystems" MOUNT_RESULT=1 if mount -a -O _netdev >/dev/null 2>&1; then MOUNT_RESULT=0 break fi log_end_msg $MOUNT_RESULT -- This will ensure that the filesystems on iscsi target, marked with option _netdev in fstab, will get mounted. I have tested the above successfully. I have also tested without the _netdev option, with other file system marked with _netdev, with the iscsi target unreachable, etc, and it seem to behave correctly. Also, the networking init script have a bit of code in check_network_file_systems() to ensure that there is no network file systems or block device currently in use before bringing network down. I think it should also look for iscsi target. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 227848] Re: boot order wrong for iscsi
That's still too late for local iscsi filesystems. :-Dustin -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
The patch sent by Dustin already changes the open-iscsi script from S25 to S47, and (as we saw here) it seems that this is enough to mount any storage volume after the network is up. However, the original open-iscsi script position (S25) is before S45 (waitnfs) and S46 (mountnfs-bootclean), and in a case where one uses ordinary interfaces (as said in two posts above), udev makes everything work and so any NFS filesystems get mounted. But now (with the patch), open-iscsi will load AFTER the NFS scripts. Wouldn't be better to move the open-iscsi script to a value between 40 and 45 (40 < open-iscsi < 45), BEFORE the NFS scripts, allowing to be mounted over iSCSI volumes ? -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Changed in: open-iscsi (Ubuntu) Importance: Undecided => Critical Target: None => ubuntu-8.10 -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Debian have fixed two related bugs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423851 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438542 The solution might be to sync from Debian. Package 2.0.869~rc4-1 is supposed to include modification to the init script that would fix this problem (and related problem of having the iscsi initiator killed before the filesystem are unmounted). However, it requires filesystem on iscsi to be marked with the _netdev option in fstab. I can test that early next week (unfortunately not able to for the next few days). -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
The above solution is not entirely right, as the open-iscsi init script will be run after /etc/rcS.d/mountall.sh, which mean that filesystem in /etc/fstab that reside on iSCSI will not be available when mountall.sh is ran. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
** Changed in: open-iscsi (Ubuntu) Status: Incomplete => In Progress -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Patch attached. :-Dustin ** Attachment added: "open-iscsi.227848.debdiff" http://launchpadlibrarian.net/18342692/open-iscsi.227848.debdiff -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
I did the same as Christian Roessner, above: moved the open-iscsi link from S25 to S42 in rcS.d. This is the preferred method, as - he also pointed out - change the network order it's NOT a good idea. Also, like Etienne Goyer stated, if you are using an "ordinary" interface (ethX), udev may load things in the right order. I'm using a bridged interface (br0) and so udev doesn't bring it up, making necessary the change above. Maybe that's the case with bonded interfaces as well. But, in my opinion, it doesn't matter if one is using ordinary interfaces or not - open-iscsi MUST be started AFTER networking, since it depends on the network to do its job. It's a matter of logic So, the open-iscsi installation script should be changed to reflect the solutions found here - change its number from S25 to something above S40. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
I also have seen the wron startup ordering. But I only have moved the open-iscsi from S25 to S47 in rcS.d. It must start _after_ networking and not before. Changing network-ordering seems not to be a good idea IMHO. Everything is working with this simple change. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
I have a fairly consistent boot process now that mounts iSCSI drives. Here are the changes I made to the default init scripts symlinks order: rc0.d : changed K25open-iscsi to K44open-icsi rc6.d: changed K25open-iscsi to K44open-iscsi rcS.d: Changed S40networking to S23networking in /etc/init.d, I added a sleep 10 as the last statement of the "start" block of code in open-iscsi. this delays the boot process a bit, but allows the iSCSI disks to initialize fully before the fsmount stuff kicks in. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
Having similar major problems utilizing iSCSI effectively with Heron. I have changed the Boot script order in rcS.d so iSCSI is now S44 instead of S25 ( starts iscsi AFTER networking ) and I now have iSCSI drives available to the system. However, it's proving difficult to get the boot order right for initiation and mounting of iSCSI drives to be automatic and effective as part of the boot process. For example, if we want to hold service data on SAN iSCSI drives ( e.g. SAMBA file shares, LDAP or MySQL databases) we need to have the iSCSI drives fully mounted and available at the service startup scripts kick in. Currently with the default setup of iSCSI, this does not happen. Continuing to investigate and experiment , but any further tips to effectively get iSCSI usable as a system drive would be appreciated. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227848] Re: boot order wrong for iscsi
The problem, I believe, come from the fact that open-iscsi is brought up (S25 in /etc/rcS.d) before networking (S40 in /etc/rcS.d). It is my understanding that udev bring interfaces up as they are discovered, which mean that "bare" interfaces (eth0, eth1, etc) happen to be brought up before /etc/rcS.d/S25open-iscsi is run, in which case it is all fine. However, if you depend on an interface not being brought up by udev to reach the iSCSI target (such as a bonded interface, as it is the case above), then open-iscsi indeed come up before there is a path to its target and fail. I tried setting node.conn[0].timeo.login_timeout to a large value, as Soren suggested earlier, but it did not change anything for me. -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
