Re: Adding New ISCSI LUN to Target, How does client iSCSI initiator access new Lun
thx, it helped me to find the discovered lun On Tuesday, October 5, 2010 8:08:47 AM UTC-4, Rahsaan Page wrote: Thank You Mike, This is very appreciated Sent from my HTC on the Now Network from Sprint! - Reply message - From: Mike Christie mich...@cs.wisc.edu javascript: Date: Mon, Oct 4, 2010 5:00 pm Subject: Adding New ISCSI LUN to Target, How does client iSCSI initiator access new Lun To: open-...@googlegroups.com javascript: Cc: Rahsaan Page rahsaa...@gmail.com javascript: On 10/03/2010 02:08 PM, Rahsaan Page wrote: Hello All, I have a question, when you add a new lun to iscsi target, if client iSCSI initiator is already logged in to target, do i have to restart the client iSCSI initiator for it to see the new lun? how can i make client iSCSI initiator see new lun with out restarting iSCSI initiator and losing connection to current Target and Lun's? If you use a target that sends the iscsi async pdu with REPORT_LUNS_DATA_CHANGED then the new luns should be added automatically for you (deleted luns are not removed though and need to be manually deleted). If it is not getting automatically added then you need to run either //rescan all sessions for new luns iscsiadm -m session --rescan // rescan specific session iscsiadm -m session -R $SID --rescan (see the README for other variants) This commands only add new luns. If you want something that adds and deletes luns then use the rescan-bus.sh script in the sg utils. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: iSCSI Driver hangup for IBM V3700
Hi Rushi, Please upgrade the V3700 to latest code , Xen support is added with V7.2 release. Specifically this problem signature was certainly fixed in 7.2 GA. Let me know if you still have issues with latest code. Kind regards, Anil. On 4/3/2014 8:02 PM, Rushikesh Jadhav wrote: Hello Forum, We have a IBM V3700 and 4 Xenserver6.2 hosts. We are facing trouble in adding SR from it and below are the logs generated in kern.log n2 kernel: [429671.643262] connection19:0: pdu (op 0x2c itt 0x1) rejected. Reason code 0x7 n2 kernel: [429671.643302] connection19:0: pdu (op 0x2a itt 0x1) rejected. Reason code 0x4 n2 kernel: [429671.643354] connection19:0: pdu (op 0x2b itt 0x1) rejected. Reason code 0x4 n2 kernel: [429671.643524] connection19:0: pdu (op 0x2f itt 0x1) rejected. Reason code 0x4 n2 kernel: [429671.643554] connection19:0: pdu (op 0x2e itt 0x1) rejected. Reason code 0x4 n2 kernel: [429671.643703] connection19:0: pdu (op 0x2d itt 0x1) rejected. Reason code 0x4 n2 kernel: [429671.643750] connection19:0: pdu (op 0x33 itt 0x1) rejected. Reason code 0x4 n2 kernel: [429671.643846] connection19:0: pdu (op 0x35 itt 0x1) rejected. Reason code 0x7 Unfortunately VMs running from existing iSCSI luns face IO timeout as the LUNs on host hang. This hang occurs as soon as the new LUN is getting added. Existing luns can be recovered only if we do restart iscsid and get no success in adding additional luns. The iscsid is running with default parameters. The iscsi module losses all LUN access even for non-IBM as soon as it tries to mount LUN from IBM-V3700. The iscsi rpm is open-iscsi-2.0.871-0.20.3.xs1120 Regards, Rishi -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com mailto:open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com mailto:open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
iSCSI tgtd synology
Hello, I'm not familiar with any of iscsi stuff. however i tried a lot of stuff to get my synology nas working with opennebula. OpenNebula is an open-source cloud computing toolkit for managing heterogeneous distributed data center infrastructures. The OpenNebula toolkit manages a data center's virtual infrastructure to build private, public and hybrid implementations of infrastructure as a service. I asked around in the opennebula community and they told me the problem with the iSCSI implementation is that it's tied to tgtd. It's a requirement. If your iSCSI server is not a linux box + tgtd then you will need to develop new drivers or use other drivers. so my question now is how do i know if my synology uses tgtd? can anyone help me please -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
