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

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

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

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

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

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

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

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

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

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: [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: [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: [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: 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: [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: 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: [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: Recovering initiator connection when target (IET) is restarted - root over iscsi

On Monday, August 7, 2017 at 2:35:26 PM UTC-7, Bob Marris wrote: > > I'm running my initiator's root partition via open-iscsi to an IET target. > > I'm testing failure scenarios, and in the event of a target reboot (or > daemon restart) my initiator seems to hang. I was hoping it would be able

Re: installing initiator and target

On Sunday, July 30, 2017 at 10:01:20 PM UTC-7, jayshankar nair wrote: > > Hi, > I like to install the iscsi initiator and target on fedora 25. PLease > email me the README file. > > Thanks, > Jayshankar > Why do you not install the package and look at the README? Or use git to download the

Re: How to limit logins to discovered iscsi-targets on Linux

On Tuesday, July 18, 2017 at 7:43:13 AM UTC-7, Damir wrote: > > Hello! > > I try to configure iscsi initiator on Linux (Mageia 5 x86_64, open-iscsi). > The goal is to automatically connect to iscsi-storage by starting linux. > Iscsi-storae is configured on 10.11.104.10 (by the provider, and I

Re: [RFC] C/Python initiator userspace API approach.

On Wednesday, April 26, 2017 at 9:15:50 AM UTC-7, Christian Seiler wrote: > > On 04/26/2017 01:03 PM, Gris Ge wrote: > > On Wed, Apr 26, 2017 at 09:14:35AM +0200, Christian Seiler wrote: > >> On 04/26/2017 01:11 AM, Gris Ge wrote: > >>> B) Expand iscsid to listen on a socket for IPC with

Re: [PATCH] iscsid: Add qedi ping transport hook

Applied. Please note that pull requests via github are easier to apply than traditional patch emails. On Wednesday, April 26, 2017 at 2:27:03 AM UTC-7, Nilesh Javali wrote: > > iscsiuio ping is operational for qedi. > Add missing qedi transport hook for ping support. > > Signed-off-by: Nilesh

Re: LTO-4 iSCSI performance less than expected ...

On Friday, April 14, 2017 at 4:31:05 AM UTC-7, david.partri...@perdrix.co.uk wrote: > > Let's try another tack. > > Will "mt-st -f /dev/st0l /stoptions 35" turn on MTWEOFI? > > Dave > Hi Dave: I don't know. I download mt-st, which I've never seen before, and perhaps you mean: > # mt-st -f

Re: LTO-4 iSCSI performance less than expected ...

On Friday, March 31, 2017 at 2:23:30 PM UTC-7, david.partri...@perdrix.co.uk wrote: > > I don't know? How do I find out? Should I have it set? > >> >> Have you set the Write Immediate Filemark option for the st driver? >> > There are a couple of ways to enable writing immediate filemarks in

Re: LTO-4 iSCSI performance less than expected ...

On Monday, March 27, 2017 at 9:03:59 AM UTC-7, david.partri...@perdrix.co.uk wrote: > > I'm connecting my Linux server to an LTO-4 tape drive over a 1 gigabit LAN > with very little other activity. > > Doing some hand waving, I guess that I should allow ten bits per byte and > a protocol

Moving target-isns to the open-iscsi github project

I would like to move the target-isns project, owned and managed by Christophe Vu-Brugier on github, under our open-iscsi project. Chris and Andy in particular, do you have any objections? See https://github.com/cvubrugier/target-isns for the target-isns project. -- Lee Duncan -- You

Re: iscsistart -N skips offload NICs causing boot to fail on debian

On Friday, December 23, 2016 at 7:32:27 AM UTC-8, Christian Seiler wrote: > > On 12/22/2016 07:07 PM, Andrew Patterson wrote: > > I found a bnx2x card with iscsi hardware offload support. Running > > iscsistart -f does bring the interace up and assign an IP to it as > > long as

Re: Problem with iSCSI connected LTO-2 tape drive

Hi David: I have created Issue#35 for this on github. On Thursday, December 15, 2016 at 2:00:15 PM UTC-8, David C. Partridge wrote: > > You’re right, it is in section 8.2. Maybe it needs to be said in 8.1.1 as > well? > > > > Dave > > > > *From:* open-iscsi@googlegroups.com

Re: Problem with iSCSI connected LTO-2 tape drive

ng on Windows 10 x64 >> >> Dave >> >> On Saturday, December 10, 2016 at 10:38:43 PM UTC, The Lee-Man wrote: >>> >>> What is your setup? What OS and version are you running on, what is your >>> transport, and what tape drive are you using? >>>

Re: Problem with iSCSI connected LTO-2 tape drive

What is your setup? What OS and version are you running on, what is your transport, and what tape drive are you using? On Saturday, December 10, 2016 at 9:24:33 AM UTC-8, Dave partridge wrote: > > I did: > > root@Charon:/home/amonra# mt -f /dev/st0 fsf 1 > mt: /dev/st0: rmtioctl failed:

Re: [RESEND][PATCH v2 0/3] Add QLogic FastLinQ offload iSCSI driver (qedi) support

Nilesh: These patches look good to me, but I'd like to hear from Chris. (And Mike, if he so chooses.) I know Hannes hoped this project would *not* use iscsiuio, but I saw a pledge to made iscsiuio card-agnostic "some time soon". On Tuesday, November 29, 2016 at 9:47:49 PM UTC-8, Javali,

Re: [PATCHv2 0/2] Handle iscsid shutdown more cleanly

Please ignore this. I am going to post an updated version that sorts out the "poll()" logic in iscsid_req.c, as Uli requested with the earlier patch. On Tuesday, November 22, 2016 at 2:44:56 PM UTC-8, The Lee-Man wrote: > > From: Lee Duncan <lduncan@*.com <ldun...@suse.com&

RFC: iscsid shutdown hangs with system when service manually killed

In this wonderful new world of systemd, I have an issue with stopping the iscsid service when the daemon has died or been killed. My setup: * I have an iscsid.socket unit file, which is enabled and started * I have an iscsid.service unit file, which controls the iscsid daemon. This is disabled

Re: [PATCH] iBFT 'origin' is an enum, not a string

I have not seen any objections, so I'm going to merge the pull request on github for this patch. On Saturday, November 12, 2016 at 11:50:17 AM UTC-8, The Lee-Man wrote: > > From: Lee Duncan <leeman.dun...@gmail.com> > > A recent change, commit 4959a89f421fdebc, modified open

Re: how to get iscsi target details(iqn) from device OS name programmatically at initiator side

On Thursday, November 10, 2016 at 11:03:09 AM UTC-7, lvpriyana...@gmail.com wrote: > > i need C/C++ library/API at initiator side which can give me the iscsi > target details(iqn) when i pass the OS device name or scsi-channel-lun > details. > > for example input will be "/dev/sdc" or something

Re: why certain function name prefix of “_ _” (double underscore)

On Tuesday, November 8, 2016 at 4:29:05 PM UTC-7, Raghu Murugesan wrote: > > I am reading the source code of open-iscsi. In source files, I see few > functions start with prefix "__". Whats the reason behind naming a function > with double underscore as prefix in general in C language? > >

Re: iscsi: make mutex for target scanning and unbinding per-session

On Monday, November 7, 2016 at 11:22:23 AM UTC-7, Chris Leech wrote: > > Currently the iSCSI transport class synchronises target scanning and > unbinding with a host level mutex. For multi-session hosts (offloading > iSCSI HBAs) connecting to storage arrays that may implement one >

Re: iscsiadm --logoutall=all vs. sessions without match in node database

Hi Christian: Apologies for not replying sooner. Yes, this area of open-iscsi is a bit messy IMHO. What about having open-iscsi update the node database entry when the TPG changes? I'd rather not see iscsid shutting down targets that were not specified. What I would actually like to solve

open-isns: BUG: Discovery Domain membership duplicated when restoring from disc

Apologies. I get how the versioning works now. I hadn't updated the version since you had added that, and I shouldn't have been more careful. It's fixed now. I had never actually pushed the tag for v0.97 yet, so I tagged the latest commit, which reverts the changes to libisns. On Friday, October

open-isns: BUG: Discovery Domain membership duplicated when restoring from disc

I recently found and fixed a bug in open-isns: commit d6004bf7358a3ac3a040b475cdd96fc243b118f8 Author: Lee Duncan Date: Wed Oct 26 13:54:33 2016 -0700 Fix DD member doubling when restoring from DB. Fix issue where a restore of DD members from disc, at

Re: Antw: Re: [RFC 1/3] iscsid: Changes to support the new qedi transport

In this case, I'd like to see you create a "class" of transports that have this feature. Or perhaps it can be a field in the transport structure? I dislike checking against one transport, as Chris also mentioned. On Wednesday, October 19, 2016 at 11:38:08 PM UTC-7, Javali, Nilesh wrote: > > >

Re: version 2.0.874 tagged

Thanks Chris! On Thursday, September 29, 2016 at 11:42:44 AM UTC-7, Chris Leech wrote: > > Hi all, > > There's been a lot of requests for an overdue tagged release with a new > version. I've gone ahead and done that on github, creating version > 2.0.874. I merged a few typo fixes, updated

Re: [PATCHv2] MAINTAINERS: Update open-iscsi maintainers

Christoph Hellwig suggested we do away with the open-iscsi google group (this group) and use linux-scsi. Any thoughts on this? (removed others on the cc list). On Monday, September 26, 2016 at 3:26:36 PM UTC-7, Lee Duncan wrote: > > Chris Leech and I are taking over as open-iscsi maintainers.

Re: How to encrypt password store in nodes dir

There is no option to encrypt the password and storing in that format. On Friday, September 16, 2016 at 5:24:46 PM UTC-7, Vimol Kshetrimayum wrote: > The "iscsiadm -m discoverydb -p -t st -o update -n > discovery.sendtargets.auth.password -v ", command update the > password and store the

Re: When is the next release of open-iscsi?

Yes, this is the correct forum. :) On Thursday, September 15, 2016 at 10:28:55 PM UTC+2, Raghu Murugesan wrote: > > Hi All, > > When in next version of open-iscsi planning to be released? > > Am I posting this question in the right forum? > > if there is a email thread where this topic is

Re: How to disable - Message from syslogd@localhost

You are getting an empty error message? That alone sounds like an issue. Are there any other error messages in your messages file during that same time? What OS and version of open-iscsi are you using? On Friday, September 9, 2016 at 2:27:16 PM UTC-7, Vimol Kshetrimayum wrote: > > I am getting

Re: Segfaults from iscsiuio (iscsiuio/src/unix/nic_nl.c)

On Thursday, July 28, 2016 at 2:16:12 AM UTC-7, Frank Fegert wrote: > > Hello all, > Hi Frank. > > disclaimer: i'm not a programmer, so the following might be utterly > and completely wrong ;-) > > TL;DR: i'm getting segfaults from iscsiuio upon any target login. > Specifically this happens

Chris Leech, please contact me

Apologies for this broadcast email, but ... Chris Leech, please contact me. I sent you email directly, but your SPAM filter may have eaten it. lduncan at suse dot com Thanks. -- Lee -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To

Re: login fail

You really need to supply more information than this. It looks like you don't have your target set up correctly. What type of target are you using (and on what platform)? Can you share it's configuration? On Wednesday, June 22, 2016 at 1:07:14 AM UTC-7, 陳德安 wrote: > > > Hi, > > I have the

Re: sysfs compatibility during logouts and could not read session info errors

I'm guessing that all of these issues have to do with the inherent asynchronous nature of sysfs. The time between an event happening and the sysfs data representing it is not zero, and when the system becomes busy this time delta can be large enough so that assumptions in the code start

open-isns updated to version v0.96

Several updates have been recently to open-isns (many thanks to Christian Seiler), and as a result I've updated the version to v0.96. Available at https://github.com/gonzoleeman/open-isns/releases/tag/v0.96. Note: It is my plan "some time soon" to move open-isns from being a "personal" project

Re: iscsistart takeover vs iface names

ys support it would help. On 05/27/2016 01:13 PM, The Lee-Man wrote: > Mike: I know you've been busy. Any progress on this? Can I help, as I > have the same issue? > > On Thursday, October 8, 2015 at 2:48:30 PM UTC-7, Mike Christie wrote: > > On 10/08/2015 04:10 PM, Ferenc Wagn

Re: iscsistart takeover vs iface names

Mike: I know you've been busy. Any progress on this? Can I help, as I have the same issue? On Thursday, October 8, 2015 at 2:48:30 PM UTC-7, Mike Christie wrote: > > On 10/08/2015 04:10 PM, Ferenc Wagner wrote: > > Mike Christie > writes: > > > >> > On

Re: open-iscsi Ping timeout error.

Hi: It seems like your backend is getting busy and not replying in time when it gets very busy. You can disable the NOOP, or you can lengthen its interval, I believe. If there is a bug, it would be in the kernel target subsystem. Have you tried the target-devel @ vger kernel mailing list? On

Re: "iscsi-initiator-utils" cannot recognize NIC ports

On Thursday, March 17, 2016 at 6:32:34 AM UTC-7, z*@gmail.com wrote: > > Hi! > > I'm in trouble with "iscsi-initiator-utils" and my iscsi target. > I have a Dell T420 server and a Dell SCv2000 storage.The server is > installed with two NICs and "iscsi-initiator-utils" software. > The SCv2000 is

Using all 24-bits of the ISID

When we made the most recent changes to open-iscsi: "make use of all 24 bits of ISID qualifier space" we agreed it would be a "good thing" to modify the kernel to use the "id" routines instead of an atomic int. I created a set of patches and submitted them, and they got comments, but the

Re: [PATCH] Build system: sort object file lists

On Saturday, February 13, 2016 at 3:30:13 PM UTC-8, Mike Christie wrote: > >Lee and Chris, > > > >The patch seems fine to me. It will not break SUSE or Red Hat build > >stuff will it? > I have no objection. I personally prefer Makefile targets to be explicitly listed in the Make file, in

Do you prefer pull requests or patches submitted?

Hi Mike: I see you have taken some pull requests using the github issue/pull-request mechanism. Do you prefer this over the mailing list? I know I kind of prefer it, myself, from both directions, since it makes the workflow a touch easier and faster. What's your preference? -- Lee Duncan --

Re: [PATCH v3 0/2] open-iscsi: Ping support in iscsiuio

On Tuesday, November 17, 2015 at 10:04:44 AM UTC-8, Mike Christie wrote: > > On 09/18/2015 05:38 AM, adheer.cha...@qlogic.com wrote: > > From: Adheer Chandravanshi > > > > Mike, > > > > This is patchset v3 to add ping support in iscsiuio. > > Please review and

Updated open-isns to 0.95

Hello all: I've added a couple of bug fixes to open-isns, and updated the version to 0.95. Here's a summary of the changes: 3af749e0c8e1 Bump version to 0.95 6d794c22c867 isnsd exit(0) when terminated with SIGTERM d1495f23cca5 Be more robust when dealing with the database 2f2aa4ef102f Remove

Re: [PATCH 1/1] add systemd unit for automatic target login

Hi Christian: I apologize: I should have posted it before, but I have a similar service file that we have been using successfully on SUSE now for a while. It's similar to yours but has a few differences. I will post it shortly as a patch, for consideration by the list. On Thursday, September

systemd files for open-iscsi

A recent patch submission by Christian Hesse to supply an "iscsi login service" for systemd spurred me to share the systemd files currently being used by SUSE, since these may help others (like Christian). In the open-iscsi repository, there are only two systemd files: iscsid.socket -- the

<    1   2   3   >