Is machine name allowed for login?
Hi all, I am asking very basic,simple question here.I am using iscsi- initiator-utils-6.2.0.865-0.2.fc7. iscsiadm -m discovery -t sendtargets -p ip:port It says that ip:port should be specified.It worked with 'machine name' stead of 'ip' also. iscsiadm -m node -T targetname -p ip:port --login But login command didn't work with replacing 'ip' by 'machine name'. What should I do? is it way to login by 'machine name'.otherwise I will have to disallow discovery using 'machine name'. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Maintaining /dev/sdx path after changes and/or reboots?
Hey Guys, I'm new to iSCSI so I apologize if this has been covered. My background has been primarily FC Storage dealing with Unix Host's, FC HBA's, FC Switch's and Large Monolithic arrays. Anyway, part of the FC Storage world that I've come to depend on is LUN binding on the host. Meaning that /dev/ path entries correlate to the same backend LUNS all the time. Adding/Removing LUNS, rebooting will not effect the /dev/ path - LUN host mapping. Can this be done using open-iscsi in Linux? /dev/sdc1 - iqn. :LUN00 Host Mount /ora0 /dev/sdd1 - iqn. :LUN01 Host Mount /ora1 etc. Thanks for any info. Cheers, Peter --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Maintaining /dev/sdx path after changes and/or reboots?
phub03 schrieb: Hey Guys, I'm new to iSCSI so I apologize if this has been covered. My background has been primarily FC Storage dealing with Unix Host's, FC HBA's, FC Switch's and Large Monolithic arrays. Anyway, part of the FC Storage world that I've come to depend on is LUN binding on the host. Meaning that /dev/ path entries correlate to the same backend LUNS all the time. Adding/Removing LUNS, rebooting will not effect the /dev/ path - LUN host mapping. Can this be done using open-iscsi in Linux? /dev/sdc1 - iqn. :LUN00 Host Mount /ora0 /dev/sdd1 - iqn. :LUN01 Host Mount /ora1 Look into /dev/disk/ and use these paths rather than /dev/sdX. -- Tomasz Chmielewski http://wpkg.org --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Maintaining /dev/sdx path after changes and/or reboots?
Thanks for the info but I don't follow. These appear to be links back the actual device entry. rwxrwxrwx 1 root root 9 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:0dd4e167-ba0b-ceb6-fd0e-e0074378b270-lun-0 - ../../sdc lrwxrwxrwx 1 root root 10 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:0dd4e167-ba0b-ceb6-fd0e-e0074378b270-lun-0- part1 - ../../sdc1 lrwxrwxrwx 1 root root 9 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:cd490ea9-61e1-4b3f-b40b-cae467c46259-lun-0 - ../../sdd lrwxrwxrwx 1 root root 10 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:cd490ea9-61e1-4b3f-b40b-cae467c46259-lun-0- part1 - ../../sdd1 Maybe it's a lack of understanding of how Linux creates the device entries. Could you explain this in more detail? What would my fstab look like and how would I ensure the correlation remains? Not just the mount point entries but the actual device entries? Thanks again !! On Jan 15, 11:06 am, Tomasz Chmielewski man...@wpkg.org wrote: phub03 schrieb: Hey Guys, I'm new to iSCSI so I apologize if this has been covered. My background has been primarily FC Storage dealing with Unix Host's, FC HBA's, FC Switch's and Large Monolithic arrays. Anyway, part of the FC Storage world that I've come to depend on is LUN binding on the host. Meaning that /dev/ path entries correlate to the same backend LUNS all the time. Adding/Removing LUNS, rebooting will not effect the /dev/ path - LUN host mapping. Can this be done using open-iscsi in Linux? /dev/sdc1 - iqn. :LUN00 Host Mount /ora0 /dev/sdd1 - iqn. :LUN01 Host Mount /ora1 Look into /dev/disk/ and use these paths rather than /dev/sdX. -- Tomasz Chmielewskihttp://wpkg.org --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Maintaining /dev/sdx path after changes and/or reboots?
phub03 schrieb: Thanks for the info but I don't follow. These appear to be links back the actual device entry. rwxrwxrwx 1 root root 9 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:0dd4e167-ba0b-ceb6-fd0e-e0074378b270-lun-0 - ../../sdc lrwxrwxrwx 1 root root 10 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:0dd4e167-ba0b-ceb6-fd0e-e0074378b270-lun-0- part1 - ../../sdc1 lrwxrwxrwx 1 root root 9 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:cd490ea9-61e1-4b3f-b40b-cae467c46259-lun-0 - ../../sdd lrwxrwxrwx 1 root root 10 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:cd490ea9-61e1-4b3f-b40b-cae467c46259-lun-0- part1 - ../../sdd1 Maybe it's a lack of understanding of how Linux creates the device entries. Could you explain this in more detail? What would my fstab look like and how would I ensure the correlation remains? Not just the mount point entries but the actual device entries? /dev/sdX, as you observed, can be dynamic. Paths in /dev/disk/by-path/ are static and are just links pointing to a correct /dev/sdX device. If you set scsi_sn on your target, you will have shorter names in /dev/disk/by-id (no partitions though). And if you want to use fstab, you probably want to use device labels (-L option in tune2fs, mkswap, see man fstab). -- Tomasz Chmielewski http://wpkg.org --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
iferror -38
I have created two virtual machines with oracle VM which is Xen based VM and installed openfiler 2.3 on one VM and Centos 5.2 on another VM as iscsi client which has iscsi initiator. the client could discover the target successfully with iscsiadm -m discovery -t sendtargets -p IP address of the target iscsiadm -m node -l gives the sucessful message but I could not see any block devices in /dev. Instead of /dev/sda , it is showing as /dev/sga i did cat /proc/partitions and it is showing sda there. But in /dev/ it is showing as /dev/sga, instead of ./dev/sda. So I am not able to partion the /dev/sga as it says ' it is not a block device' I checked the syslog with tail -f /var/log/messages and it has the following error messages rac2 iscsid: received iferror -38 rac2 last message repeated 2 times rac2 iscsid: connection1: o is operational after recovery rac2 kernel : ping timeout of 5 sec expired , last rx 825664 , last ping 826914, now 828164 rac2 kerenl : connection 1:0:iscsi:detected conn error (1011) rac2 kerenl: sd 0:0:0:2: SCSCI error : retrun code =0x0002 rac2 kernel: end_request : I/O error on dev sdc, logical block 0 rac2 kerenl : Buffere I/O error on device sda, logical block 0 rac2 kernel : Dev sdc: unnable to read RDB block 0 rac2 iscsid : kerenel reports ISCSI connection 1:0 error (1011) state 3 I stuckup here for weekes and not able to move forward. I need to install Oracle rac on Oracle VM for testing with openfiler. Any help is appreciated I am very very thankful on this Thanks Chava --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: iferror -38
Mike, Thank you for your fast response. I have tried installing the following rpm kernel-xen-2.6.18-128.el5.i686.rpm . But it did not help. Do we need to do any additional things after installing that rpm? i did rpm -Uvh kernel-xen-2.6.18-128.el5.i686.rpm on Cent 5.2 But it could not help. Thanks Chava Mike Christie wrote: chava45 wrote: I have created two virtual machines with oracle VM which is Xen based VM and installed openfiler 2.3 on one VM and Centos 5.2 on another VM as iscsi client which has iscsi initiator. Is the 5.3 kernel out yet? If not could you try this kernel http://people.redhat.com/dzickus/el5/128.el5/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Maintaining /dev/sdx path after changes and/or reboots?
Thanks!! I'll give it a try. Cheers! On Jan 15, 1:39 pm, Tomasz Chmielewski man...@wpkg.org wrote: phub03 schrieb: Thanks for the info but I don't follow. These appear to be links back the actual device entry. rwxrwxrwx 1 root root 9 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:0dd4e167-ba0b-ceb6-fd0e-e0074378b270-lun-0 - ../../sdc lrwxrwxrwx 1 root root 10 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:0dd4e167-ba0b-ceb6-fd0e-e0074378b270-lun-0- part1 - ../../sdc1 lrwxrwxrwx 1 root root 9 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:cd490ea9-61e1-4b3f-b40b-cae467c46259-lun-0 - ../../sdd lrwxrwxrwx 1 root root 10 2009-01-15 10:42 ip-10.17.179.130:3260-iscsi- iqn.1986-03.com.sun:02:cd490ea9-61e1-4b3f-b40b-cae467c46259-lun-0- part1 - ../../sdd1 Maybe it's a lack of understanding of how Linux creates the device entries. Could you explain this in more detail? What would my fstab look like and how would I ensure the correlation remains? Not just the mount point entries but the actual device entries? /dev/sdX, as you observed, can be dynamic. Paths in /dev/disk/by-path/ are static and are just links pointing to a correct /dev/sdX device. If you set scsi_sn on your target, you will have shorter names in /dev/disk/by-id (no partitions though). And if you want to use fstab, you probably want to use device labels (-L option in tune2fs, mkswap, see man fstab). -- Tomasz Chmielewskihttp://wpkg.org --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Is machine name allowed for login?
AFAIK, This might be because u might have multiple interfaces up with different ip address. Now a target can provide for a login event only via the specified ip:port as the target is mapped to that interface. On Thu, Jan 15, 2009 at 10:26 PM, Mike Christie micha...@cs.wisc.eduwrote: HIMANSHU wrote: Hi all, I am asking very basic,simple question here.I am using iscsi- initiator-utils-6.2.0.865-0.2.fc7. iscsiadm -m discovery -t sendtargets -p ip:port It says that ip:port should be specified.It worked with 'machine name' stead of 'ip' also. This works in discovery, but iscsiadm -m node -T targetname -p ip:port --login But login command didn't work with replacing 'ip' by 'machine name'. does not work here because it is not implemented yet. You have to actually pass the login command whatever the target gave us in sendtargets discovery. So if it gave us a machine name you can use it. If it gave us a ip then you have to use it. Do not ask when it will be fixed. It is on the TODO, but I do not have much time right now. What should I do? is it way to login by 'machine name'.otherwise I will have to disallow discovery using 'machine name'. -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Maintaining /dev/sdx path after changes and/or reboots?
On 15 Jan 2009 at 7:59, phub03 wrote: Hey Guys, I'm new to iSCSI so I apologize if this has been covered. My background has been primarily FC Storage dealing with Unix Host's, FC HBA's, FC Switch's and Large Monolithic arrays. Anyway, part of the FC Storage world that I've come to depend on is LUN binding on the host. Meaning that /dev/ path entries correlate to the same backend LUNS all the time. Adding/Removing LUNS, rebooting will not effect the /dev/ path - LUN host mapping. That's generally not true: System s like HP-UX have persistent I/O-path to device name mappings (/etc/ioconfig, etc.), but systems like Linux recreate the devices every boot or every module load. If you use non-continuous LUNs and then restart the SCSI module, the device names after a filled gap will change. Same for FC and iSCSI (IMHO). Can this be done using open-iscsi in Linux? /dev/sdc1 - iqn. :LUN00 Host Mount /ora0 /dev/sdd1 - iqn. :LUN01 Host Mount /ora1 Someone more competent than I will answer, I'm sure. Ulrich etc. Thanks for any info. Cheers, Peter --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
