We have an occasional problem where one LUN of a target (LUN-0) does not appear in a connection started by iscsistart. This is in an iscsi- root scenario where iscsistart is called from within the initrd ramdisk image. I don't why this happens, but I can detect when it does. However, I don't know how to stop the connection and try again. If I just re-run iscsistart, it complains that there is already a connection. I tried just pulling out all the iscsi related modules and re-loading them, but they are "in use".
Is there some way to stop the connection so that I can reinvoke iscsistart and see all of my LUNs? Some trick with /proc or /sys? I don't have much to work with in this early user space environment, and I don't want it to grow too big. Any thoughts? Thanks, Craig --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
