Re: iscsiadm: initiator reported error (9 - internal error)
On Jul 12, 2012, at 12:31 AM, parveen kumar wrote: Dear Mike Christie, First of all thanks for replying to my first mail :) . M not building my own kernel m just using the centos and trying to mount LUN from my SAN storage through iscsi, But i dont know how to enable the crc32c module ? It should be done for you if you are using the centos kernel. Before trying to do any iscsi commands just run lsmod | grep crc Do you see the crc32c module? If not try modprobe crc32c Do you see it now? If not look in /lib/modules/$YOUR_KERNEL/kernel/crypto do you see it (I am not sure if it was built as a module in centos 5.3). -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: iscsiadm: initiator reported error (9 - internal error)
On Jul 12, 2012, at 4:32 AM, parveen kumar wrote: Dear Mike Christi, I had done steps that you given but not get crc32c, also checked in /lib/modules/$YOUR_KERNEL/kernel/crypto but not found crc32c ? Do you have the crc32c_intel one instead? any other solution ? Send the /boot/config-$YOUR_KERNEL file so I can see how your kernel was compiled. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: iscsiadm: initiator reported error (9 - internal error)
On Jul 12, 2012, at 5:54 AM, parveen kumar wrote: Dear Mike Christie, File attached with this mail. It should be built in. I tried centos 5.6 and it worked for me. Could you try a newer version. I think centos 5.7 or 5.8 is out. Centos 6.1 also worked for me. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Can't discover new targets
On Wed, Jul 11, 2012 at 09:50:17PM PDT, Mike Christie spake thusly: I have not run tgtadm manually for a while but I think you need to also set the ACL for that target? I never had to do anything along these lines for the other targets I have set up... If you just add the targets and luns to /etc/tgt/targets.conf then run service tgtd start does it work? I think the default for that is to just allow any initiator to login without chap so that should work. For a while I was confused as to the difference between tgt-admin and tgtadm. I'm surprised such confusing names were chosen. Just to make sure I've got it straight: tgtadm manually sets up the targets and LUNs and tgt-admin reads/writes the targets.conf config file. The iSCSI HOWTO's for CentOS that I have found all seem to use tgtadm to set things up manually so that is what I have been doing. Since I have recently found out about tgt-admin I have been doing tgt-admin --dump on my iSCSI target machines so I can write out the targets.conf to persist the configs. But when I do tgt-admin --dump I get no output. As if it has nothing configured. But if I do: tgtadm --lld iscsi --mode target --op show I get output as described before showing that targets and LUNs are configured. So...I'm not sure what is going on here. How are target and LUN numbers assigned in targets.conf? I don't see any assigned. I have a feeling they are assigned by order in the config file but that seems risky as you could add a line or stanza and cause everything to shift. One thing I'm wondering about is if it is necessary to have all of the targets assigned sequentially and for the targets to all have LUNs on them. For example I have target 1 with LUN1 then I have targets 2 and 3 with no LUNs and then target 4 with the LUN that I am trying to discover. The fact that targets 2,3 don't have any LUNs doesn't matter does it? Thanks! -- Tracy Reed pgpEpoGsmAiHG.pgp Description: PGP signature
Re: Can't discover new targets
On Jul 12, 2012, at 1:24 PM, Tracy Reed wrote: On Wed, Jul 11, 2012 at 09:50:17PM PDT, Mike Christie spake thusly: I have not run tgtadm manually for a while but I think you need to also set the ACL for that target? I never had to do anything along these lines for the other targets I have set up... So you did not have to run: tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL the ACL information section in the tgtadm -op show command said ALL by default? If so that is all that is needed for simple setup that allows any initiators access. I thought before you had to run the above command for each target when setting them up with tgtadm by hand. If you just add the targets and luns to /etc/tgt/targets.conf then run service tgtd start does it work? I think the default for that is to just allow any initiator to login without chap so that should work. For a while I was confused as to the difference between tgt-admin and tgtadm. I'm surprised such confusing names were chosen. Just to make sure I've got it straight: tgtadm manually sets up the targets and LUNs and tgt-admin reads/writes the targets.conf config file. The iSCSI HOWTO's for CentOS that I have found all seem to use tgtadm to set things up manually so that is what I have been doing. Since I have recently found out about tgt-admin I have been doing tgt-admin --dump on my iSCSI target machines so I can write out the targets.conf to persist the configs. But when I do tgt-admin --dump I get no output. As if it has nothing configured. But if I do: tgtadm --lld iscsi --mode target --op show I get output as described before showing that targets and LUNs are configured. So...I'm not sure what is going on here. Ask the tgt list. I have not worked on tgt code for a long time. How are target and LUN numbers assigned in targets.conf? I don't see any assigned. I have a feeling they are assigned by order in the config file but that seems risky as you could add a line or stanza and cause everything to shift. By default it goes by the order you define them. You can add a lun $num to tell tgt to use a specific value: example: backing-store /dev/sda lun 123 /backing-store Ask the tgt list for more info though. One thing I'm wondering about is if it is necessary to have all of the targets assigned sequentially and for the targets to all have LUNs on them. For example I have target 1 with LUN1 then I have targets 2 and 3 with no LUNs and then target 4 with the LUN that I am trying to discover. The fact that targets 2,3 don't have any LUNs doesn't matter does it? Works for me. I made the mistake of using the same disk for both targets. If you do that make sure you add the allow-in-use yes setting to the targets.conf. If it does not work for you, report it to the tgt list. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: iscsiadm: initiator reported error (9 - internal error)
Dear Mike Christie, i had installed Centos5.7 and Centos6 in seperate machine and try to mount LUN from storage and i got sucess and i had also tried with RHEL5 and RHEL6 but m using centos 5.3 in my machine, basiclly cluster running on this server and some applications also running on this server and i dont want to upgrade this server , only in this machine m not able to mount LUN from storage through ISCSI. oki u r talking about some kernal modules and crc32c what is that ? can u plz share some info regarding this with me. Regards, PARVEEN +919780933599 On Thu, Jul 12, 2012 at 11:26 PM, Mike Christie micha...@cs.wisc.eduwrote: On Jul 12, 2012, at 5:54 AM, parveen kumar wrote: Dear Mike Christie, File attached with this mail. It should be built in. I tried centos 5.6 and it worked for me. Could you try a newer version. I think centos 5.7 or 5.8 is out. Centos 6.1 also worked for me. -- *.* -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
RFC: Doc: FLASH DDB Management using iscsiadm
Hi Mike, We want to work on this solution that would enable qla4xxx users to manage the DDBs in FLASH and migrate the entries from FLASH to user space. Here is our initial thought, please review and let us know your feedback. Add support for FLASH DDB management in iscsiadm = 1. Export normal target entries to /sys/class/iscsi_session from FLASH when the driver comes up /sys/class/iscsi_session/session2 - for the DDB at Flash DDB index 1 /sys/class/iscsi_session/session3 - for the DDB at Flash DDB index 2 /sys/class/iscsi_session/session4 - for target at index 3 in the RAM DDB Note: This will need changes in the driver 2. Export sendtarget entries to /sys/firmware /sys/firmware/send_targets/host0 /sys/firmware/send_targets/host0/target0 /sys/firmware/send_targets/host0/target0/ip_address /sys/firmware/send_targets/host0/target0/port /sys/firmware/send_targets/host0/target0/authentication information Note: This will need changes in the driver 3. Now in user space tools we will have to travers the /sys directories when user wants to display the node records or discoverydb records. On running the command actual node records or discovery db records will also get created in user space. # iscsiadm -m node (for offload iface, need to go through syfs sessions ) qla4xxx: [106] 192.168.1.11:3260,1 iqn.1992-04.com.emc:cx.ckm00101200392.a2 (Flash) qla4xxx: [107] 192.168.1.8:3260,3 iqn.1992-04.com.emc:cx.ckm00101200392.a3 (Flash) qla4xxx: [108] 192.168.1.12:3260,2 iqn.1992-04.com.emc:cx.ckm00101200392.b2 qla4xxx: [109] 192.168.1.9:3260,4 iqn.1992-04.com.emc:cx.ckm00101200392.b3 Note, we will append the node listing with (Flash) if its from the FLASH DDB. # iscsiadm -m discoverydb 192.168.1.11:3260 via sendtargets (Flash) 192.168.1.175:3260 via sendtargets Now since we have the node records and discovery records equivalent to the entries in FLASH user can use iscsiadm command to do login, logout and discovery to records in FLASH. 4. To update a node record user can update the user space node record and then commit it to the FLASH # iscsiadm -m node target name -o update # iscsiadm -m node target name -o apply (commit to flash, valid for offload node) 5. We can also introduce new options to iscsiadm to migrate the FLASH records to open-iscsi database # iscsiadm -m node targetname -o [migrate | migrateall] valid for offload node # iscsiadm -m discoverydb portal -o [migrate | migrateall] valid for offload discoverydb Thanks, Lalit. This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: iscsiadm: initiator reported error (9 - internal error)
Dear Mike Christi, I had done steps that you given but not get crc32c, also checked in /lib/modules/$YOUR_KERNEL/kernel/crypto but not found crc32c ? any other solution ? Regards, PARVEEN +919780933599 On Thu, Jul 12, 2012 at 12:57 PM, Mike Christie micha...@cs.wisc.eduwrote: On Jul 12, 2012, at 12:31 AM, parveen kumar wrote: Dear Mike Christie, First of all thanks for replying to my first mail :) . M not building my own kernel m just using the centos and trying to mount LUN from my SAN storage through iscsi, But i dont know how to enable the crc32c module ? It should be done for you if you are using the centos kernel. Before trying to do any iscsi commands just run lsmod | grep crc Do you see the crc32c module? If not try modprobe crc32c Do you see it now? If not look in /lib/modules/$YOUR_KERNEL/kernel/crypto do you see it (I am not sure if it was built as a module in centos 5.3). -- *.* -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
RFC: Doc: FLASH DDB Management using iscsiadm
Hi Mike, We want to work on this solution that would enable qla4xxx users to manage the DDBs in FLASH and migrate the entries from FLASH to user space. Here is our initial thought, please review and let us know your feedback. Add support for FLASH DDB management in iscsiadm 1. Export normal target entries to /sys/class/iscsi_session from FLASH when the driver comes up /sys/class/iscsi_session/session2 - for the DDB at Flash DDB index 1 /sys/class/iscsi_session/session3 - for the DDB at Flash DDB index 2 /sys/class/iscsi_session/session4 - for target at index 3 in the RAM DDB Note: This will need changes in the driver 2. Export sendtarget entries to /sys/firmware /sys/firmware/send_targets/host0 /sys/firmware/send_targets/host0/target0 /sys/firmware/send_targets/host0/target0/ip_address /sys/firmware/send_targets/host0/target0/port /sys/firmware/send_targets/host0/target0/authentication information Note: This will need changes in the driver 3. Now in user space tools we will have to travers the /sys directories when user wants to display the node records or discoverydb records. On running the command actual node records or discovery db records will also get created in user space. # iscsiadm –m node (for offload iface, need to go through syfs sessions ) qla4xxx: [106] 192.168.1.11:3260,1 iqn.1992-04.com.emc:cx.ckm00101200392.a2 (Flash) qla4xxx: [107] 192.168.1.8:3260,3 iqn.1992-04.com.emc:cx.ckm00101200392.a3 (Flash) qla4xxx: [108] 192.168.1.12:3260,2 iqn.1992-04.com.emc:cx.ckm00101200392.b2 qla4xxx: [109] 192.168.1.9:3260,4 iqn.1992-04.com.emc:cx.ckm00101200392.b3 Note, we will append the node listing with (Flash) if its from the FLASH DDB. # iscsiadm –m discoverydb 192.168.1.11:3260 via sendtargets (Flash) 192.168.1.175:3260 via sendtargets Now since we have the node records and discovery records equivalent to the entries in FLASH user can use iscsiadm command to do login, logout and discovery to records in FLASH. 4. To update a node record user can update the user space node record and then commit it to the FLASH # iscsiadm –m node target name -o update # iscsiadm –m node target name -o apply (commit to flash, valid for offload node) 5. We can also introduce new options to iscsiadm to migrate the FLASH records to open-iscsi database # iscsiadm –m node targetname -o [migrate | migrateall] valid for offload node # iscsiadm –m discoverydb portal -o [migrate | migrateall] valid for offload discoverydb Thanks, Lalit. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/zEdMEt6cD-UJ. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: iscsiadm: initiator reported error (9 - internal error)
On 07/12/2012 11:25 PM, parveen kumar wrote: Dear Mike Christie, i had installed Centos5.7 and Centos6 in seperate machine and try to mount LUN from storage and i got sucess and i had also tried with RHEL5 and RHEL6 but m using centos 5.3 in my machine, basiclly cluster running on this Can you just try to do a clean install of the system with the older OS or use RHEL 5.3 since it seems you have access to that? RHEL 5.3 should work too. server and some applications also running on this server and i dont want to upgrade this server , only in this machine m not able to mount LUN from storage through ISCSI. oki u r talking about some kernal modules and crc32c what is that ? can u It is just some kernel module used for digests. We always load it in case we need it later on. plz share some info regarding this with me. Regards, PARVEEN +919780933599 On Thu, Jul 12, 2012 at 11:26 PM, Mike Christie micha...@cs.wisc.eduwrote: On Jul 12, 2012, at 5:54 AM, parveen kumar wrote: Dear Mike Christie, File attached with this mail. It should be built in. I tried centos 5.6 and it worked for me. Could you try a newer version. I think centos 5.7 or 5.8 is out. Centos 6.1 also worked for me. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: iscsiadm: initiator reported error (9 - internal error)
Dear Mike Christie, So what should i do to resolve this problem now ? What you suggest ? Regards, PARVEEN +919780933599 On Fri, Jul 13, 2012 at 10:17 AM, Mike Christie micha...@cs.wisc.eduwrote: On 07/12/2012 11:25 PM, parveen kumar wrote: Dear Mike Christie, i had installed Centos5.7 and Centos6 in seperate machine and try to mount LUN from storage and i got sucess and i had also tried with RHEL5 and RHEL6 but m using centos 5.3 in my machine, basiclly cluster running on this Can you just try to do a clean install of the system with the older OS or use RHEL 5.3 since it seems you have access to that? RHEL 5.3 should work too. server and some applications also running on this server and i dont want to upgrade this server , only in this machine m not able to mount LUN from storage through ISCSI. oki u r talking about some kernal modules and crc32c what is that ? can u It is just some kernel module used for digests. We always load it in case we need it later on. plz share some info regarding this with me. Regards, PARVEEN +919780933599 On Thu, Jul 12, 2012 at 11:26 PM, Mike Christie micha...@cs.wisc.edu wrote: On Jul 12, 2012, at 5:54 AM, parveen kumar wrote: Dear Mike Christie, File attached with this mail. It should be built in. I tried centos 5.6 and it worked for me. Could you try a newer version. I think centos 5.7 or 5.8 is out. Centos 6.1 also worked for me. -- *.* -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
