Dr. Volker Jaenisch wrote: > Hi Mike! > > Thank you very much! You gave a push in the right direction! > > Mike Christie schrieb: >> On the initiator side running 2.6.24 and 2.0.865.15, I >> > I simply booted both machines with 2.6.24 and now the connection > handshake runs. > > iscsi_discovery 10.6.0.2 -tiser > iscsiadm: No active sessions. > iscsiadm: Could not read node record for > iqn.2001-04.com.poseidon-de.inqbus.poseidon:disk1 10.6.0.2 3260 default
Start over from scratch. We support upgrading to new /etc/iscsi/node formats, but not downgrading well. Just do rm -f -r /etc/iscsi/nodes rm -f -r /etc/iscsi/send_targets Then retry iscsi_discovery > Set target de.inqbus.poseidon:disk1 to automatic login over iser to > portal 10.6.0.2:3260 > Logging out of session [sid: 1, target: de.inqbus.poseidon:disk1, > portal: 10.6.0.2,3260] > Logout of [sid: 1, target: de.inqbus.poseidon:disk1, portal: > 10.6.0.2,3260]: successful > discovered 1 targets at 10.6.0.2 > > But then again a connection error occurs. > what error exactly? > dmesg on initiator: > > iser: iser_connect:connecting to: 10.6.0.2, port 0xbc0c > iser: iser_cma_handler:event 0 conn ffff81021cd84b80 id ffff81021cd4e400 > iser: iser_cma_handler:event 2 conn ffff81021cd84b80 id ffff81021cd4e400 > iser: iser_create_ib_conn_res:setting conn ffff81021cd84b80 cma_id > ffff81021cd4e400: fmr_pool ffff81021bd49ec0 qp ffff81021cde2200 > iser: iser_cma_handler:event 9 conn ffff81021cd84b80 id ffff81021cd4e400 > iser: iscsi_iser_ep_poll:ib conn ffff81021cd84b80 rc = 1 > scsi7 : iSCSI Initiator over iSER, v.0.1 > iser: iscsi_iser_conn_bind:binding iscsi conn ffff81021d401a58 to > iser_conn ffff81021cd84b80 > scsi 7:0:0:0: RAID IET Controller 0001 PQ: 0 ANSI: 5 > scsi 7:0:0:1: Direct-Access IET VIRTUAL-DISK 0001 PQ: 0 ANSI: 5 > sd 7:0:0:1: [sde] 83886080 512-byte hardware sectors (42950 MB) > sd 7:0:0:1: [sde] Write Protect is off > sd 7:0:0:1: [sde] Mode Sense: 79 00 00 08 > sd 7:0:0:1: [sde] Write cache: enabled, read cache: enabled, doesn't > support DPO or FUA > sd 7:0:0:1: [sde] 83886080 512-byte hardware sectors (42950 MB) > sd 7:0:0:1: [sde] Write Protect is off > sd 7:0:0:1: [sde] Mode Sense: 79 00 00 08 > sd 7:0:0:1: [sde] Write cache: enabled, read cache: enabled, doesn't > support DPO or FUA > sde: unknown partition table > sd 7:0:0:1: [sde] Attached SCSI disk > iser: iser_cma_handler:event 10 conn ffff81021cd84b80 id ffff81021cd4e400 > connection1:0: iscsi: detected conn error (1011) If you mean this one it can probably be ignored. It is a bug and is expected with stgt. > iser: iscsi_iser_ep_disconnect:ib conn ffff81021cd84b80 state 3 > iser: iser_cq_tasklet_fn:comp w. error op 0 status 5 > iser: iser_cq_tasklet_fn:comp w. error op 0 status 5 > iser: iser_cq_tasklet_fn:comp w. error op 0 status 5 > iser: iser_cq_tasklet_fn:comp w. error op 0 status 5 > iser: iser_free_ib_conn_res:freeing conn ffff81021cd84b80 cma_id > ffff81021cd4e400 fmr pool ffff81021bd49ec0 qp ffff81021cde2200 > iser: iser_device_try_release:device ffff81021bd497c0 refcount 0 > iscsi: cmd 0x12 is not queued (6) > sd 7:0:0:1: [sde] Synchronizing SCSI cache > iscsi: cmd 0x35 is not queued (6) > iscsi: cmd 0x35 is not queued (6) > iscsi: cmd 0x35 is not queued (6) > sd 7:0:0:1: [sde] Result: hostbyte=DID_NO_CONNECT > driverbyte=DRIVER_OK,SUGGEST_OK this is sort of expected because of the top issue, but it reminds me that you should use 2.6.26 upstream kernel to fix some other shutdown bugs in 2.6.24 and use the iscsi modules in there. Then use only the tools in the open-iscsi tarball release (do not use the open-iscsi tarball modules (I guess you have figured that out already to make this work)). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---
