Most stable modules, daemon
I've been using Debian with a custom 2.6.18 kernel config, then doing a 'make install' of open-iscsi daemon and modules. I am switching to CentOS 5.4 with a custom kernel config based on 2.6.18 (specifically http://wiki.openvz.org/Download/kernel/rhel5/028stab066.10 ). Should I install the modules and daemon of 2.0-871 from open- iscsi.org, or should I just install the iscsi-initiator-utils from the yum repo of CentOS 5.4? How can I make sure I have the most stable iscsi modules and daemon? Thanks, Dave -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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: open-iscsi on SUSE 11
On 13 Jan, 14:31, Hannes Reinecke h...@suse.de wrote: Stuart Little wrote: Hi, Using open-iscsi-2.0.869-8.1 (x86_64) on a SUSE 11.0 based machine, connecting to an HP D2D. Is that OpenSUSE 11.0 or SLES11? This is SLES11. I still have not had a chance to try the settings changes to fix the 'work on boot' issue, hopefully will do so soon. Cheers, Stuart -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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.
problems with setup
I have a new VM running Mandriva, I am writing a file manager website that will allow clients to upload files to our server via http. I want to store those files on my SAN so I've installed open-iscsi. I can't seem to get it to discover though. I am using the package install of open-iscsi. I've run iscsiadm -m discovery -p 10.10.82.43:3260 it returns #BEGIN RECORD 2.0-871 discovery.startup = manual discovery.type = sendtargets discovery.sendtargets.address = 10.10.82.43 and goes on through. The instructions I read said to restart iscsi after this and I tried. here is what I get [r...@localhost r...@localhost iscsi]# /etc/init.d/open-iscsi restart Detaching nodes: OK stopping iscsi initiator service: OK STarting iscsi initiator service: OK Attaching nodes: iscsiadm: no records found. Any help would be appreciated. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@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: Most stable modules, daemon
On 01/19/2010 11:07 AM, dave wrote: I've been using Debian with a custom 2.6.18 kernel config, then doing a 'make install' of open-iscsi daemon and modules. I am switching to CentOS 5.4 with a custom kernel config based on 2.6.18 (specifically http://wiki.openvz.org/Download/kernel/rhel5/028stab066.10 ). Should I install the modules and daemon of 2.0-871 from open- iscsi.org, or should I just install the iscsi-initiator-utils from the yum repo of CentOS 5.4? How can I make sure I have the most stable iscsi modules and daemon? I would use the centos code if you want stability. If you want features then use the open-iscsi.org code. I backport features and fixes from upstream/open-iscsi.org/kernel.org to RHEL, then Centos picks them up. I normally get the critical bug fixes, but do not get all the features because the risk to port the feature would be too great. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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: problems with setup
On 01/19/2010 11:15 AM, Billy Ronie wrote: I have a new VM running Mandriva, I am writing a file manager website that will allow clients to upload files to our server via http. I want to store those files on my SAN so I've installed open-iscsi. I can't seem to get it to discover though. I am using the package install of open-iscsi. I've run iscsiadm -m discovery -p 10.10.82.43:3260 You forgot the discovery type param. iscsiadm -m discovery -p 10.10.82.43:3260 -t st -P 1 This will instruct iscsiadm to perform SendTargets iscsi discovery and the -P 1 tells it to print it out what it found nicely. When you run that command you should see something like: iscsiadm -m discovery -t sendtargets -p ip:port -P 1 Target: iqn.1992-08.com.netapp:sn.33615311 Portal: 10.15.84.19:3260,2 Iface Name: default Portal: 10.15.85.19:3260,3 Iface Name: default -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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: problems with setup
Forgive any typos since I'm working in the vsphere client window I can't copy out the message, but here is the reply I get from that command. iscsiadm: Cannot perform discovery. Initiatorname required. iscsiadm: Discovery process to 10.10.82.43:326 failed to create a discovery session iscsiadm: Could not perform SendTargets discovery. Thanks for your quick replies I've been stuck on this for hours with no luck. -Will On Tue, Jan 19, 2010 at 2:21 PM, Mike Christie micha...@cs.wisc.edu wrote: On 01/19/2010 11:15 AM, Billy Ronie wrote: I have a new VM running Mandriva, I am writing a file manager website that will allow clients to upload files to our server via http. I want to store those files on my SAN so I've installed open-iscsi. I can't seem to get it to discover though. I am using the package install of open-iscsi. I've run iscsiadm -m discovery -p 10.10.82.43:3260 You forgot the discovery type param. iscsiadm -m discovery -p 10.10.82.43:3260 -t st -P 1 This will instruct iscsiadm to perform SendTargets iscsi discovery and the -P 1 tells it to print it out what it found nicely. When you run that command you should see something like: iscsiadm -m discovery -t sendtargets -p ip:port -P 1 Target: iqn.1992-08.com.netapp:sn.33615311 Portal: 10.15.84.19:3260,2 Iface Name: default Portal: 10.15.85.19:3260,3 Iface Name: default -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@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: problems with setup
On 01/19/2010 02:32 PM, Billy Ronie wrote: Forgive any typos since I'm working in the vsphere client window I can't copy out the message, but here is the reply I get from that command. iscsiadm: Cannot perform discovery. Initiatorname required. iscsiadm: Discovery process to 10.10.82.43:326 failed to create a discovery session iscsiadm: Could not perform SendTargets discovery. Thanks for your quick replies I've been stuck on this for hours with no luck. In /var/log/messages do you see something from iscsid about missing Initiatorname or missing initiatorname.iscsi file? It should be there around the time you do service iscsi start? Or do you see something about missing iscsi modules or missing or invalud version and something about scsi_transport_iscsi? To install this did you do make install? If so you should have a file under /etc/iscsi/initiatorname.iscsi and in that file you should have a line Initiatorname=iqn.2001-08.something.something If you do not, then create one and instead of something.something add whatever you want the name to be. Then start the iscsi service /etc/init.d/open-iscsi start that should start iscsid which should read the initiatorname.iscsi and load all the iscsi modules including scsi_transport_iscsi. Then run the discovery command again. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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: problems with setup
You were exactly right, I had the file already but didn't know what was supposed to go there. I've been pretty unsuccessful at understanding all this so far. This time it replied exactly like you said it would, my only question is what now. If you have a link that would give me some more instructions I'm happy to read up, I just haven't found anything that has the things I've been looking for. Thanks very much again for your help -Will On Tue, Jan 19, 2010 at 3:48 PM, Mike Christie micha...@cs.wisc.edu wrote: On 01/19/2010 02:32 PM, Billy Ronie wrote: Forgive any typos since I'm working in the vsphere client window I can't copy out the message, but here is the reply I get from that command. iscsiadm: Cannot perform discovery. Initiatorname required. iscsiadm: Discovery process to 10.10.82.43:326 failed to create a discovery session iscsiadm: Could not perform SendTargets discovery. Thanks for your quick replies I've been stuck on this for hours with no luck. In /var/log/messages do you see something from iscsid about missing Initiatorname or missing initiatorname.iscsi file? It should be there around the time you do service iscsi start? Or do you see something about missing iscsi modules or missing or invalud version and something about scsi_transport_iscsi? To install this did you do make install? If so you should have a file under /etc/iscsi/initiatorname.iscsi and in that file you should have a line Initiatorname=iqn.2001-08.something.something If you do not, then create one and instead of something.something add whatever you want the name to be. Then start the iscsi service /etc/init.d/open-iscsi start that should start iscsid which should read the initiatorname.iscsi and load all the iscsi modules including scsi_transport_iscsi. Then run the discovery command again. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@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.
