According to Mike's explanation below it seems that we have a bug in
iSER initiator.
Fixing this bug will require a fix in the stgt iSER code.
The problem is that the initiator send a VA which already includes an
offset for the unsolicited data (which is wrong).
In iser_initiator.c::iser_prepare_w
On Tue, Apr 15, 2008 at 6:02 PM, Mike Christie <[EMAIL PROTECTED]> wrote:
> Are you having troubles building open-iscsi against a plain upstream
> kernel or is is xen kernel based on 2.6.22? And what were the compile
> errors again (did we talk about this before on the list?)?
I was trying to
I am trying to use iscsi target with iser(Infiniband), but when I mount it
became unstable.
I use OFED-1.2.5.1 , scsi-target-utils-0.2-20071227_1 and iscsi-initiator-
utils-2.0-865.
I got logs from iscsi-initiator server like below when it turn into Read-
only file system.
[EMAIL PROTECTED] ~
[EMAIL PROTECTED] wrote on Wed, 16 Apr 2008 11:22 +0300:
> According to Mike's explanation below it seems that we have a bug in
> iSER initiator.
> Fixing this bug will require a fix in the stgt iSER code.
>
> The problem is that the initiator send a VA which already includes an
> offset for the
Erez Zilber wrote:
> When a transport (e.g. iscsi_tcp, ib_iser) is unloaded, a notification
> must be sent to userspace. This will allow the userspace code to release
> all transport related resources.
>
> Signed-off-by: Erez Zilber <[EMAIL PROTECTED]>
Erez, some tiny comments.
> ---
> driver
Mike Christie wrote:
>
> Resend it and then let's send it to James with the other iscsi patches
> for 2.6.26. Thanks.
>
See attached. I did it so we could get this out.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
Bart Van Assche wrote:
> On Tue, Apr 15, 2008 at 6:02 PM, Mike Christie <[EMAIL PROTECTED]> wrote:
>> Are you having troubles building open-iscsi against a plain upstream
>> kernel or is is xen kernel based on 2.6.22? And what were the compile
>> errors again (did we talk about this before on t
노성후 wrote:
>
> Apr 16 20:49:47 OSS1 kernel: iser: iscsi_iser_ib_conn_lookup:no conn exists
> for eph
>
This eph looks weird. Erez, have you seen this before?
>
> Apr 16 20:49:49 OSS1 iscsid: connection2:0 is operational after recovery (2
> attempts)
>
> Apr 16 20:49:53 OS
Hello,
After unmount iSCSI directory, I was trying to stop tgtd services but I
couldn’t.
Looks like, It has network connection between iSCSI target and initiator
still.
How can I get rid of nexus?
[EMAIL PROTECTED] ~]# tgtadm --lld iscsi --op unbind --mode target --tid 2 -I
10.
1.1.0/24
