Mike: I know you've been busy. Any progress on this? Can I help, as I have the same issue?
On Thursday, October 8, 2015 at 2:48:30 PM UTC-7, Mike Christie wrote: > > On 10/08/2015 04:10 PM, Ferenc Wagner wrote: > > Mike Christie <m*@cs.wisc.edu <[email protected]>> writes: > > > >> > On 10/7/15, 1:37 AM, Ferenc Wagner wrote: > >> > > >>> >> In a pristine system (iscsistart only, no targets configured by > >>> >> iscsiadm) I only get two sessions (with short interfaces names). > With > >>> >> an older open-iscsi version I could then add the four needed node, > and > >>> >> after login iscsid took over the two from iscsistart and also > started > >>> >> the two other. Now, that iscsid uses long interface names, it > creates > >>> >> four new sessions and leaves the two from iscsistart unmanaged. > Than > >> > > >> > How do you know they are unmanaged by iscsid? Is the iscsid session > >> > state in the iscsiadm -m session -P 1 info showing: > >> > > >> > Internal iscsid Session State: Unknown > > Maybe I was wrong on this point. After an iscsistart -b in the > > initramfs, but with no ifaces or nodes configured later: > > No problem. I think I fully understand the problem. I am working on a > patch. I messed up the firmware on my card, so I cannot access the boot > setup any more here, but am looking for one in the red hat lab. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
