>Then there's MC/S. Mutlitple Connections in the same Session. Which I
don't believe is supported.
I am talking about this scenario. Want to know if there any design
considerations inhibiting this support.
-Original Message-
From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED
>Andrew Morton wrote:
> > + *
> > + * Written by: Karen Xie ([EMAIL PROTECTED]) */
> > +
> > +#include "cxgb3i.h"
> > +
> > +#define DRV_MODULE_NAME "cxgb3i"
> > +#define DRV_MODULE_VERSION "1.0.0"
>I'd suggest that the version number just be removed. It becomes
meaningless (and of
> David Miller wrote:
> > Andrew Morton wrote:
> >I'd suggest that the version number just be removed. It becomes
> meaningless (and often misleading) once a driver is in the mainline
> kernel. People will >update the driver without changing the version
> number. Code external to the driver
>Look, what you're suggesting is to change existing practice and that
doesn't belong in the discussion of the review of a specific driver.
>If you want to bring that up as a topic and change globally how that is
handled, bring that up as a seperate topic on linux-kernel.
Sounds reasonable.
>Don'
Nandkumar wrote:
> Here is what initiator and taget passes to each other while iscsi
negotiation phase. Assuming CHAP is only enabled on initiator and not on
target.
> 1) Initiator pass "CHAP,NONE" as Authentication parameter.
> 2) Target replies with "NONE".
> 3) Both will settle on "NONE" as Auth
git://git.kernel.org/pub/scm/linux/kernel/git/mnc/open-iscsi.git
Is this still the url to clone the iscsi git tree or do we have a change
here.
I get a connection timed out error always on this. Ideas?
Shyam Iyer
--~--~-~--~~~---~--~~
You received this message
The open-iscsi fwparam tool does not connect through all the initiators
in the initiator structure exported by the iBFT.
I ask this because though the Nic fw can connect twice to the same
target using both the initiators(Dual port card) but then the OS makes
only one connection with the last(I ho
Mike Christie wrote:
> [EMAIL PROTECTED] wrote:
> > The open-iscsi fwparam tool does not connect through all the
> > initiators in the initiator structure exported by the iBFT.
> >
> > I ask this because though the Nic fw can connect twice to the same
> > target using both the initiators(Dual port
Konrad wrote:
>On Wed, Nov 26, 2008 at 06:06:41AM -0600, Mike Christie wrote:
> >
> > [EMAIL PROTECTED] wrote:
> > > The open-iscsi fwparam tool does not connect through all the
> > > initiators in the initiator structure exported by the iBFT.
> > >
> > > I ask this because though the Nic fw can co
> 2) our next problem is multipath. When we configure multipath, over
one NIC with dd we get 90 MBps read, but over 2 NICs just 80 MBps what
is strange. On
> switch and SAN we see that data flow is over both NICs, but dd shows
still 80 MBps.
Are the dd results just one time results or an avera
That is the 20 MB access Lun used for in-band management with the MD3000i
controller. Its not a proper scsi LUN so you might want those error messages.
You could also choose not have it exposed to the host (in your case the debian
server) by editing the Host to virtual disk mappings using eithe
Scott wrote:
> I have a Dell MD3000i connected to a PowerEdge 2950 server running
out-of-box CentOS 5.2 64-bit, unpatched, on an isolated test LAN.
> I also purchased the snapshot premium feature.
> Using the included Modular Disk Storage Manager, I successfully
activated the premium feature, an
If you can view the snapshots from the OS through fdisk -l(which means
they have been mapped to the host properly) then you can as well mount
them to retrieve data.
Is that the question ? Maybe I haven't understood properly.
-Original Message-
From: Scott R. Ehrlich [mailto:sc...@mit.edu
Does anyone know the reason for file attributes of the files created in
/sys/firmware/ibft/<>/files being readonly?
Can't dynamically changing parameters like target ip-addreseses, iqns
and others etc. be configurable through userspace via sysfs?
I think we do have precedence of firmware paramet
Konrad wrote:
>On Mon, Feb 23, 2009 at 06:16:04PM +0530, shyam_i...@dell.com wrote:
>>
>> Does anyone know the reason for file attributes of the files created
>> in /sys/firmware/ibft/<>/files being readonly?
>Yes. The spec does not allow you to write to the iBFT - only read.
Thanks Konrad. I
Michael wrote:
>On Monday 23 February 2009 12:46:04 shyam_i...@dell.com wrote:
>> Does anyone know the reason for file attributes of the files created
>> in /sys/firmware/ibft/<>/files being readonly?
>>
>> Can't dynamically changing parameters like target ip-addreseses, iqns
>> and others etc.
-Original Message-
From: Michael Brown [mailto:mbr...@fensystems.co.uk]
Sent: Tuesday, February 24, 2009 2:13 PM
To: Iyer, Shyam
Cc: open-iscsi@googlegroups.com
Subject: Re: [RFC]-Sysfs attributes of /sys/firmware/ibft files
On Tuesday 24 February 2009 07:57:32 shyam_i...@dell.com wro
Sorry. I clicked on send before the mail completed.
Michael wrote:
>It sounds as though you're expecting that making changes to the iBFT
would cause the iSCSI initiator to change its configuration. I don't
think this is >going to be the case; it definitely won't happen in the
case of gPXE.
Ye
I don't think open-iscsi needs to support that.
You just load the relevant I/O AT modules. This should get automatically
loaded if the system BIOS enables I/O AT (requires chipset support).
Once you have done that the network has a performance boost and you can
do all you want from normal netwo
A double memory free is detected by glibc when iscsistart -b is run by
initrds to connect to an iSCSI target using iBFT info. Issue is easily
reproducible if chap authentication is used.
o...@localhost open-iscsi-2.0-870.3]# ./usr/iscsistart -b
iscsistart: transport class version 2.0-870. iscsid v
Ulrich wrote:
>On 17 Mar 2009 at 22:33, shyam_i...@dell.com wrote:
>> The issue is caused because child is trying to free up the session
and
>> connections that the parent had setup.
>Hi!
>Not knowing the source, I wonder: Parent and child (both processes?)
have their own copy of memory, so ea
Resending because earlier patch had a small typo.
>Ulrich wrote:
>On 17 Mar 2009 at 22:33, shyam_i...@dell.com wrote:
>> The issue is caused because child is trying to free up the session
and
>> connections that the parent had setup.
>Hi!
>Not knowing the source, I wonder: Parent and child
Mike Christie wrote:
> Mike Christie wrote:
>> We should not have to call stop_event_loop if the event_loop is
>> already stopped. What I am wondering is how the event loop is stopped
>> by anyone other than the call to stop_event_loop? It looks like it
>> could happen if there was a signal or
Mike Christie wrote:
>mala...@us.ibm.com wrote:
>> Hi all,
>>
>> I am trying to install RHEL5.3 on an iSCSI disk with two paths.
>> I booted with "mapth" option but the installer picked up only a
single
>> path. Is this the expected behavior when I use "iBFT"?
>>
>
>For this mail ibft bo
mala...@us.ibm.com wrote:
>Mike Christie [micha...@cs.wisc.edu] wrote:
>> If the ibft implementation uses one session, but exports all the
>> targets in the ibft info, then in RHEL 5.3 the installer only picks
up
>> the session used for the ibft boot up, but the initrd root-boot code
>> used af
Mike Christie wrote:
>That is what I said in the mail you replied to more or less. For boot
it is fixed. iscsiadm/iscsistart logs into all the targets found in ibft
whehter
>they were used for the ibft boot or not. For install there is a bug
still, because the isntaller code used the wrong API wh
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Mike Christie
> Sent: Saturday, June 13, 2009 8:30 AM
> To: open-iscsi@googlegroups.com
> Subject: Re: open-iscsi and discover newly created LUN
>
>
> On 06/12/2009 01:16 AM, Th
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Konrad Rzeszutek
> Sent: Monday, June 15, 2009 8:39 PM
> To: open-iscsi@googlegroups.com
> Subject: Re: open-iscsi and discover newly created LUN
>
>
> > >
> > > On RHEL 5.3 and n
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Mike Christie
> Sent: Monday, June 15, 2009 9:15 PM
> To: open-iscsi@googlegroups.com
> Subject: Re: open-iscsi and discover newly created LUN
>
>
> On 06/15/2009 12:41 AM, shyam_
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Mike Christie
> Sent: Thursday, June 11, 2009 11:11 PM
> To: open-iscsi
> Subject: RFC: do we need a new list for kernel patches
>
>
> Hey,
>
> It seems like we have a lot of mem
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of shyam_i...@dell.com
> Sent: Thursday, June 11, 2009 11:39 PM
> To: open-iscsi@googlegroups.com
> Subject: RE: do we need a new list for kernel patches
>
>
> > -Original Messag
Establish a connection to an MD3000i (use CHAP and Rev. CHAP)
- Disconnect the iSCSI session
iscsiadm -m node -p -T -u
- Reconnect the iSCSI session
iscsiadm -m node -p -T -l
<-Fails because iscsid gets killed
Signed-off-by: Thomas C
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Konrad Rzeszutek
> Sent: Thursday, June 25, 2009 8:10 PM
> To: open-iscsi@googlegroups.com
> Subject: Re: do we need a new list for kernel patches
>
>
> > >>> see what features ar
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Mike Christie
> Sent: Thursday, June 25, 2009 8:57 PM
> To: open-iscsi@googlegroups.com
> Cc: Chenault, Thomas; thomas.weyerg...@net-m.de
> Subject: Re: [PATCH] fix conn context da
I see that a couple of ways are being used to get the ibft data from
memory -
1) iscsiadm -m fw
Which relies on /sys/firmware/ibft/* files to create the record
and thus login.
2) fwparam_ibft -b
This relies on opening /dev/mem and getting all the parameters
and thus login
I am s
> > QUESTION:
> > =
> > Since I am creating two iscsi sessions (one out eth2 and eth3), I'm
> > wondering how routing plays into sessions. Since iscsiadm is given
> > the hwaddress, does iscsid need to care much about routing? In
other
> > words, let's say that, for whatever reason, my
Donald,
Mike is talking about this fix from Dell that we submitted
http://groups.google.com/group/open-iscsi/browse_thread/thread/436ff294f
49d06df.
Thanks,
Shyam
From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
On Behalf Of Donald Williams
Sent: We
Signed-off-by: Shyam Iyer
Adds support to register for scn events with iSNS server.
--~--~-~--~~~---~--~~
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@googlegroups.co
1) With the first patch we should be able to do the following -
#iscsiadm -m discovery -t isns -l
And all the target portals will get logged in.
It also adds iface support to be able to login through multiple
initiator portals.
The iSNS server needs to be configured in iscsid.conf.
TODO: dhcp b
Signed-off-by: Shyam Iyer
Adds support to autologin to isns discovered target portals.
--~--~-~--~~~---~--~~
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@googlegroups
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Mike Christie
> Sent: Monday, August 03, 2009 10:46 PM
> To: open-iscsi@googlegroups.com
> Subject: Re: [PATCH 0/2] iSNS enhancements
>
>
> On 07/30/2009 10:37 AM, shyam_i...@dell
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Jonas
> Sent: Tuesday, September 22, 2009 5:21 AM
> To: open-iscsi
> Subject: iscsid crashes on disconnect (using Dell MD3000i)
>
>
> Hi!
>
> I'm having a bit of an odd issue -
1. Install Red Hat Enterprise Linux 5.4 snapshot 5 i386 on a server with
Broadcom iSCSI offload capable LOMs.
*** Note: 32-bit OS believed necessary ***
2. Discover an iSCSI target on the local IP network using the offload
interface.
iscsiadm -m discovery -p -t st -I bnx2i.
3. Configure t
>From the spec:
"
CHAP secrets MUST be an integral number of bytes (octets). A
compliant implementation SHOULD NOT continue with the login step in
which it should send a CHAP response (CHAP_R, Section 11.1.4
Challenge Handshake Authentication Protocol (CHAP)) unless it can
verify tha
> -Original Message-
> From: devel-boun...@open-fcoe.org [mailto:devel-boun...@open-fcoe.org]
> On Behalf Of Eric Multanen
> Sent: Tuesday, December 15, 2009 10:31 AM
> To: de...@open-fcoe.org
> Subject: [Open-FCoE] [fcoemon PATCH v2 00/11] rfcoemon restructuring
>
> v2 - restore code in t
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Ulrich Windl
> Sent: Wednesday, December 16, 2009 1:08 PM
> To: open-iscsi@googlegroups.com
> Subject: Re: minimum password length check
>
> On 15 Dec 2009 at 22:47, shyam_i...@dell
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Ulrich Windl
> Sent: Thursday, December 17, 2009 1:27 PM
> To: open-iscsi@googlegroups.com
> Subject: RE: minimum password length check
>
> On 17 Dec 2009 at 0:55, shyam_i...@dell.c
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Ulrich Windl
> Sent: Wednesday, December 16, 2009 1:08 PM
> To: open-iscsi@googlegroups.com
> Subject: Re: minimum password length check
>
> On 15 Dec 2009 at 22:47, shyam_i...@de
> -Original Message-
> From: devel-boun...@open-fcoe.org [mailto:devel-boun...@open-fcoe.org]
> On Behalf Of Mike Christie
> Sent: Thursday, December 17, 2009 9:05 AM
> To: open-iscsi@googlegroups.com
> Cc: eric.w.multa...@intel.com; de...@open-fcoe.org
> Subject: Re: [Open-FCoE] [fcoemon
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Ulrich Windl
> Sent: Friday, December 18, 2009 3:24 PM
> To: open-iscsi@googlegroups.com
> Subject: RE: minimum password length check
>
> On 18 Dec 2009 at 1:13, shyam_i...@dell.com
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Alex Zeffertt
> Sent: Tuesday, December 22, 2009 4:32 PM
> To: open-iscsi@googlegroups.com
> Subject: Re: [PATCH] support multidisk iBFTs
>
> Mike Christie wrote:
> > Alex Zeffertt
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Mike Christie
> Sent: Friday, January 15, 2010 2:03 PM
> To: open-iscsi
> Subject: iscsi offload boot support
>
> Hey,
>
> In the open-iscsi git tree there is now offload boot su
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On
> Behalf Of Benjamin Li
> Sent: Wednesday, November 03, 2010 4:05 PM
> To: Mike Christie
> Cc: open-iscsi@googlegroups.com; Anish Bhatt; Eddie Wai
> Subject: Re: case sensitivity of hardware
> -Original Message-
> From: Ben Greear [mailto:gree...@candelatech.com]
> Sent: Wednesday, November 03, 2010 11:56 PM
> To: open-iscsi@googlegroups.com
> Cc: Iyer, Shyam; micha...@cs.wisc.edu; an...@chelsio.com; w...@broadcom.com
> Subject: Re: case sensitivity of hardware addresses & vl
(Ton I am copying the open-iscsi mailing list as some of the Broadcom iSCSI
offload developers hang here as well and I believe I saw a fix for this issue )
Hi,
>
> I'm trying to get offload iscsi (rhel 5.5) to work on a PowerEdge M610
> and bnx2i.
> The thing is that I get it to work through the
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
> On Behalf Of Hannes Reinecke
> Sent: Monday, December 20, 2010 6:47 AM
> To: open-iscsi@googlegroups.com
> Cc: Rustad, Mark D
> Subject: Re: DCB support for iSCSI
>
> On 12/17/2010 06:55 PM, Rus
> -Original Message-
> From: Mike Christie [mailto:micha...@cs.wisc.edu]
> Sent: Monday, January 03, 2011 3:39 PM
> To: open-iscsi@googlegroups.com
> Cc: Iyer, Shyam; mark.d.rus...@intel.com
> Subject: Re: DCB support for iSCSI
>
> On 12/22/2010 11:22 PM, shyam_i...@dell.com wrote:
> >>
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Pasi Kärkkäinen
> Sent: Saturday, March 19, 2011 10:16 AM
> To: rahul gupta
> Cc: open-iscsi@googlegroups.com
> Subject: Re: multiple initiator instances on same machine.
>
> On S
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Mike Christie
> ccing Broadcom devs, Some questions for you guys below
>
>
> On 04/02/2011 01:34 PM, vikas.chaudh...@qlogic.com wrote:
> > From: Vikas Chaudhary
> >
> > To su
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Pasi Kärkkäinen
> Sent: Tuesday, April 26, 2011 7:20 AM
> To: open-iscsi@googlegroups.com
> Cc: james.bottom...@suse.de; Mike Christie; linux-s...@vger.kernel.org;
> Vikas Chaudhar
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Joe Hoot
> Sent: Thursday, April 28, 2011 8:08 PM
> To: open-iscsi@googlegroups.com
> Subject: Re: determining window size
>
> Thanks for the quick response (as always) Mike.
>
>
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Joe Hoot
> Sent: Friday, April 29, 2011 11:47 AM
> To: open-iscsi@googlegroups.com
> Subject: Re: determining window size
>
> We have a few environments that we're testing this wi
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Rustad, Mark D
> Sent: Friday, February 24, 2012 8:30 PM
> To:
> Subject: Re: [PATCH] iscsid: Add support for net_prio cgroups
>
> I have sent this patch to improve the behavior
Just a thought.. if this was being overhauled considering a REST-like interface
to manage iSCSI would go a long way in solving manageability issues.
--
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@g
> -Original Message-
> From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com]
> On Behalf Of Mike Christie
> Sent: Wednesday, May 29, 2013 1:30 PM
> To: open-iscsi@googlegroups.com
> Cc: Eddie Wai; vikas.chaudh...@qlogic.com; lalit.chandiv...@qlogic.com;
> ravi.an...@qlogi
65 matches
Mail list logo
