[PATCH] IB/iSER: Release connection resources when receiving a RDMA_CM_EVENT_DEVICE_REMOVAL event

When a RDMA_CM_EVENT_DEVICE_REMOVAL event is raised, iSER should release the connection resources except for the rdma cm id (which will be released by the cma itself). This behavior is necessary if IB modules are unloaded while open-iscsi is still running. Currently, iSER just initiates a BUG()

Re: Removing the transport module before iscsid

Mike Christie wrote: Erez Zilber wrote: Mike, We're trying to solve a problem, but first the motivation: a user may want to stop the InfiniBand modules (/etc/init.d/openibd stop) while open-iscsi is running. In order to do that, we must remove ib_iser. Now, the question: is it ok to

[PATCH] Use correct debug option '-d' for iscsiadm

Hi Mike, the debug option for iscsiadm is '-d', not '-g'. Cheers, Hannes -- Dr. Hannes Reinecke zSeries Storage [EMAIL PROTECTED] +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg)

[PATCH] Fixup IPC leak in iscsid

Hi Mike, iscsid is leaking IPC identifiers when the startup fails. Please apply. Cheers, Hannes -- Dr. Hannes Reinecke zSeries Storage [EMAIL PROTECTED] +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB

Moutning Sessions

I have installed the open-iscsi and I can see my sessions just fine. I can log into the sessions just fine. When I run iscsiadm -m session -P 1 i get: Target: iqn.1992-08.com.netapp:sn.101170410 Current Portal: 192.168.27.10:3260,1001 Persistent Portal: 192.168.27.10:3260,1001

cannot run the iscsistart CLI

Hello all, I am trying to setup an iscsi root disk; googled instructions that suggests to make changes to init in the initrd; before doing so I wanted to test the iscsistart CLI. I am able to connect to my target when I start the iscsi daemon via the: service iscsi start. However, I am unable

Re: Moutning Sessions

On Tue, Apr 8, 2008 at 11:51 AM, fischerman [EMAIL PROTECTED] wrote: I have installed the open-iscsi and I can see my sessions just fine. I can log into the sessions just fine. I am wondering how to mount this device to be used? I have read the read-me until I was blue in the face and

Re: Moutning Sessions

On Tue, Apr 8, 2008 at 12:22 PM, fischerman [EMAIL PROTECTED] wrote: What I am seeing in dmesg is this Hm, how are your volumes configured in the iscsi enclosure? Can you check /var/log/kern.log (or whatever) to verify whether all of those messages are coming from a single time logging into

Re: Understanding effect of read-ahead on open-iscsi block device

On Tue, Apr 08, 2008 at 09:45:06AM -0400, Konrad Rzeszutek wrote: What is the MTU set on your NICs? If it is 1500 (the default) a 4KB transfer will have to be divided in four TCP packets and re-assembled on the target side. This increases the amount of work that the TCP stack

Re: Removing the transport module before iscsid

Erez Zilber wrote: Mike Christie wrote: Erez Zilber wrote: Mike, We're trying to solve a problem, but first the motivation: a user may want to stop the InfiniBand modules (/etc/init.d/openibd stop) while open-iscsi is running. In order to do that, we must remove ib_iser. Now, the

Re: [PATCH 0/4] fixes on iscsi_discovery

Doron Shoham wrote: The following patches contain several bug fixes and add-ons to the iscsi_discovery script. Thanks for the patches. Merged them all, so they will be in the next rc. You should do a git pull or rebase your tree before sending patches, so you know you are diffing against

Re: [PATCH ] Add -f flag to iscsiadm

Doron Shoham wrote: Add -f flag (force) to iscsiadm when changing node parameters that are defined as ATTR_DEFERRED. When using this flag, changing of ATTR_DEFERRED parameter while in active session can take place. The change itself will take effect only in the next session. A warning

Re: Moutning Sessions

fischerman wrote: I have installed the open-iscsi and I can see my sessions just fine. I can log into the sessions just fine. When I run iscsiadm -m session -P 1 i get: You need to run iscsiadm -m session -P 3 to see the disks that were found through each session. Like others have