Re: udev events for iscsi

On Tuesday, April 21, 2020 at 8:20:23 AM UTC-7, Robert ECEO Townley wrote: > > Wondering myself. > > On Apr 21, 2020, at 2:31 AM, Gionatan Danti > wrote: > >  > [reposting, as the previous one seems to be lost] > > Hi all, > I have a question regarding udev events when using iscsi disks. > > By

Re: udev events for iscsi

On Tuesday, April 21, 2020 at 12:31:24 AM UTC-7, Gionatan Danti wrote: > > [reposting, as the previous one seems to be lost] > > Hi all, > I have a question regarding udev events when using iscsi disks. > > By using "udevadm monitor" I can see that events are generated when I > login and logout

Re: [EXT] [PATCH] open-iscsi:Modify iSCSI shared memory permissions for logs

On Monday, April 20, 2020 at 5:08:36 AM UTC-7, Uli wrote: > > Hi! > > Maybe this could be made a symbolic constant, or even be made > configurable. > The other interesting thing is that there are three seemingly very similar > code fragements to create the shared memory, but each with a

Re: [RFC RESEND PATCH v2] scsi: iscsi: register sysfs for iscsi workqueue

On Monday, May 4, 2020 at 6:24:20 PM UTC-7, Bob Liu wrote: > > Motivation: > This patch enable setting cpu affinity through "cpumask" for iscsi > workqueues > (iscsi_q_xx and iscsi_eh), so as to get performance isolation. > Please summarize for this performance-idiot how setting thee CPU

Re: Concurrent logins to different interfaces of same iscsi target and login timeout

rtal: > 0.0.0.0,0]' err='iscsiadm: Could not login to [iface: default, target: > iqn.2003-01.org.vm-18-220.iqn2, portal: 0.0.0.0,0].\niscsiadm: initiator > reported error (8 - connection timed out)\niscsiadm: Could not log into all > portals' > 2020-08-18 16:20:06,656 INFO(MainTh

Re: [PATCH] TODO: Update to todo list.

tch is to update the todo list. Tasks are suggested by The > Lee-Man > > Signed-off-by: Sonu k > --- > TODO | 13 + > 1 file changed, 13 insertions(+) > > diff --git a/TODO b/TODO > index 7328180..a3d1d91 100644 > --- a/TODO > +++ b/TODO > @@ -37

Re: BUG, lockdep warnings during iSCSI login?

See https://www.spinics.net/lists/kernel/msg3607739.html -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To view this

Re: Slow iSCSI tape performance

I haven't heard about disabling TUR for iSCSI tape improvement. Even if true, I'm not sure how you'd do that. You'd need to modify your target IMHO to always reply "ready" for TUR. But TUR is used to clear some conditions at the target, if present, so not sure about the semantics of ignoring

Re: [PATCH] iscsid: drop uid privileges after locking memory

Hi Anythony: On Thursday, October 22, 2020 at 12:33:08 PM UTC-7 Anthony Iliopoulos wrote: > Move the setuid call after mlockall, since the latter requires elevated > privileges, and will cause iscsid startup to fail when an unprivileged > uid is specified. > I appreciate your patch, but I'm

Re: [PATCH] scsi: iscsi: jump to correct label in an error path

On Sunday, July 26, 2020 at 7:40:48 PM UTC-7, Jing Xiangfeng wrote: > > In current code, it jumps to put_host() when scsi_host_lookup() > failes to get host. Jump to correct label to fix it. > > Signed-off-by: Jing Xiangfeng > --- > drivers/scsi/scsi_transport_iscsi.c | 11 +-- > 1

Re: Todo list for open-iscsi

Heh. I just realized you uncovered one item you could do: update the todo list! But there *are* things in that list that you could help with. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving

Re: Concurrent logins to different interfaces of same iscsi target and login timeout

On Monday, July 27, 2020 at 10:38:05 AM UTC-7, Amit Bawer wrote: > > Thank you for your answers, > > The motivation behind the original question is for reducing the waiting > time for different iscsi connections logins > in case some of the portals are down. > > We have a limitation on our RHEV

Re: Todo list for open-iscsi

On Thursday, July 30, 2020 at 9:58:41 PM UTC-7, sonu kumar wrote: > > Hi All, > > I looked into the TODO list of open-iscsi. It is quite old and written > on July 7th,2011. Do we have any updated version of it? > > I am looking for some low hanging tasks to getting started with > open-iscsi

Re: Concurrent logins to different interfaces of same iscsi target and login timeout

On Thursday, August 6, 2020 at 1:42:35 AM UTC-7, Amit Bawer wrote: > > Another point i'd like to ask about is iSER fallback that we have: > > Currently we check during connection flow if 'iser' is set on > iscsi_default_ifaces in our configuration. > If yes, it is first checked if its working

Re: Concurrent logins to different interfaces of same iscsi target and login timeout

On Sunday, August 9, 2020 at 11:08:50 AM UTC-7, Amit Bawer wrote: > > ... > >> >>> The other option is to use one login-all call without parallelism, but >>> that would have other implications on our system to consider. >>> >> >> Such as? >> > As mentioned above, unless there is a way to

Re: Concurrent logins to different interfaces of same iscsi target and login timeout

On Tuesday, June 30, 2020 at 6:00:03 AM UTC-7, Amit Bawer wrote: > > [Sorry if this message is duplicated, haven't seen it is published in the > group] > > Hi, > > Have couple of question regarding iscsiadm version 6.2.0.878-2: > > 1) Is it safe to have concurrent logins to the same target from

Re: Concurrent logins to different interfaces of same iscsi target and login timeout

On Tuesday, June 30, 2020 at 8:55:13 AM UTC-7, Donald Williams wrote: > > Hello, > > Assuming that devmapper is running and MPIO properly configured you want > to connect to the same volume/target from different interfaces. > > However in your case you aren't specifying the same interface.

Re: Large Immediate and/or Unsolicted Data causes long delays on R2T responses

On Saturday, May 2, 2020 at 11:30:27 AM UTC-7, ajhutc...@gmail.com wrote: > > I am able to create a condition where the open-iscsi initiator fails to > respond to an R2T request if the immediate/unsolicited data support is > large ~128KB. I've seen instances where a delay on an R2T is only a

Re: [EXT] [PATCH] iscsi: Add break to while loop

On Thursday, June 4, 2020 at 7:43:13 AM UTC-7, Uli wrote: > > >>> Wu Bo schrieb am 04.06.2020 um 14:23 in Nachricht > <7784_1591272646_5ED8E4C6_7784_490_1_1591273415-689835-1-git-send-email-wubo40@h > > > awei.com>: > > From: liubo > > > > Fix the potential risk of rc value being washed

Re: [PATCH] iscsi: Add break to while loop

On Thursday, June 4, 2020 at 5:10:49 AM UTC-7, Wu Bo wrote: > > From: liubo > > Fix the potential risk of rc value being washed out by jumping out of the > loop > > Signed-off-by: liubo > Reported-by: Zhiqiang Liu > --- > utils/fwparam_ibft/fwparam_sysfs.c | 5 - > 1 file changed, 4

RFC: what to do about the open-iscsi GPL license vs. the open-ssl BSD license?

th the exception of one distribution that runs nit-picking license checkers, just for fun. :) So this is the official request for comment. Anyone? -- The Lee-man -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this gro

About to tag a new version

Hi All: I',m planning on tagging a new version of open-iscsi, which will be 2.1.2. This would be a bug-fix and cleanup release. Any comments/objections? -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop

Re: About to tag a new version

On Friday, July 24, 2020 at 1:04:43 PM UTC-7, The Lee-Man wrote: > > Hi All: > > I',m planning on tagging a new version of open-iscsi, which will be 2.1.2. > > This would be a bug-fix and cleanup release. > > Any comments/objections? > See https://github.com/open-is

Re: Hi help me please

As Ulrich replied, there's not much we can do with the data you provided. On Wednesday, December 16, 2020 at 12:29:20 PM UTC-8 go xayyasang wrote: > [root@target ~]# iscsiadm -m node -o show > iscsiadm: No records found > > That's normal if you have no records in your database. If you want

Re: Clarification request on open-iscsi affected by uIP vulnerabilities (AMNESIA:33)

Hi Christian: Chris Leech just merged in the mitigations for these CVEs and tagged a new release. These CVEs were all related to the uip package that iscsiuio uses. But in fact iscsiuio only uses uip for network "services", such as DHCP, ARP, etc, and not for normal TCP/IP communications. So

Re: [PATCH] iscsi: Do Not set param when sock is NULL

The patch concept is good. I have a couple of issues though. First, you say you will return EPERM, but you return ENOTCONN. Update the text to match to code? Also, the indentation seems messed up? It's hard to tell using the web interface. If so, please fix. On Monday, November 16, 2020 at

Shouldn't firmware nodes be marked as "onboot", for consistency?

Hi All: I'm working on getting iBFT (firmware) booting working well using open-iscsi with dual paths and DM/multipathing, and I noticed something. When you run "iscsiadm -m discovery -t fw", it creates node database entries for your firmware targets. But it sets "node.startup", and

Re: Submitting a change

On Thursday, June 3, 2021 at 8:01:35 AM UTC-7 Anjali Kulkarni wrote: > *fall. -> foll. > *Gothic -> GitHub > > On May 25, 2021, at 12:26 PM, Anjali Kulkarni > wrote: > > Hi, > I am interested in submitting a change upstream for open-iscsi. How can I > go about doing this? > Also, is the

Re: Antw: [EXT] ISCSI Target and Initiator on same host

I need a bit more information about your setup. What target are you using? I'm guessing LIO, since that's the most common (using targetcli), but there are others, and each one is different with respect to ACLs, using passwords, etc. I use LIO/targetcli, and I usually work with the initiator

Tagged new version of open-iscsi

I have tagged version 2.1.4 of open-iscsi. Follow the link for more info: open-iscsi release here -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and

Re: iface.c:36:21: fatal error: libkmod.h: No such file or directory

open-iscsi relies on libkmod, which didn't exist in 3.10 kernel. You'll have to use an older open-iscsi, such as 2.0.876. On Wednesday, February 17, 2021 at 7:58:35 AM UTC-8 Manish Dusane wrote: > All, > > Trying to compile latest open-iscsi-master on 3.10.0-957.10.1.el7.x86_64 > Getting

Release 2.1.5 tagged

I tagged and pushed release 2.1.5, which contains bug fixes. Enjoy! -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To

Re: iscsiadm: iface iter could not read dir /var/lib/iscsi/nodes/

Hi! My apologies to bharatvivek2972. I believe Mike, who was answering questions here, moved on from open-iscsi, and I didn't notice this thread needed more attention. I believe the problem here is that iscsiadm is not set up for parallel operation. So no, you can not run logins in parallel.

Re: [EXT] Concurrent usage of iscsiadm

Hi Vojtech: I know there's confusion around this issue, and as some testing at RH has shown, you can get away with using iscsiadm in parallel, as long as you're careful about what you do. For example, if each instance is trying to log into a different target, and there is no error handling

Re: Concurrent usage of iscsiadm

P.S. Perhaps Chris will chime in with his opinion, which may be a bit different than mine on this subject. Chris? On Wednesday, October 20, 2021 at 7:18:47 AM UTC-7 Vojtech Juranek wrote: > Hi, > I'd like to follow up with discussion about concurrent usage iscsiadm > tool. It > was discussed

Re: Yet another timed out connection

The target thinks there are two ways to reach it, so during discovery it is telling you both of those paths. Discovery, by design, reports all LUNs on the target, not just the one you want. So now, after discovery, your iscsi database thinks there are two IQNs to connect to, both reaching the

Re: hostbyte=DID_TRANSPORT_DISRUPTED: network issues or?

Yes, I believe your problems are network-related. I would advise taking iscsi NOPs off the table -- if you have a slow connection, the error recovery involved in a ping timeout can screw up I/O big time. On Friday, November 26, 2021 at 6:52:45 AM UTC-8 Mauricio wrote: > Now I was able

Re: iSCSI initiator setting max_sectors_kb=4 when target optimal_io_size=4096

Perhaps someone from RedHat can comment? I suspect this is a kernel change, though. On Sunday, November 21, 2021 at 6:31:39 PM UTC-8 alexi...@gmail.com wrote: > Hi, > > Looking into whether this is a bug, or an expect behavior with kernel 4.18+ > > RHEL 8.4 on AWS r5.xlarge hardware type,

Version 2.1.6 Available now.

I just tagged version 2.1.6 of open-iscsi. Enjoy. :) -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To view this

Updatges to iscsiuio

Hi All: A co-worker and I have recently pushed some updates to iscsiuio to make it more reliable. The first wave has been merged, and I have just submitted a pull request on github for the 2nd (and last) group of changes. If you care to review them, please check out github pull request 428

Re: [PATCH] drivers: scsi: Directly use ida_alloc()/free()

On Sunday, May 29, 2022 at 11:33:06 AM UTC-7 keliu wrote: > Use ida_alloc()/ida_free() instead of deprecated > ida_simple_get()/ida_simple_remove() . > > Signed-off-by: keliu > --- > drivers/scsi/hosts.c | 4 ++-- > drivers/scsi/scsi_transport_iscsi.c | 6 +++--- > 2 files changed, 5

Re: iscsi device with multipath

I'm sorry I didn't see this earlier. I don't see any replies. I can't quite parse your question, though. What are you asking about? On Thursday, June 16, 2022 at 11:57:20 PM UTC-7 zhuca...@gmail.com wrote: > How can we repoduce the error with "Multiply-cliamed blocks"? -- You received this

Using meson to build open-iscsi/iscsiuio

Hi All: I am planning on converting open-iscsi to use meson for building instead of 'make'. This would convert iscsiuio as well, which currently uses autoconf/autotools. It looks like the resulting systems is functionally equivalent (i.e. it builds the same stuff), and it's faster and a bit

Release 2.1.8 available

Hi All: I just tagged version 2.1.8 of open-iscsi in github. This release fixes a few bugs, and it adds support for building using meson. Building using make/autoconf is still supported but deprecated. Please check it out if you get a chance. -- Lee Duncan -- You received this message

Re: FCoE target with LIO

You should perhaps try the target-devel@vger mailing list? This list is about the initiator and (mostly) iSCSI. I don't _believe_ that LIO handles FCoE, but I may be wrong. Good luck. On Monday, September 5, 2022 at 2:51:23 AM UTC-7 opansz...@gmail.com wrote: > Hi dear Members. > > I want to

Should we use autotools (or something like it) for build system?

Hi! I'm considering updating the build system to use autoconf/automake, or maybe something newer like meson? See the discussion at: https://github.com/open-iscsi/open-iscsi/issues/359 -- Lee Duncan -- You received this message because you are subscribed to the Google Groups "open-iscsi"

Re: iscsiadm error "Could not load transport iser"

The iser transport is only supported for some cards. It's normally an infiniband transport. Do you have a CNA card (and infrastructure) that supports iser? On Tuesday, November 22, 2022 at 11:28:47 PM UTC-8 Luis Navarro wrote: > Hi all, > > I'm trying to test a new Ubuntu 22.04.1 LIO iSCSI

Re: Kernel BUG: kernel NULL pointer dereference on Windows server connect/disconnect

This is a mailing list for open-iscsi, the iSCSI initiator. Your issues seems to be with LIO, the in-kernel target code. I suggest the target development kernel mailing list: target-de...@vger.kernel.org It would help if, when you post there, you include your distribution. Also, is there any

Re: Could not logout of all requested sessions reported error (9 - internal error)

Could you try this with debugging in the daemon as well as the command? Also, can you share you iscsid.conf? Of course obfiscate your name/password settings if you wish. (But be sure username/password is not the same as username_in/password_in -- the sets have to be different). On Thursday,

Re: I have successfully mounted iSCSI targets from Synology NAS in Debian 11 Linux server for a construction company at Defu Lane 10, Singapore on 10 Feb 2023 Fri

This really isn't useful here IMHO. Did you have a question? Or a suggestion for changes? If not, we don't really need advertising here. On Friday, February 10, 2023 at 7:33:14 AM UTC-8 tdte...@gmail.com wrote: > Subject: I have successfully mounted iSCSI targets from Synology NAS in > Debian

Re: [RFC 0/9] Make iscsid-kernel communications namespace-aware

CSI SAN with multiple > customers accessing the SAN via unique containers. > > It should be possible to specify those files and directories as part of > the container config. > > Don > > On Wed, 2023-02-08 at 11:17 -0800, The Lee-Man wrote: > > I wanted to men

RFC: Making iSNS and SLP discovery code optional in open-iscsi?

Hi All: I posted an issue on github about this, but I wanted to mention it here, as well. As part of trying to make open-iscsi "container-ized", I have been looking at how to make the iscsi executable footprint smaller. As part of that, I have been looking first at shared libraries being used

Re: [RFC 0/9] Make iscsid-kernel communications namespace-aware

collide. Also, I can imagine situations where different daemons may want to set different configuration values. Currently they cannot. On Wednesday, February 8, 2023 at 9:41:02 AM UTC-8 The Lee-Man wrote: > From: Lee Duncan > > This is a request for comment on a set of patches that

Re: iscsi daemon in docker container

Hi: I'm trying to update open-iscsi, using Chris' patches as a starting place, so that it's network namespace aware, and hence could work in a docker container. I will soon (I hope) be testing it in a container. So far, it seems to work using "ip netns exec". Please see the RFC for patches I

SPAM control measure stepped up

Hi All: Most have probably noticed quite a bit of SPAM recently. This was because anyone could join this group, and then post. I have changed the group settings so that joining must be approved. And I have kicked out the latest SPAMer, and will continue to do so. Sadly, google groups makes it

<    1   2   3