On 04/09/2012 07:26 AM, Tim Fotherby wrote: > Mike Christie <michaelc@...> writes: > > >> When you did the restart, were there sessions already running? Were you >> also running IO to those sessions? This trace is bad because it >> indicates a double free. I am not sure if it is related to the login >> error above though. Could you do: >> >> echo 1 > /sys/module/libiscsi2/paramters/debug_libiscsi >> echo 1 > /sys/module/libiscsi_tcp/paramters/debug_libiscsi_tcp >> echo 1 > /sys/module/iscsi_tcp/paramters/debug_iscsi_tcp >> >> Then rerun your test? >> > > > I ended up fixing this by removing all the scanned targets and readding them. > Apparently if you change the config to chap from default config after you've > added targets then you have to delete them, re-add them, then restart the > iscsi > service. >
By config you must meant the iscsid.conf settings. iscsid.conf settings are the ones used for the initial discovery session and used to create the per portal iscsi node db. If you have already discovered targets/portals then to update specific portals settings you need to run iscsiadm -m node -T target -p ip -o update -n name-of-setting -v value Or you can set them in iscsid.conf then rerun the discovery command. That will overwrite the current node db with settings based on iscsid.conf values. But even if you did not do this, you should not hit that OOPS/BUG you were hitting 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
