Re: bind_src_by_address() is disabled?

be so useful if you have multiple IPs on the same interface. Thanks, Ben > > SO_BINDTODEVICE is not related to bind() (was not sure about your comment > about avoiding bind when using that sockopt). It tells the kernel to ignore > the normal > routing tables and to just use the i

Re: bind_src_by_address() is disabled?

On 01/12/2015 11:48 AM, Mike Christie wrote: > On 1/12/15, 1:29 PM, Ben Greear wrote: >> On 01/12/2015 11:22 AM, Mike Christie wrote: >>> On 1/9/15, 8:28 PM, Thomas Dwyer III wrote: >>>> Hi folks, >>>> >>>> I spent some time browsing through t

Re: bind_src_by_address() is disabled?

; device. Could use mac-vlans though... Thanks, Ben > > For the ip binding stuff, did you already try uncommenting/ifdeffing the > bind by ip related code? I think there is other related code that has to > be updated. I will look at it when I get some time, but that is not > goi

iscsi error "host not found" on Fedora 21 systems

t find disk, try: 4 Will sleep and try again in 1 second. FAILED Couldn't find disk in /dev/disk/by-path listing: we will try manu total 0 lrwxrwxrwx 1 root root 9 Aug 11 09:30 pci-:00:14.0-usb-0:5:1.0-scsi-0:0:0:0 -> ../../sr0 Thanks, Ben -- Ben Greear Candela Technologies Inc h

How to match /dev/sdaX to a particular session?

When I create a session to a target, a /dev/sdX shows up. Is there any way to know which /dev/sdX a particular target is associated with? Fdisk will show me a 'Disk identifier', maybe that could be set in iscsi somehow? --~--~-~--~~~---~--~~ You received this mes

Re: How to match /dev/sdaX to a particular session?

Tomasz Chmielewski wrote: > Ben Greear schrieb: >> When I create a session to a target, a /dev/sdX shows up. Is there >> any way to know which /dev/sdX >> a particular target is associated with? >> >> Fdisk will show me a 'Disk identifier', maybe that

How to remove all iscsi configuration.

, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com --~--~-~--~~~---~--~~ 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@googlegro

Re: How to remove all iscsi configuration.

aybe just script it to look at the process listing and don't call iscsiadm if no daemons are running? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to th

Possible bug, not sure if it's iscsi or not.

2.6.29-rc7 (plus my hacks, but no hacks anywhere near iscsi). Aside from that, seems to be working marvelously, binding to local addresses as I wish. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com --~--~-~--~~~---~--~~ You received

Crash tgtd and tgtadm with more than 112 volumes.

-test 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 EST 2009 x86_64 x86_64 x86_64 GNU/Linux Let me know if I can provide any additional info. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com --~--~-~--~~~---~--~~ You rec

Re: Crash tgtd and tgtadm with more than 112 volumes.

sourceforge.net. > > The address is s...@vger.kernel.org for a year or so, the > iscsitarget-de...@lists.sourceforge.net is an old address which is not > used any more. > > CC: s...@vger.kernel.org Thanks, I tried to forward it off to stgt, hopefully it will make it.

Re: How to remove all iscsi configuration.

Mike Christie wrote: > Ben Greear wrote: >> george joseph wrote: >>> Hi Ben, >>> >>> Please try the following steps. >>> >>> 1) Log out from all the connected session. >>> >>> 2) Delete the entry using iscsiadm -m di

Re: Workaround for problem with 2.6.31+ and iface binding

.conf.default.rp_filter = 0 We have seen no trouble doing just this, but we have always set the rp_filter to zero because we run send-to-self patches (not directly for iSCSI connections, but for other connections on the same system). Thanks, Ben -- Ben Greear Candela Technologies Inc http

Re: case sensitivity of hardware addresses & vlan configs

cr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- Ben Greear Candela Technologies Inc http://www.candelatech.com -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To

iSCSI failover seems to blow up on 2.6.36.3 kernel.

te=DRIVER_OK sd 11:0:0:3: [sdk] CDB: Read(10): 28 00 00 10 10 08 00 00 08 00 end_request: I/O error, dev sdk, sector 1052680 EXT2-fs (sdk): previous I/O error to superblock detected Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com -- You received this message bec

Re: iSCSI failover seems to blow up on 2.6.36.3 kernel.

On 04/14/2011 04:24 PM, Mike Christie wrote: On 04/14/2011 06:08 PM, Ben Greear wrote: We make a application that calls the iscsi tools to mount and iscsi server. We then generate file-IO against the mounted disks to load-test the iscsi servers... One customer is testing failover in their

Re: iSCSI failover seems to blow up on 2.6.36.3 kernel.

On 04/14/2011 04:24 PM, Mike Christie wrote: On 04/14/2011 06:08 PM, Ben Greear wrote: We make a application that calls the iscsi tools to mount and iscsi server. We then generate file-IO against the mounted disks to load-test the iscsi servers... One customer is testing failover in their

Re: iSCSI failover seems to blow up on 2.6.36.3 kernel.

value, whatever that is..but I'll check. Also, even if we fail the time-out, I assume the system shouldn't hang and panic as it did? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com -- You received this message because you are subscribed to the Google Gro

Re: iSCSI failover seems to blow up on 2.6.36.3 kernel.

On 04/15/2011 12:22 PM, Mike Christie wrote: On 04/15/2011 01:43 PM, Ben Greear wrote: On 04/15/2011 11:37 AM, Mike Christie wrote: On 04/15/2011 01:18 PM, Mike Christie wrote: Ok, yeah we have seen this type of setup before and we should be able to handle this situation as long as the other