Re: [Patch v2 2/2] libiscsi: Remove iscsi_destroy_session

On Thursday, September 14, 2017 at 12:57:58 AM UTC-7, Johannes Thumshirn wrote: > > On Wed, Sep 13, 2017 at 05:09:03PM -0700, Lee Duncan wrote: > > On 07/13/2017 09:11 AM, Khazhismel Kumykov wrote: > > > iscsi_session_teardown was the only user of this function. Function > > > currently is

Re: facing problem to mount EMC storage in ubuntu 14.04/

On Saturday, September 30, 2017 at 11:11:24 AM UTC-7, sali wrote: > > Dear Team, > > anybody can help me to mount storage in linux ubuntu 14.04 ? > > i tried with open iscsi, but i can see the drives but i cant format the > disk > > could you please help me to fix this issue ? > > > regards, >

Re: [iscsiadm] iscsiadm creates multiple same sessions when run with --login option in parallel.

Thanks for this report. I'll try to reproduce this myself and see what is going on. It is certainly the case that there is insufficient locking in iscsid with respect to multiple threads, IMHO, so I am not surprised. On Wednesday, September 27, 2017 at 11:43:02 PM UTC-7, Tangchen (UVP) wrote:

Re: [Bug?] Stray session in sysfs

On Tuesday, August 8, 2017 at 7:55:41 AM UTC-7, Frank Ritsema wrote: > > During changes in the iscsi SAN layout the initiator got confused, holding > on to a session in RAM while this session should not exists. > > "iscsiadm -m session" shows 1 session. Trying to delete the record for it >

Re: New version for open-iscsi?

Version 2.0.875 has been released. On Friday, September 1, 2017 at 9:38:48 AM UTC-7, The Lee-Man wrote: > > On Sep 1, 2017, at 9:37 AM, Chris Leech <cleech@*.com <cle...@redhat.com>> > wrote: > > > > On Thu, Aug 31, 2017 at 10:41:30AM -0700, The Lee-Man wr

New version for open-iscsi?

I would like to update the version of open-iscsi from 2.0.874 to 2.0.875. Any objections or suggestions? -- Lee -- 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: backstores/iblock missing

This does not seem related to open-iscsi. It sounds like you are asking about targetcli-fb. On Monday, December 11, 2017 at 11:11:23 PM UTC-8, malteseLun wrote: > > Hello > I have centos7.4 running and came across few tutorials which tell > backstores/iblock configuration.I can't see iblock on

Re: backstores/iblock missing

mailing list for targetcli-fb is https://lists.fedorahosted.org/mailman/listinfo/targetcli-fb-devel > > On Friday, December 15, 2017 at 9:17:01 PM UTC+3, The Lee-Man wrote: >> >> This does not seem related to open-iscsi. It sounds like you are asking >> about targetcli-fb

Re: [PATCH 0/9] use network namespace for iSCSI control interfaces

I will review these patches individually (it might take an extra day), but I have an initial question: will this change the sysfs interface for iscsi. But I'm pretty sure the answer is yes. Which would mean we could break other things. If this is true, perhaps we should bump the major version

Re: [PATCH 0/9] use network namespace for iSCSI control interfaces

I have reviewed all the patches to the best of my ability. Other than the comments I made, please add my reviewed-by tag to all of them. I was surprised as how pervasive the single-namespace assumption was buried in the code, as evidenced by how much you had to change. I assume you've tested

Re: [PATCH 9/9] iscsi: filter flashnode sysfs by net namespace

On Tuesday, October 31, 2017 at 3:41:45 PM UTC-7, Chris Leech wrote: > > Finished the net namespace support for flashnode sysfs devices > Needs a better explanation, though I can understand if you were tired of typing by this point! > > Signed-off-by: Chris Leech > --- >

Re: [PATCH 5/9] iscsi: set netns for iscsi_tcp hosts

On Tuesday, October 31, 2017 at 3:41:38 PM UTC-7, Chris Leech wrote: > > This lets iscsi_tcp operate in multiple namespaces. It uses current > during session creation to find the net namespace, but it might be > better to manage to pass it along from the iscsi netlink socket. > Could you add

Re: [iscsiadm] iscsiadm creates multiple same sessions when run with --login option in parallel.

oglegroups.com > *Cc:* guijianfeng <guijianf...@huawei.com>; Zhangyanfei (YF) < > yanfei.zh...@huawei.com> > *Subject:* RE: [iscsiadm] iscsiadm creates multiple same sessions when > run with --login option in parallel. > > > > Hi leeman > > > > I

Re: [PATCH 8/9] iscsi: rename iscsi_bus_flash_* to iscsi_flash_*

On Tuesday, October 31, 2017 at 3:41:45 PM UTC-7, Chris Leech wrote: > > cleanups after the bus to class conversion > If this has no functional change I'd prefer it if you made that more clear. Or maybe it's just me? Not that I have anything against cleanups, in general. > > Signed-off-by:

Small changes to get open-iscsi compiling with new gcc 7.2.1

I noticed our openSUSE build service builds of open-iscsi were failing, and I tracked it down to updates in gcc and in the gcc C Library package. In short, all of these cleanups were conceptually simple and should *not* cause any functional changes, unless you were trying to overflow strings.

Re: [RFC dracut 1/1] unexpected boot failure due to races between iscsistart for multiple interfaces

On Thursday, December 7, 2017 at 11:49:53 AM UTC-8, cathy.z...@oracle.com wrote: > > From: Cathy Zhou > > Co-existence of iscsid and iscsistart can lead to unexpected iSCSI boot > behavior: > > We ran into iSCSI netboot failure when multiple interfaces are configured >

Re: Small changes to get open-iscsi compiling with new gcc 7.2.1

Note: some of these changes are in iscsiuio. On Saturday, December 2, 2017 at 2:36:12 PM UTC-8, The Lee-Man wrote: > > I noticed our openSUSE build service builds of open-iscsi were failing, > and I tracked it down to updates in gcc and in the gcc C Library package. > >

RFC: open-iscsi summit?

Hi All: I have been thinking that, with all the new development going on in Linux and in our own open-iscsi community, that a summit would be a good idea. It turns out both Chris and I live in the Northwest US (near Portland, OR), and it would be easy for us to get together and talk. But it

Re: RFC: open-iscsi summit?

On Thursday, May 31, 2018 at 3:59:44 PM UTC-7, Chris Leech wrote: > > On Tue, May 15, 2018 at 01:25:34PM -0700, The Lee-Man wrote: > > Hi All: > > > > I have been thinking that, with all the new development going on in > Linux > > and in our own open-isc

Re: [PATCH 0/4] libopeniscsiusr iface record fixes

This just points out how much we need to (1) get our self-test running, and (2) add to it for cases like this. Thank you for testing! On Wednesday, June 13, 2018 at 8:26:15 AM UTC-7, Chris Leech wrote: > > In testing the latest code against a variety of iSCSI HBAs, I found some > regressions in

Re: [PATCH 0/4] libopeniscsiusr iface record fixes

On Thursday, June 14, 2018 at 9:45:56 AM UTC-7, Chris Leech wrote: > > On Wed, Jun 13, 2018 at 08:25:41AM -0700, Chris Leech wrote: > > In testing the latest code against a variety of iSCSI HBAs, I found some > > regressions in the iface handling after merging the libopeniscsiusr > > code. > >

Re: hdparm -I gives random output on open-iscsi connected CDROM device

On Thursday, June 14, 2018 at 8:02:47 AM UTC-7, a...@seewald.at wrote: > > Hi all, > > When I run hdparm -I on a local device (CDROM) I get... > > /dev/sr0: > > ATAPI CD-ROM, with removable media > Model Number: TSSTcorp BDDVDW SN-506BB > Serial Number: R90H6YLG7000QR

Re: RFC: open-iscsi summit?

On Tuesday, May 15, 2018 at 1:25:34 PM UTC-7, The Lee-Man wrote: > > Hi All: > > I have been thinking that, with all the new development going on in Linux > and in our own open-iscsi community, that a summit would be a good idea. > > It turns out both Chris and I live in t

Re: iscsiadm utility to update persistent address of all sessions, to a given address.

On Wednesday, February 8, 2017 at 1:56:07 AM UTC-8, Satyajit Deshmukh wrote: > > Hello, > > We have a setup, where we are using the iSCSI redirect functionality, > where we connect to a highly available persistent address, and get > redirected to a different address/portal. > Our setup allows

Re: How to force `iscsiadm` to create only one session on login?

On Tuesday, May 1, 2018 at 8:31:49 AM UTC-7, Ciprian Dorin Craciun wrote: > > Hello all! > > I'm using `open-iscsi` version `2.0.873` on OpenSUSE 13.2, and I am trying > to connect to a Linux LIO-based target with the following command: > > > iscsiadm --mode node --portal IP:3260,1

Re: Frequent kernel crashes (reboots) on nodes with iscsi attached

Please check out this thread, from this group: https://groups.google.com/forum/#!topic/open-iscsi/-HOsGZ_GT9I > -- 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: backstores/iblock missing

On Thursday, December 21, 2017 at 12:10:52 AM UTC-8, malteseLun wrote: > > Is there a list that I can see CLIs for scsi targets? actually I cant find > openiscsi on centos 7.4. couldnot even install with yum. I am trying to > implement "IBLOCK(any block device).I cant see IBLOCK on targetcli and

Tagging a new version today

Hi All: I'm sorry I've been slack at keeping the open-iscsi users informed, but I'm planning on tagging a new version of open-iscsi this morning. If there are any issues with this, please let me know. -- Lee Duncan -- You received this message because you are subscribed to the Google Groups

Re: Proxmox VE iSCSI strange log on Synology Storage

On Wednesday, January 31, 2018 at 10:25:11 AM UTC-8, juniper wrote: > > Hi, > > i have a cluster of 5 server connected (iSCSI) with a Synology RS3617xs+ > (10GBE interface); > > all seems working fine but on Synology i have some strange log: > > continuous: > > 2018-01-31T18:39:33+01:00 mksyn

Re: Proxmox VE iSCSI strange log on Synology Storage

'll try to trace some sessions (tcpdump) trying to debug what >> happens. >> >> >> >> Il 1 feb 2018 20:20, "The Lee-Man" <leeman.dun...@gmail.com> ha scritto: >> >> On Wednesday, January 31, 2018 at 10:25:11 AM UTC-8, juniper wrote: >>&

Re: 4.14.16 kworker deathspin if logged out without deleting scsi devices

On Thursday, February 15, 2018 at 2:41:11 PM UTC-8, Maxim Ivanov wrote: > > Investigating it further, it looks like it is working fine if multipathd > didn't start at all (unit is masked). If it was started, then stopped, > logout hangs. > I just tested on Tumbleweek, using a 4.15 kernel. I

Re: iSCSI opcode 0x3c vendor specific

On Thursday, February 15, 2018 at 6:52:23 PM UTC-8, Jim Gunnarsson wrote: > > Hey > > I currently tweaking the configuration settings for open-iscsi on RHEL 7 > with > Oracle Database 11g as load. It works, but can be improved. > > During a tcpdump of the traffic flow I found an outbound, to

Re: [RFC dracut 1/1] unexpected boot failure due to races between iscsistart for multiple interfaces

On Saturday, December 23, 2017 at 8:13:01 AM UTC-8, si-wei liu wrote: > > > > On 12/21/2017 05:03 PM, Lee Duncan wrote: > > That seems like the wrong approach to me. iscsiadm/iscsid were designed > for this. The iscsistart script was designed for sing, one-shot use, and is > not used in dracut

Re: [PATCH] scsi: libiscsi: Allow sd_shutdown on bad transport

On Wednesday, December 20, 2017 at 6:39:49 PM UTC-8, Martin K. Petersen wrote: > > > > If, for any reason, userland shuts down iscsi transport interfaces > > before proper logouts - like when logging in to LUNs manually, without > > logging out on server shutdown, or when automated scripts

Re: [PATCH 3/4] libopeniscsiusr: clear errno before calling strtoll

Chris, what did you decide to do here? On Monday, June 25, 2018 at 1:01:45 AM UTC-7, Uli wrote: > > >>> Chris Leech schrieb am 13.06.2018 um 17:25 in > Nachricht > <20180613152545.1049967-4-cle...@redhat.com>: > > errno must be set to 0 before calling strtoll or error checking will > > have

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

This makes sense to me. I was hoping Chris would comment since he's looked more closely at the locks. @chris ? On Monday, July 2, 2018 at 8:00:48 AM UTC-7, Anoob Soman wrote: > > When a target sends Check Condition, whilst initiator is busy xmiting > re-queued data, could lead to race between

Re: changes to node.session.queue_depth doesn't take effect?

On Wednesday, June 27, 2018 at 12:34:56 PM UTC-7, Neutron Sharc wrote: > > Hi all, > > I will describe the problem I saw step by step. Please take patience. > > I'm using tgt as iscsi target server (fujita/tgt from github) on Ubuntu > 16.04. iscsi initiator runs the stock open-iscsi coming with

Re: [PATCH] scsi: libiscsi: Fix an error handling path in 'iscsi_session_setup()'

On Saturday, August 25, 2018 at 10:16:52 AM UTC-7, Christophe JAILLET wrote: > > All error handling paths in this function go through > 'iscsi_host_dec_session_cnt()' except this one. > Fix it and properly decrement the number of active sessions in such a > case. > > Signed-off-by: Christophe

Re: fdisk -l does not show VessRAID in Fedora 28

On Tuesday, September 11, 2018 at 9:04:42 AM UTC-7, rkud...@fordham.edu wrote: > > and any reason for this command to core dump? > > iscsiadm -m session -P 3 > > iSCSI Transport Class version 2.0-870 > > version 6.2.0.874 > > Segmentation fault (core dumped) > > That version of open-iscsi seems

Re: [PATCH] scsi: iscsi_tcp: set BDI_CAP_STABLE_WRITES when data digest enabled

On Friday, March 9, 2018 at 11:23:56 AM UTC-8, Jianchao Wang wrote: > > iscsi tcp will first send out data, then calculate and send data > digest. If we don't have BDI_CAP_STABLE_WRITES, the page cache will > be written in spite of the on going writeback. Consequently, wrong > digest will be

Re: BUG: unable to handle kernel NULL pointer sysfs_find_dirent+0x16/0xf0 (in iscsi_iser_ep_disconnect)

On Monday, April 9, 2018 at 9:38:51 PM UTC-7, tej parkash wrote: > > Hi All, > > On RHEL 7.4 once we have seen that kernel panic while doing iser > disconnect. Following is the stack observed > > [276413.836283] RIP: 0010:[] [] > sysfs_find_dirent+0x16/0xf0 > [276413.836319] RSP:

Re: iscsid: Kernel reported iSCSI connection 9:0 error (1011 - ISCSI_ERR_CONN_FAILED: iSCSI connection failed) state (3)

On Tuesday, April 10, 2018 at 11:21:58 AM UTC-7, mark wrote: > > Hello > > > I have 3 CentOS 6 connecting to a ISCSI server with Targecli suddenly one > of then lost connection and my mounted partition have they filesystem go > to read-only. > > Thanks for attention. > You're going to need to

Re: [PATCH] Reduce delays to improve iscsi boot performance

On Monday, April 16, 2018 at 2:38:01 PM UTC-7, The Lee-Man wrote: > > On Friday, April 13, 2018 at 3:19:11 PM UTC-7, cathy.z...@oracle.com > wrote: >> >> From: Cathy Zhou <cathy.z...@oracle.com> >> >> iscsi boot performance can be improved by

Re: [PATCH] Reduce delays to improve iscsi boot performance

On Friday, April 13, 2018 at 3:19:11 PM UTC-7, cathy.z...@oracle.com wrote: > > From: Cathy Zhou > > iscsi boot performance can be improved by sleep() with finer > grained interval and exponential backoff. > > Signed-off-by: Cathy Zhou > --- >

Re: initiator/targetd debug advice

On Monday, April 23, 2018 at 3:37:12 PM UTC-6, Peter Larsen wrote: > > Using targetd 0.8.6 (RHEL7) and iscsi-initiator-utils-6.2.0, I'm looking > for ways to diagnose random disconnects under load. The initiator indicates > it's logged into the target, but all IO fails. A logout and login fixes

Update version number to 2.0.877?

Hi: It looks like there have been almost 50 changes, not counting merge entries, since version 2.0.876. Anyone object to updating the version number to 2.0.877? -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and

Re: [PATCH] scsi: iscsi_tcp: Explicitly cast param in iscsi_sw_tcp_host_get_param

On Thursday, October 4, 2018 at 10:20:56 AM UTC-7, Nathan Chancellor wrote: > > Clang warns when one enumerated type is implicitly converted to another. > > drivers/scsi/iscsi_tcp.c:803:15: warning: implicit conversion from > enumeration type 'enum iscsi_host_param' to different enumeration type

New open-iscsi minor version?

I'm planning on updating the open-iscsi version to 2.0.877 "real soon now", unless I hear any objections. Here's a list of what's changed: Antoine de Maleprade (1): iscsid: fix logging level when starting daemon Cathy Zhou (1): Reduce delays to improve iscsi boot performance Chris

Re: Running iscsiadm in containers

On Tuesday, October 23, 2018 at 9:03:01 AM UTC-7, Shailesh Mittal wrote: > > Hi there, > > I understand that it was the topic of discussion earlier. As containers > are getting used more and more to run applications, there are frameworks > like Kubernetes (and more) where the calls to talk to

Re: Running iscsiadm in containers

Sorry, I should have asked: what issues have you experienced with containers? On Wednesday, October 24, 2018 at 1:27:43 PM UTC-7, The Lee-Man wrote: > > On Tuesday, October 23, 2018 at 9:03:01 AM UTC-7, Shailesh Mittal wrote: >> >> Hi there, >> >> I understand that

Re: Should iscsid.service be enabled or disabled in a systemd environment

On Saturday, November 3, 2018 at 5:36:41 AM UTC-7, david.partri...@perdrix.co.uk wrote: > > I'm not really up to speed with systemd and wanted to enable iscsi on my > system. > > So I issued a "systemctl enable iscsid" after a reboot I saw it was > running and was happy! > > But after some

Re: Memory leak in pSCSI backend?

On Saturday, October 27, 2018 at 8:30:52 AM UTC-7, Ben Klein wrote: > > Hi, > > I've been trying to get a DVD-ROM drive working over iSCSI. I'm using > targetcli on the target and iscsiadm/iscsi_discovery on the initiator. > > Target is running 4.18.16 unpatched from kernel.org, with AMD64 >

Re: Running iscsiadm in containers

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 > container and iscsid on the host. At that time, iscsiadm can't reach to > iscsid at all and all iscsiadm commands fail. > > If we run iscsiadm

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

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: Initial Login Advice

On Thursday, November 1, 2018 at 11:54:31 AM UTC-7, marc.sm...@parodyne.com wrote: > > Hi, > > We use open-iscsi in our "ESOS" project. We have a custom rc/init script > (not RHEL / Debian based), which starts the iSCSI initiator stack at boot. > The current start() function in that script

Re: RFC: A problem with stale session information?

Hi Mike: Thank you for your reply. On Friday, September 21, 2018 at 9:35:25 AM UTC-7, Mike Christie wrote: > > > ... > > This is one of those things where I said I would fix if anyone ever > complains, but luckily I made it through my entire time as maintainer > and no one ever did. So, I

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

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

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

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

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

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

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

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

<    1   2   3   >