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 -~--~~~~--~~--~--~---
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: 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 -~--~~~~--~~--~--~---
