boot order wrong for iscsi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Colin Watson | ||
open-iscsi (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Unassigned | ||
Intrepid |
Won't Fix
|
High
|
Unassigned |
Bug Description
Binary package hint: open-iscsi
The boot order is still wrong in some cases for iscsi.
iscsi probably waits for networking to start (due to upstart and dependencies) but it does not wait long enough, so "link" are available before.
Trace from bootup:
root@hest:~# dmesg | perl -ane 'print if $_ =~ /(eth|bond|
[ 145.733504] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 146.052622] e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 146.372001] e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 146.701361] e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 154.506735] Driver 'sd' needs updating - please use bus_type methods
[ 154.506382] Driver 'sr' needs updating - please use bus_type methods
[ 163.088171] eth4: NIU Ethernet 00:14:4f:bb:23:a8
[ 163.088176] eth4: Port type[XMAC] mode[10G:FIBER] XCVR[XPCS] phy[xgf]
[ 164.305607] eth5: NIU Ethernet 00:14:4f:bb:23:a9
[ 164.305611] eth5: Port type[XMAC] mode[10G:FIBER] XCVR[XPCS] phy[xgf]
[ 165.450618] Loading iSCSI transport class v2.0-724.
[ 165.461844] iscsi: registered transport (tcp)
[ 165.505437] iscsi: registered transport (iser)
[ 169.129554] Ethernet Channel Bonding Driver: v3.2.3 (December 6, 2007)
[ 169.129563] bonding: MII link monitoring set to 100 ms
[ 169.297933] e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 169.321894] bonding: bond0: enslaving eth0 as a backup interface with an up link.
[ 169.447624] e1000: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 169.461239] bonding: bond0: enslaving eth1 as a backup interface with an up link.
[ 169.597327] e1000: eth2: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 169.610971] bonding: bond0: enslaving eth2 as a backup interface with an up link.
[ 169.747033] e1000: eth3: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 169.760631] bonding: bond0: enslaving eth3 as a backup interface with an up link.
[ 170.102554] ADDRCONF(
[ 177.340214] ADDRCONF(
[ 188.001939] bond0: no IPv6 routers present
So the iscsi is tried to start at 165 and first at 177 the link is ready.
Changed in open-iscsi: | |
status: | Incomplete → In Progress |
Changed in open-iscsi: | |
importance: | Undecided → Critical |
milestone: | none → ubuntu-8.10 |
Changed in open-iscsi: | |
importance: | Undecided → High |
milestone: | none → ubuntu-8.04.3 |
status: | New → Confirmed |
Changed in open-iscsi: | |
assignee: | nobody → mathiaz |
Changed in open-iscsi: | |
assignee: | mathiaz → nobody |
Changed in open-iscsi (Ubuntu Intrepid): | |
status: | In Progress → Won't Fix |
tags: |
added: verification-done removed: verification-needed |
I'm not too hot on the idea of changing the ordering. 0].timeo. login_timeout to a higher value (60 seconds should be more than enough) in /etc/iscsi/ iscsid. conf, does that solve it for you?
If you change node.conn[