RE: EADDRINUSE setting up iSCSI portal on aarch64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've started running into this too - I think it happened when I switched to testing with RHEL 7.1.
The auto create of a portal at 0.0.0.0 is really killing me.

I create Target1 and it auto creates the 0.0.0.0:3260 portal.  I want my portal at 192.168.1.1:3260
but I can't create it because the auto portal is already using that port.

I can delete the portal at 0.0.0.0:3260, then create mine at 192.168.1.1:3260.  But then when
I try to create Target2 it fails because it's trying to create a portal at 0.0.0.0:3260 for that one
and it's getting EADDRINUSE.

Is there a way to turn off this automatic creation of portals in targetcli?

Chris




> -----Original Message-----
> From: target-devel-owner@xxxxxxxxxxxxxxx [mailto:target-devel-
> owner@xxxxxxxxxxxxxxx] On Behalf Of Andy Grover
> Sent: Tuesday, December 09, 2014 9:26 PM
> To: Noah Watkins; target-devel@xxxxxxxxxxxxxxx
> Subject: Re: EADDRINUSE setting up iSCSI portal on aarch64
> 
> On 12/09/2014 04:22 PM, Noah Watkins wrote:
> > Hi, I’m trying to debug a problem setting up an iSCSI target portal on
> > aarch64. I’m seeing -EADDRINUSE when I create the portal:
> 
> Hmm interesting, haven't tried on aarch64 but can't think of why it'd matter.
> 
> > />
> > iscsi/iqn.2003-01.org.linux-iscsi.node-1.aarch64:sn.e2e690850a04/tpg1/
> > portals create 10.10.1.2 Using default IP port 3260 Could not create
> > NetworkPortal in configFS
> >
> > and dmesg shows:
> >
> > [ 5314.246743] kernel_bind() failed: -98
> >
> > The NIC has two ports, and I’ve tried both. I don’t have any reason to
> > think that there is any user of the port I’m trying to bind to.
> 
> Does
> 
> sudo netstat -anp|grep "LISTEN "
> 
> show anything for that port?
> 
> > System:
> >
> > Linux node-1.nwatkins-qv1006.emulab-net.utah.cloudlab.us
> > 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 19:05:44 UTC 2014 aarch64
> > aarch64 aarch64 GNU/Linux
> >
> > [   21.142153] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1
> > (Feb 2014) 01:00.0 Ethernet controller: Mellanox Technologies MT27520
> > Family [ConnectX-3 Pro]
> >
> > Software:
> >
> > The *-fb version of targetcli
> 
> Which version of targetcli-fb and rtslib-fb?
> 
> Recent *-fb versions get fancy and auto-create a portal for new targets
> listening on all IPs (0.0.0.0). If that turns out to be the issue then removing
> the auto-created one will allow you to create a new one listening on a
> specific IP.
> 
> Regards -- Andy
> --
> To unsubscribe from this list: send the line "unsubscribe target-devel" in the
> body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at
> http://vger.kernel.org/majordomo-info.html
��.n��������+%������w��{.n����j�����{ay�ʇڙ���f���h������_�(�階�ݢj"��������G����?���&��





[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux