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

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: 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

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

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

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

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: 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: 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,

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

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

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: 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

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

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

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,

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: 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: [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: 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.

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: 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

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

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

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

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: 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: [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

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: 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] 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: 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: 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: 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: 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: [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

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 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: 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: 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

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: 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: 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: 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: [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

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

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

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: [EXT] Re: udev events for iscsi

On Tuesday, April 21, 2020 at 11:56:23 PM UTC-7, Uli wrote: > > >>> The Lee-Man schrieb am 21.04.2020 um 20:44 > in > Nachricht > <618_1587494664_5E9F3F08_618_445_1_7f583720-8a84-4872-8d1a-5cd284295c22@googlegr > > > ups.com>: > > On Tuesday,

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: [PATCH] open-iscsi:Modify iSCSI shared memory permissions for logs

On Friday, April 17, 2020 at 2:08:57 AM UTC-7, Wu Bo wrote: > > Hi, > > Iscsid log damon is responsible for reading data from shared memory > and writing syslog. Iscsid is the root user group. > Currently, it is not seen that non-root users need to read logs. > The principle of minimizing the

Re: replacement_timeout Override

I'm glad you figured it out. Sorry I didn't reply sooner. On Monday, March 16, 2020 at 9:40:53 PM UTC-7, Marc Smith wrote: > > On Sat, Mar 14, 2020 at 10:28 AM Marc Smith wrote: > > > > Hi, > > > > I'm using open-iscsi version 2.1.1. I noticed that my > > "replacement_timeout" value set in

Re: There are two same sessions on the on client node? what's happen with it?

Those are two different sessions, as distinguished by their session numbers. On Thursday, March 5, 2020 at 7:42:46 PM UTC-8, can zhu wrote: > > [image: 微信图片_20200306114227.png] > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe

Re: [PATCH] iscsi-iname: fix iscsi-iname -p access NULL pointer without given IQN prefix

Thank you very much for this bug report and suggested patch, but I cleaned up the code and fixed it a little differently. On Wednesday, March 18, 2020 at 6:46:06 PM UTC-7, wubo40 wrote: > > From: Wu Bo > > iscsi-iname -p access NULL pointer without give IQN prefix. > > # iscsi-iname -p >

Tagging version 2.1.1 of open-iscsi/open-iscsi

Hi All: Just a heads up (for those that don't hang out on github) that I'm tagging version 2.1.1 of open-iscsi today, if there are no objections. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving

Re: iSCSI and Ceph RBD

Did Donald answer your question(s)? On Friday, January 24, 2020 at 1:50:28 PM UTC-8, Bobby wrote: > > Hi, > > I have some questions regarding iSCSI and Ceph RBD. If I have understood > correctly, the RBD backstore module > on target side can translate SCSI IO into Ceph OSD requests. The iSCSI

Version v0.100 of open-isns released

Hello: I've released version v0.100 of open-isns. This version includes: * fixes to IPv6 handling * fixes to existing test suite for openssl * adding new python3-based unittests, to replace deprecated perl-based tests Please help yourself, at https://github.com/open-iscsi/open-isns -- You

Re: [LSF/MM TOPIC] iSCSI MQ adoption via MCS discussion

On Tuesday, January 21, 2020 at 1:15:29 AM UTC-8, Bobby wrote: > > Hi all, > > I have a question please. Are these todo's finally part of Open-iSCSi > initiator? > > Thanks > No, not really. It's a "hard problem", and offload cards have somewhat worked around the problem by doing all of the

Re: [PATCH] iscsi: Add support for asynchronous iSCSI session destruction

On Friday, January 17, 2020 at 3:33:35 PM UTC-8, Gabriel Krisman Bertazi wrote: > > From: Frank Mayhar > > iSCSI session destruction can be arbitrarily slow, since it might > require network operations and serialization inside the scsi layer. > This patch adds a new user event to trigger the

Re: [PATCH v4] iscsi: Perform connection failure entirely in kernel space

On Wednesday, January 15, 2020 at 7:52:39 PM UTC-8, Martin K. Petersen wrote: > > > > Please consider the v4 below with the lock added. > > Lee: Please re-review this given the code change. > Martin: The recent change makes sense, so please still include my: Reviewed-by: Lee Duncan > > >

Re: iSCSI Multiqueue

On Wednesday, January 15, 2020 at 7:16:48 AM UTC-8, Bobby wrote: > > > Hi all, > > I have a question regarding multi-queue in iSCSI. AFAIK, *scsi-mq* has > been functional in kernel since kernel 3.17. Because earlier, > the block layer was updated to multi-queue *blk-mq* from single-queue. So >

Re: how it works

On Friday, January 10, 2020 at 8:44:05 AM UTC-8, Bobby wrote: > > > Hi, > > > - Question 1: The kernel still contains 2 files? > - Question 2: Do we still have those diagrams available online? > > > The kernel has many files, but those two files are still present for open-iscsi. If you look

Re: Who know more about this issue for iscsid?

On Tuesday, January 7, 2020 at 12:20:15 AM UTC-8, can zhu wrote: > > kernel: connection2:0: detected conn error (1020) > > iscsid: conn 0 login rejected: initiator failed authorization with target > > iscsid: Kernel reported iSCSI connection 2:0 error (1020 - > ISCSI_ERR_TCP_CONN_CLOSE: TCP

Re: [PATCH RESEND] iscsi: Don't destroy session if there are outstanding connections

On Thursday, December 26, 2019 at 12:31:55 PM UTC-8, Gabriel Krisman Bertazi wrote: > > From: Nick Black > > Hi, > > I thought this was already committed for some reason, until it bit me > again today. Any opposition to this one? > > >8 > > A faulty userspace that calls destroy_session()

Re: Open-iSCSI in research paper

On Tuesday, December 31, 2019 at 7:49:49 AM UTC-8, Bobby wrote: > > Hi all, > > I have come across this research paper (attached) called "*Design and > implementation of IP-based iSCSI Offoad Engine on an FPGA*" and the > authors have mentioned they have used open source software based >

Re: Openiscsi Release Schedule

On Friday, December 13, 2019 at 9:01:40 AM UTC-8, Karla Thurs wrote: > > Hello, > What is your latest version of Openiscsi and what was the release date? Do > you happen to have a release schedule that you follow? I see your dates for > old releases but don't see anything about following a

Re: [PATCH] Check whether socket is opened successfully in find_vlan_dev func

On Sunday, December 8, 2019 at 10:32:54 PM UTC-8, liuzhiqiang (I) wrote: In find_vlan_dev func, socket should be checked before used. Signed-off-by: Zhiqiang Liu --- usr/iscsi_net_util.c | 4 1 file changed, 4 insertions(+) diff --git a/usr/iscsi_net_util.c b/usr/iscsi_net_util.c

Re: reboot hangs with "Reached target shutdown", who can help me?

Okay, I checked CentOS 8, and the services seem very similar to what I'm familiar with. You do indeed need to make sure your nodes have startup set to automatic. Use something like: > zsh> sudo iscsiadm -m node --op update --name 'node.conn[0].startup' --value automatic to update all nodes

Re: reboot hangs with "Reached target shutdown", who can help me?

On Tuesday, December 10, 2019 at 6:25:00 AM UTC-8, can zhu wrote: > > os version: > > CentOS Linux release 7.4.1708 (Core) > > kernel version: > > 3.10.0-693.el7.x86_64 > > > systemd version: > > *systemd*-219-42.el7.x86_64 > > > Mount iscsi devices on the node(iscsi client node) and reboot os,

Re: Re: iSCSI packet generator

ux Kernel Development. > > > On Tuesday, December 10, 2019 at 11:34:49 AM UTC+1, Bobby wrote: >> >> >> Perfect ! After this reply, I had to dig deeper and now it makes >> sensethanks a lot The Lee-Man for explaining it so effectively... >> >> >&

New Version Tagged

I have tagged version 2.1.0 of open-iscsi. -- 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 discussion on the

Re: Re: iSCSI packet generator

On Friday, November 8, 2019 at 10:40:08 AM UTC-8, Bobby wrote: > > > Hi Ulrich, > > Thanks for the hint. Can you please help me regarding following two > questions. > > - Linux block layer perform IO scheduling IO submissions to storage device > driver. If there is a physical device, the block

Re: iSCSI packet generator

On Monday, November 4, 2019 at 2:49:08 AM UTC-8, Bobby wrote: > > Hi > > I have two virtual machines. One is a client and other is a sever (SAN). I > am using Wireshark to analyze the iSCSI protocols between them. > > Someone recommended me, in addition to a packet analyzer, I can also use a >

Re: after changing storage ports from 1Gig to 10Gig unable to access the vm, Openstack level vm is going to error state

On Monday, October 7, 2019 at 7:46:04 AM UTC-7, Kuruva Maddileti wrote: > > Hi Team, > > We have changed the Unity storage ports from 1Gig to 10Gig. After that we > have deleted the old iqn's from storage level and compute level. > > old iqn's : > > 170.0.0.10 > 170.0.0.11 > > New 10Gig iqn's : >

Re: iscsiadm unable to connect to iscsd

See https://github.com/open-iscsi/open-iscsi/pull/174 On Friday, September 20, 2019 at 2:02:20 AM UTC-7, Dirk Laurenz wrote: > > Hi, > > want to read the session stats for a connection, but iscsiadm claims not > to be able to connect to iscsd. > I'm not sure how to debug this: > >

Re: iscsiadm unable to connect to iscsd

Okay, I believe I found the problem, and it's one that I've seen before. On one particular path -- in this case, when you specify "-s" as well as "-r N" -- the code path forgets to set the timeout to "none" when communicating with iscsid. I have pushed my change to

Re: iscsiadm unable to connect to iscsd

On Friday, September 20, 2019 at 2:02:20 AM UTC-7, Dirk Laurenz wrote: > > Hi, > > want to read the session stats for a connection, but iscsiadm claims not > to be able to connect to iscsd. > I'm not sure how to debug this: > > $host:/etc/iscsi # iscsiadm -m session > tcp: [1] $IP1:3260,1032

Re: Open-iscsi slow boot

On Thursday, June 27, 2019 at 11:44:11 AM UTC-4, Randy Broman wrote: > > I appreciate your interest, and I've attached a text file which I hope > is responsive to your request. > > R > > On Wed, Jun 26, 2019 at 8:55 AM The Lee-Man wrote: > > > > On Tuesday, J

Re: Open-iscsi slow boot

On Tuesday, June 25, 2019 at 11:31:03 AM UTC-4, Randy Broman wrote: > > Thanks for your response. I'm using Kubuntu 19.04. I disabled the iscsi > service and in fact the boot was much faster: > > > I'm not understanding what's going on with your system. I suspect there's more than just an unused

Re: Open-iscsi slow boot

On Saturday, June 22, 2019 at 11:00:44 AM UTC-4, Randy Broman wrote: > > I have open-iscsi installed on Kubuntu 19.04, to access shared storage on > a QNAP NAS server. The setup works, but open-iscsi slows boot: > > $ systemd-analyze blame > 2min 6.105s open-iscsi.service > 10.076s

Re: [bug report][scsi blk_mq] data corruption due to a bug in SCSI LLD error handling

I think the point is that the sg path is not equal to the real IO path. You are (currently) never going to get correct error handling from the sg path, which is considered out of band. So what are you trying to do here? Are you really developing software that uses the sg path, and you need

Re: tcmu-runner failed to find module target_core_user

Note: target development mailing list is at: target-de...@vger.kernel.org, which you may have to join, first. -- 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

Re: tcmu-runner failed to find module target_core_user

On Thursday, March 28, 2019 at 8:55:07 PM UTC-7, Ravi Salamani wrote: > > Hi all, > I am able to build and install tcmu-runner, but failed to run run > tcmu-runner with following error > > $tcmu-runner > > Starting... kmod_module_new_from_lookup() failed to find module > target_core_user

Re: [PATCH] Update iscsid to always restart

On Thursday, February 21, 2019 at 2:35:46 PM UTC-8, fred.her...@oracle.com wrote: > > From: Fred Herard > > This change adds Restart=always systemd service option to iscsid.service > config file so that iscsid daemon is always restarted. This is > particularly useful when using iscsi boot

Re: [RFC] Add source address binding to iSER

On Wednesday, February 6, 2019 at 9:11:45 AM UTC-8, Nikhil Valluru wrote: > > Hi Robert, > > I am looking for a similar fix and wanted to know if this patch was > accepted into the linux kernel? > > Thanks, > Nikhil > > As a quick look at linux upstream shows, this code is not in the kernel.

Re: [RFC 1/1] libiscsi: Fix race between iscsi_xmit_task and iscsi_complete_task

On Tuesday, July 17, 2018 at 8:56:53 AM UTC-7, Anoob Soman wrote: > > On 09/07/18 11:43, Anoob Soman wrote: > > On 02/07/18 16:00, Anoob Soman wrote: > >> --- > >> drivers/scsi/libiscsi.c | 6 ++ > >> 1 file changed, 6 insertions(+) > >> > >> diff --git a/drivers/scsi/libiscsi.c

Re: Error while performing writes using dd or mkfs on iSCSI initiator.

On Wednesday, January 23, 2019 at 1:48:19 PM UTC-8, iamlinonym...@gmail.com wrote: > > We have a LIO target on RHEL 7.5 with the lun created using fileio through > targetcli. We exported it > to RHEL initiator on the same box (Tried with other box as well). > On the lun, when we do mkfs for

Re: sysfs interface sometimes does not get the block device name, for a logged in iSCSI target

On Monday, December 17, 2018 at 9:08:54 AM UTC-8, Satyajit Deshmukh wrote: > > > > On Sunday, December 16, 2018 at 5:30:29 PM UTC-8, The Lee-Man wrote: >> >> On Friday, December 14, 2018 at 12:13:46 PM UTC-8, Satyajit Deshmukh >> wrote: >>> >>>

Re: Running iscsiadm in containers

On Sunday, December 16, 2018 at 5:14:03 PM UTC-8, m...@datera.io wrote: > > As a baseline here are the previous threads discussing this issue > including the RFC from Chris Leech. > > https://groups.google.com/forum/#!msg/open-iscsi/vWbi_LTMEeM/P8-oUDkb14YJ >

Re: sysfs interface sometimes does not get the block device name, for a logged in iSCSI target

On Friday, December 14, 2018 at 12:13:46 PM UTC-8, Satyajit Deshmukh wrote: > > Hello, > > An update on the issue. I could observe that the target entries were not > populated under sysfs. > > This is for a session that has a valid block device: > $ ls /sys/class/iscsi_session/session778/device >

Re: sysfs interface sometimes does not get the block device name, for a logged in iSCSI target

On Monday, December 10, 2018 at 5:52:19 PM UTC-8, Satyajit Deshmukh wrote: > > Hello, > > We are fairly frequently now running into this. Looks like an issue with > the sysfs interface. > > iscsi_sysfs_get_blockdev_from_lun() sometimes does not find the SCSI block > device (say /dev/sdd) for a

Re: Query regarding iscsi initiator login via specific port

On Monday, November 26, 2018 at 4:43:17 PM UTC-8, Sastha M wrote: > > Hello all, > > Is there a provision today with iscsiadm utility to create a iscsi login > connection via specific initiator port number? The initiator port can be > provided from the user end. Please help me in finding the

Re: Patch for faster iscsi logins by optimized idbm_lock() and idbm_unlock() APIs

On Monday, November 12, 2018 at 5:02:44 PM UTC-8, satyajit.deshm...@nutanix.com wrote: > > Hello, > > We had a use case, where we had to log into multiple iSCSI targets in > parallel. And it was important for these operations to complete in a timely > manner. > We found 2 major codes that

Re: Running iscsiadm in containers

ailesh. > > On Monday, October 29, 2018 at 10:57:06 AM UTC-7, The Lee-Man wrote: >> >> On Monday, October 29, 2018 at 10:40:07 AM UTC-7, dat...@gmail.com wrote: >>> >>> Thanks for the reply. We are facing issues when we run iscsiadm in the >>> co

  1   2   3   >