Re: Build problems with 869.2
On Aug 27, 1:34 am, Erez Zilber [EMAIL PROTECTED] wrote: If you don't plan to use iSER, you can remove the line the loads it in the init script (where it says something like modprobe ib_iser). If you do plan to use iSER, there's also a solution for that. Erez Rather than having to modify the init scripts on my machines, can I just comment out 'CONFIG_INFINIBAND_ISER=m' in the kernel config next time I rebuild my kernel? Or will I still see those warnings without iser in the kernel? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Build problems with 869.2
open-iscsi 869.2 doesn't seem to want to compile for me. I am compiling against linux-2.6.18 with openvz patches applied from http://wiki.openvz.org/Download/kernel/rhel5/028stab057.2 Any ideas? ak1-vz1:~/open-iscsi-2.0-869.2# make make -C utils/fwparam_ibft make[1]: Entering directory `/root/open-iscsi-2.0-869.2/utils/ fwparam_ibft' cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o fwparam_ibft.o fwparam_ibft.c cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o fw_entry.o fw_entry.c fw_entry.c: In function ‘dump_mac’: fw_entry.c:41: warning: unused variable ‘i’ cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o prom_lex.o prom_lex.c stdout:1622: warning: ‘yyunput’ defined but not used cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o prom_parse.tab.o prom_parse.tab.c cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o fwparam_ppc.o fwparam_ppc.c fwparam_ppc.c: In function ‘loop_devs’: fwparam_ppc.c:352: warning: passing argument 4 of ‘qsort’ from incompatible pointer type make[1]: Leaving directory `/root/open-iscsi-2.0-869.2/utils/ fwparam_ibft' make -C usr make[1]: Entering directory `/root/open-iscsi-2.0-869.2/usr' cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o util.o util.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o io.o io.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o auth.o auth.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o login.o login.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o log.o log.c log.c:325: warning: ‘__dump_char’ defined but not used cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o md5.o md5.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o sha1.o sha1.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o iscsi_sysfs.o iscsi_sysfs.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o idbm.o idbm.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o netlink.o netlink.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o initiator.o initiator.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o scsi.o scsi.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o actor.o actor.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o mgmt_ipc.o mgmt_ipc.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o isns.o isns.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o transport.o transport.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o iscsid.o iscsid.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE util.o io.o auth.o login.o log.o md5.o sha1.o iscsi_sysfs.o idbm.o netlink.o initiator.o scsi.o actor.o mgmt_ipc.o isns.o transport.o iscsid.o -o iscsid cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o strings.o strings.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o discovery.o discovery.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o iscsiadm.o iscsiadm.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE util.o io.o auth.o login.o log.o md5.o sha1.o iscsi_sysfs.o idbm.o ../utils/fwparam_ibft/fw_entry.o ../utils/ fwparam_ibft/fwparam_ibft.o ../utils/fwparam_ibft/fwparam_ppc.o ../ utils/fwparam_ibft/prom_lex.o ../utils/fwparam_ibft/prom_parse.tab.o strings.o discovery.o iscsiadm.o -o iscsiadm cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o iscsistart.o iscsistart.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o statics.o statics.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -static netlink.o util.o io.o auth.o login.o log.o md5.o sha1.o iscsi_sysfs.o idbm.o initiator.o scsi.o actor.o mgmt_ipc.o isns.o transport.o ../utils/fwparam_ibft/ fw_entry.o ../utils/fwparam_ibft/fwparam_ibft.o ../utils/fwparam_ibft/ fwparam_ppc.o ../utils/fwparam_ibft/prom_lex.o ../utils/fwparam_ibft/ prom_parse.tab.o iscsistart.o statics.o -o iscsistart login.o: In function `resolve_address': /root/open-iscsi-2.0-869.2/usr/login.c:168: warning: Using
Re: Build problems with 869.2
Just saw the thread about rhel5 symbol problems, which seems to be my issue. Tried to apply the patch from Erez to 869.2 source, but it failed :( On Aug 26, 2:03 am, v42bis [EMAIL PROTECTED] wrote: open-iscsi 869.2 doesn't seem to want to compile for me. I am compiling against linux-2.6.18 with openvz patches applied fromhttp://wiki.openvz.org/Download/kernel/rhel5/028stab057.2 Any ideas? ak1-vz1:~/open-iscsi-2.0-869.2# make make -C utils/fwparam_ibft make[1]: Entering directory `/root/open-iscsi-2.0-869.2/utils/ fwparam_ibft' cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o fwparam_ibft.o fwparam_ibft.c cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o fw_entry.o fw_entry.c fw_entry.c: In function ‘dump_mac’: fw_entry.c:41: warning: unused variable ‘i’ cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o prom_lex.o prom_lex.c stdout:1622: warning: ‘yyunput’ defined but not used cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o prom_parse.tab.o prom_parse.tab.c cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -c -o fwparam_ppc.o fwparam_ppc.c fwparam_ppc.c: In function ‘loop_devs’: fwparam_ppc.c:352: warning: passing argument 4 of ‘qsort’ from incompatible pointer type make[1]: Leaving directory `/root/open-iscsi-2.0-869.2/utils/ fwparam_ibft' make -C usr make[1]: Entering directory `/root/open-iscsi-2.0-869.2/usr' cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o util.o util.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o io.o io.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o auth.o auth.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o login.o login.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o log.o log.c log.c:325: warning: ‘__dump_char’ defined but not used cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o md5.o md5.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o sha1.o sha1.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o iscsi_sysfs.o iscsi_sysfs.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o idbm.o idbm.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o netlink.o netlink.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o initiator.o initiator.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o scsi.o scsi.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o actor.o actor.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o mgmt_ipc.o mgmt_ipc.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o isns.o isns.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o transport.o transport.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o iscsid.o iscsid.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE util.o io.o auth.o login.o log.o md5.o sha1.o iscsi_sysfs.o idbm.o netlink.o initiator.o scsi.o actor.o mgmt_ipc.o isns.o transport.o iscsid.o -o iscsid cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o strings.o strings.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o discovery.o discovery.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o iscsiadm.o iscsiadm.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE util.o io.o auth.o login.o log.o md5.o sha1.o iscsi_sysfs.o idbm.o ../utils/fwparam_ibft/fw_entry.o ../utils/ fwparam_ibft/fwparam_ibft.o ../utils/fwparam_ibft/fwparam_ppc.o ../ utils/fwparam_ibft/prom_lex.o ../utils/fwparam_ibft/prom_parse.tab.o strings.o discovery.o iscsiadm.o -o iscsiadm cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o iscsistart.o iscsistart.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -c -o statics.o statics.c cc -O2 -g -Wall -Wstrict-prototypes -I../include -DLinux - DNETLINK_ISCSI=8 -D_GNU_SOURCE -static netlink.o util.o io.o auth.o login.o log.o md5.o sha1.o iscsi_sysfs.o idbm.o initiator.o scsi.o actor.o mgmt_ipc.o isns.o transport.o ../utils/fwparam_ibft
Re: Build problems with 869.2
On Aug 26, 6:23 am, Erez Zilber [EMAIL PROTECTED] wrote: On Tue, Aug 26, 2008 at 11:20 AM, v42bis [EMAIL PROTECTED] wrote: Just saw the thread about rhel5 symbol problems, which seems to be my issue. Tried to apply the patch from Erez to 869.2 source, but it failed :( Try the attached patch. Erez Add-compat-patch-for-RHEL-5.2.patch Thanks, Erez. That patch worked on 869.2. I am getting some warnings on boot/module load: Starting iSCSI initiator service: iscsidLoading iSCSI transport class v2.0-869. iscsi: registered transport (tcp) ib_iser: disagrees about version of symbol iscsi_conn_setup ib_iser: Unknown symbol iscsi_conn_setup ib_iser: disagrees about version of symbol iscsi_verify_itt ib_iser: Unknown symbol iscsi_verify_itt ib_iser: disagrees about version of symbol iscsi_session_recovery_timedout ib_iser: Unknown symbol iscsi_session_recovery_timedout ib_iser: disagrees about version of symbol iscsi_conn_bind ib_iser: Unknown symbol iscsi_conn_bind ib_iser: disagrees about version of symbol class_to_transport_session ib_iser: Unknown symbol class_to_transport_session ib_iser: disagrees about version of symbol iscsi_conn_failure ib_iser: Unknown symbol iscsi_conn_failure ib_iser: disagrees about version of symbol iscsi_complete_pdu ib_iser: Unknown symbol iscsi_complete_pdu ib_iser: disagrees about version of symbol iscsi_register_transport ib_iser: Unknown symbol iscsi_register_transport ib_iser: disagrees about version of symbol iscsi_set_param ib_iser: Unknown symbol iscsi_set_param ib_iser: disagrees about version of symbol iscsi_conn_get_param ib_iser: Unknown symbol iscsi_conn_get_param ib_iser: disagrees about version of symbol iscsi_conn_teardown ib_iser: Unknown symbol iscsi_conn_teardown ib_iser: disagrees about version of symbol iscsi_session_get_param ib_iser: Unknown symbol iscsi_session_get_param ib_iser: disagrees about version of symbol iscsi_conn_send_pdu ib_iser: Unknown symbol iscsi_conn_send_pdu ib_iser: disagrees about version of symbol iscsi_conn_start ib_iser: Unknown symbol iscsi_conn_start ib_iser: disagrees about version of symbol iscsi_prep_unsolicit_data_pdu ib_iser: Unknown symbol iscsi_prep_unsolicit_data_pdu ib_iser: disagrees about version of symbol iscsi_free_mgmt_task ib_iser: Unknown symbol iscsi_free_mgmt_task ib_iser: Unknown symbol iscsi_session_setup2 ib_iser: disagrees about version of symbol iscsi_session_teardown ib_iser: Unknown symbol iscsi_session_teardown ib_iser: disagrees about version of symbol iscsi_unregister_transport ib_iser: Unknown symbol iscsi_unregister_transport ib_iser: disagrees about version of symbol iscsi_conn_stop ib_iser: Unknown symbol iscsi_conn_stop . Setting up iSCSI targets:iscsiadm: No records found! Any idea what might cause this? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Configuration question
On Aug 20, 1:39 am, Mike Christie [EMAIL PROTECTED] wrote: v42bis wrote: Thank for the reply, Mike. No problem. The iscsi connections failed about 1m13s after my iscsi target went down (timestamps that follow are synced from same ntp master, however clock skew may account for a few seconds difference [1m45sec seems very conspicuous - a multiplier of default 15sec timers?]). The target went down at Aug 19 13:33:33. Actually this looks like a different problem. What version of open-iscsi are you using? Do a iscsiadm -P 3. The top part should dump the iscsiadm version. `iscsiadm -P 3` just spits out the usage/help information - no version. I know it is version open-iscsi-2.0-865.15, though. Aug 19 13:36:42 ak1-vz2 kernel: iscsi: scsi conn_destroy(): host_busy 0 host_failed 0 This means that userspace decided to kill the iscsi session/connection which means that we ignore the recovery/replacement timeout and just kill everything which forces IO errors. We only did this for fatal errors, but we should not do that anymore. What userspace process would have done that? The above did not affect normal operation of my open-iscsi initiators. That is weirder. In this setup do you have multiple sessions/connections? When you checked the machine were all the session/connections running? There should have been two sessions that were destroyed. Only one session per connection. One connection to each iscsi target. All of the filesystems and iscsi connections seemed fine, as far as I could tell. In older open-iscsi userspace tools there were certain errors the target could send us and iscsid would consider it a fatal error and it would kill the sessions like above. For example if a target was shutting down it could tell us that it was not coming back, so we would kill the session. There was also a case where iscsid got confused and thought it was a fatal error and would kill the session. We now just retry forever or until the user kills the session manually to avoid problems like this. To confirm: open-iscsi version 2.0-869.2 and above will never kill iscsi sessions unless the user explicitly tells iscsid to logout/kill the session? I want to make sure my open-iscsi initiators never return errors until replacement_timeout is reached. I'd rather have any processes accessing filesystems on iscsi hang forever than have the connections lost and journals aborted. Looking at the code, there is no problem with setting such a high replacement_timeout? Please tell me you were using a older version than open-iscsi-2.0-869.2 :) If you were using open-iscsi-2.0-869.2 then we have a different problem :( I am definitely running 2.0-865.15. I will upgrade to 2.0-869.2. It would be *very* convenient if the Changelog would include changes in every version and not just the current release. :) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
