Re: Can't discover more than 1 iSER device

2016-07-28 Thread darlingm
Just noticied on my other post the open-iscsi I'm running is from 2012.  Is 
the latest open-iscsi release really from 2012?

Are there plans to tag another release, or is it just planned to continue 
git comits without tagging releases?

Maybe the iSER bug I ran into was fixed a long time ago.

On Thursday, July 28, 2016 at 5:45:21 AM UTC-4, james harvey wrote:
>
> Sorry for cross-posting to github, just saw several messages saying to use 
> the mailing list instead.
>
> I made a similar bug report to the linux-rdma mailing list about a year 
> ago, and never followed up here.  I got a response that this is an 
> open-iscsi issue not a kernel issue.  (See 
> http://www.spinics.net/lists/linux-rdma/msg27533.html)
>
> Below is the same bug report, updated now that it's a year later.
>
>
> Two up to date arch systems.  Kernel 4.6.4 (Arch -1).
>
> 2 Mellanox MT25418 [ConnectX VPI PCIe 2.0 2.5GT/s - IB DDR / 10GigE]
> (rev a0) running mlx4_core driver v2.2-1 (Feb, 2014.)  Both on most
> recent firmware for PSID MT_04A0110002, FW Version 2.9.1000.  Systems
> directly connected, no switches.  InfiniBand otherwise works great,
> through VERY extensive testing.
>
> Running OpenFabrics most recent releases of everything (release
> versions, not git versions.)
>
> Open-iscsi 2.0_873-7.
>
> targetcli-fb 2.1.fb43-1, python-rtslib-fb 2.1.fb60-1, and
> python-configshell-fb 1.1.fb20-1.
>
>
> I can't discover more than 1 iSER device working at a time.  Using
> IPoIB lets me discover as many as I want.
>
> At the very end is a workaround - not a fix.
>
>
> I start with 3 disks working through iSCSI over IPoIB, with
> targetcli's (-fb version) ls looking like:
>
> o- / . 
> [...]
>   o- backstores .. 
> [...]
>   | o- block .. [Storage 
> Objects: 3]
>   | | o- sda4  [/dev/sda4 (4.4TiB) write-thru 
> activated]
>   | | o- sdb4  [/dev/sdb4 (4.4TiB) write-thru 
> activated]
>   | | o- sdc4  [/dev/sdc4 (4.4TiB) write-thru 
> activated]
>   | o- fileio . [Storage 
> Objects: 0]
>   | o- pscsi .. [Storage 
> Objects: 0]
>   | o- ramdisk  [Storage 
> Objects: 0]
>   | o- user ... [Storage 
> Objects: 0]
>   o- iscsi  
> [Targets: 3]
>   | o- iqn.2003-01.org.linux-iscsi.terra.x8664:sn.2549ae938766 ... 
> [TPGs: 1]
>   | | o- tpg1 ... [no-gen-acls, 
> no-auth]
>   | |   o- acls .. 
> [ACLs: 1]
>   | |   | o- iqn.2005-03.org.open-iscsi:c04e8f17af18 .. [Mapped 
> LUNs: 1]
>   | |   |   o- mapped_lun0 .. [lun0 block/sda4 
> (rw)]
>   | |   o- luns .. 
> [LUNs: 1]
>   | |   | o- lun0 . [block/sda4 
> (/dev/sda4)]
>   | |   o- portals  
> [Portals: 1]
>   | | o- 0.0.0.0:3260 
> . [OK]
>   | o- iqn.2003-01.org.linux-iscsi.terra.x8664:sn.8518b92b052d ... 
> [TPGs: 1]
>   | | o- tpg1 ... [no-gen-acls, 
> no-auth]
>   | |   o- acls .. 
> [ACLs: 1]
>   | |   | o- iqn.2005-03.org.open-iscsi:c04e8f17af18 .. [Mapped 
> LUNs: 1]
>   | |   |   o- mapped_lun0 .. [lun0 block/sdb4 
> (rw)]
>   | |   o- luns .. 
> [LUNs: 1]
>   | |   | o- lun0 . [block/sdb4 
> (/dev/sdb4)]
>   | |   o- portals  
> [Portals: 1]
>   | | o- 0.0.0.0:3260 
> . [OK]
>   | o- iqn.2003-01.org.linux-iscsi.terra.x8664:sn.d4603198ba50 ... 
> [TPGs: 1]
>   |   o- tpg1 ... [no-gen-acls, 
> no-auth]
>   | o- acls .. 
> [ACLs: 1]
>   | | o- iqn.2005-03.org.open-iscsi:c04e8f17af18 .. [Mapped 
> LUNs: 1]
>   | |   o- mapped_lun0 .. [lun0 block/sdc4 
> (rw)]
>   | o- luns .. 
> [LUNs: 1]
>   | | o- lun0 . [block/sdc4 
> (/dev/sdc4)]
>   | o- portals  
> [Portals: 1]
>   |   o- 0.0.0.0:3260 
> . [OK]
>   o- loopback 

Re: /etc .startup = automatic settings don't appear to make iscsid automatically log in, what do they do?

2016-07-28 Thread darlingm
Arch.  Kernel 4.6.4.  open-iscsi 2.0_873.

Oh boy, that might be my problem right there for one or both of my posts.  
Is the latest open-iscsi release really from 2012?

Are there plans to tag another release, or is it just planned to continue 
git comits without tagging releases?

On Thursday, July 28, 2016 at 5:50:54 AM UTC-4, james harvey wrote:
>
> Am I doing something wrong to get iscsid to automatically login to certain 
> nodes, or am I not understanding what the .startup = automatic settings do?
>
> I was about to post about having trouble getting automatic login to work, 
> but on the mailing list archives, I see some systemd services that run 
> logins.
>
> Now I'm confused.
>
> I spammed automatic everywhere, thinking that would make iscsid 
> automatically log into them.
>
> iscsid.conf:node.startup = automatic
> nodes/iqn.XXX/IP,port,1/defualt:node.startup = automatic
> nodes/iqn.XXX/IP,port,1/defualt:node.conn[0].startup = automatic
> send_targets/IP,port/st_config:discovery.startup = automatic
>
> Should these be left as manual, and run a systemd service that uses 
> iscsiadm to login instead?
>

-- 
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 open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at https://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.