[libvirt] [PATCH 3/3] virISCSIGetSession: Don't leak memory

John Ferlan jferlan at redhat.com
Thu Apr 6 11:05:01 UTC 2017


>>
>> So what's the output from a "iscsiadm --mode session" on Michal's
>> machine?  And then if there is a duplicate - how did it happen?
> 
> # iscsiadm --mode session
> tcp: [31] 10.34.126.253:3260,1 iqn.2017-03.com.mprivozn:server
> tcp: [32] virt-iscsi-server.usersys.redhat.com:3260,1 iqn.2017-03.com.mprivozn:server
> 
> where the URL from "line" [32] resolves to the IP from "line" [31].
> 

Ah - I see - so some sort of intentional (mis)configuration to avoid the
text comparison because the IP address isn't being resolved... One would
think that would/could be an iscsi(d) type bug.

Does 'iscsiadm -m session -P 3' consider them different?

Can you login to each?

iscsiadm -m node -T $IQN -p $PORTAL --login

where $PORTAL would be in your case 10.34.126.253:3260 or
virt-iscsi-server.usersys.redhat.com:3260.

What about:

iscsiadm -m discovery -t sendtargets -p $PORTAL -P1

or

Wonder how other tools react... "lsscsi -t -g" or "iscsi-ls ...". Do
they see "two" devices which in the end are the same thing?  That's kind
of (well) scary.


John





More information about the libvir-list mailing list