All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: open-iscsi@googlegroups.com
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Re: Running open-iscsi with device mapper hangs
Date: Wed, 10 May 2006 12:22:53 -0500	[thread overview]
Message-ID: <4462216D.6070907@cs.wisc.edu> (raw)
In-Reply-To: <44619424.4090208@voltaire.com>

Erez Zilber wrote:
> Mike Christie wrote:
> 
>> Erez Zilber wrote:
>>  
>>
>>> Hi,
>>>
>>> I'm trying to run open-iscsi with the multipath tool. I was able to 
>>> create a scenario in which the initiator machine hangs:
>>>
>>> My initiator runs on a SLES 10 beta 8 machine. The db contains 2 targets:
>>> iscsiadm -m node
>>> [83347a] 192.168.10.106:3260,1 iqn.2005-12.com.voltaire.206000C0FF07C1D1
>>> [030479] 192.168.10.105:3260,1 iqn.2005-12.com.voltaire.206000C0FF07C1D1
>>>
>>>    
>>>
>> are you using the iscsi initiator in a SLES kernel, a mainline kernel or
>> svn or a open-iscsi.org tarball?
>>
>> --
>> dm-devel mailing list
>> dm-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/dm-devel
>>  
>>
> I'm using the initiator that comes with the SLES kernel 
> (2.6.16-rc6-git1-4-smp). We applied 3 patches that are located in 
> https://openib.org/svn/gen2/branches/backport/sles10/:
> iscsi-04-libiscsi.patch
> iscsi-05-convert-tcp.patch
> iscsi-06-transport-ep-cb.patch
> 
> The userspace part is r560.
> 
> Do you prefer that I try to run it with a different open-iscsi version?
> 

Maybe. Do those patches have any of the later fixes PatM found? Look at
r543, 544, 545. Without them you can hit some lockups or oops.

  reply	other threads:[~2006-05-10 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 14:00 Running open-iscsi with device mapper hangs Erez Zilber
2006-05-09 14:14 ` Erez Zilber
2006-05-09 16:55 ` Mike Christie
2006-05-10  7:20   ` Erez Zilber
2006-05-10 17:22     ` Mike Christie [this message]
2006-05-11 14:55       ` Erez Zilber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4462216D.6070907@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=dm-devel@redhat.com \
    --cc=open-iscsi@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.