[PATCH 1/2 v2] Release transport entry when the transport is unloaded

When iscsid detects a new transport (e.g. iscsi_tcp, ib_iser), it allocates an entry for it in the transport list. If the transport is unloaded and then reloaded, iscsid would still use the old transport entry. Therefore, the transport entry must be deleted when the transport is unloaded. Signed-

[PATCH 2/2 v2] Notify when transport is unloaded

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]> --- drivers/scsi/scsi_transport_iscsi.c | 30 +

Re: [PATCH 2/2] Notify when transport is unloaded

Mike Christie wrote: > 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. >> > > Thanks for fixing this. > >> + >> struct iscsi_uevent { >>

[PATCH v2] 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. This is necessary when the IB HCA module is unloaded while open-iscsi is still running. Currently, iSER just initiates a BUG() call. Signed-off-by: Erez Zilber <[EMAIL PROTECTED]> --- drivers/infi

[PATCH] Fix indentation

Fix indentation and remove trailing spaces. Signed-off-by: Erez Zilber <[EMAIL PROTECTED]> --- include/iscsi_if.h|2 +- include/iscsi_proto.h |6 ++-- kernel/iscsi_tcp.c|2 +- kernel/libiscsi.c |4 +- kernel/libiscsi.h |

Re: [PATCH] Divide node parameters into 3 categories

Doron Shoham wrote: > Doron Shoham wrote: >> Divide node parameters into 3 categories: >> a. Immutable - properties that are not allowed to change at all. >> b. Immediate - properties that are allowed to change and take effect >> immediately. >> c. Deferred - properties that are allowed to

Re: open-iscsi: Hangs trying to log out of Dell MD3000i

Andrew Moise wrote: > On Thu, Feb 28, 2008 at 10:00 AM, Mike Christie <[EMAIL PROTECTED]> wrote: >> Andrew Moise wrote: >> > Are there any iscsi fixes in 2.6.24, or is it 2.6.25 or nothing? >> >> There are major fixes in 2.6.23 for error handler races and an oops. >> There is one major fix i

iscsi initiator logs?

Hello all, I added edited my /etc/ietd.conf in my target and restarted - now it has a different target-lun exported; I try to stop and start my iscsi- initiator, and it is unable to "read" the NEW target, but seems like there is some log it is reading and persistently wants to load the old targe

Re: iscsi initiator logs?

On Mon, Apr 14, 2008 at 11:35:46AM -0700, v i n c e wrote: > > Hello all, > > I added edited my /etc/ietd.conf in my target and restarted - now it > has a different target-lun exported; I try to stop and start my iscsi- > initiator, and it is unable to "read" the NEW target, but seems like > th

Re: open-iscsi: Hangs trying to log out of Dell MD3000i

On Mon, Apr 14, 2008 at 12:56 PM, Mike Christie <[EMAIL PROTECTED]> wrote: > You mean you want the sync cache fix right? Can I just send a patch for > what went into 2.6.25 since there are several fixes in there you guys > probably want and because the patch will be easier for me to make? :) >

Re: iscsi initiator logs?

v i n c e wrote: > Hello all, > > I added edited my /etc/ietd.conf in my target and restarted - now it > has a different target-lun exported; I try to stop and start my iscsi- > initiator, and it is unable to "read" the NEW target, but seems like > there is some log it is reading and persistentl

[no subject]

Hi, a question. I have a System Storage DS300. I have configured all ok, this work ok, I test all posible fails on the DS300 and all ok. But when I did the test on the server I have a error. When I desconect and conect the cable in the NIC that use to conecting the DS300 I have a error because the

Re: iscsi initiator logs?

thanks a lot both!!! so, just as an FYI, it does not automatically refresh when I re-issue the "iscsiadm -m discovery, etc however when I opt to do with the "-o delete" option, it clears it in persistent cache ... thanks again! - v. On Apr 14, 12:44 pm, Mike Christie <[EMAIL PROTECTED]> w

How to find out initiator connections?

Hello all, Wanted to check if my initiators are connecting to the targets that I have passed on to them (pxebooting to iSCSI root). i noticed the following: 1. cat /proc/net/iet/volume ---> seems to disply what volumes have been "exported" via the /etc/ietd.conf - is this correct? cat /proc

How long is the connection timeout for mounted file system after unbind?

Hello, While I was mounting a target, I unbinded what I was mounting and I found the mounted file system turn into readonly mode about 2 minutes later. [EMAIL PROTECTED] ~]# tgtadm --lld iscsi --op bind --mode target --tid 2 -I 10.1.1.0/24 [EMAIL PROTECTED] 10.1.1.146,3260]# time dd if=/dev/ze

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

Roland Dreier wrote: > thanks, applied... I assume this much simpler patch replaces the earlier > one completely? > Yes (that's why I added "v2" in the subject). Thanks, Erez --~--~-~--~~~---~--~~ You received this message because you are subscribed to the G

can not stop target service properly.

I unmounted target and stoped the iscsi service, But I couln't stop target service. It says still in use. What shall I do to stop the target service properly? [EMAIL PROTECTED] 10.1.1.146,3260]# service iscsi stop Stopping iSCSI initiator service: Logout session [sid: 1, target: iqn.200