Narender:
I work for SUSE. Please file a SUE bug on this, and please cc me - my work
email is lduncan at novell dot com.
I have a similar setup, i.e. booted SLES 11 SP2 using iSCSI, but I have
seen no such errors. When you file the bug, please include log messages and
a list of initiator HBA
s/SUE bug/SUSE bug/
On Wednesday, June 27, 2012 3:26:25 PM UTC-7, The Lee-Man wrote:
Narender:
I work for SUSE. Please file a SUE bug on this, and please cc me - my work
email is lduncan at novell dot com.
I have a similar setup, i.e. booted SLES 11 SP2 using iSCSI, but I have
seen
Mark:
Did Mike answer your questions? If not, I'd be glad to help on the SUSE
part.
On Wednesday, February 20, 2013 10:37:57 AM UTC-8, Blaxton, Mark H wrote:
Question: I’ve configure the iscsi iniator on my suse 11 system and its
connected to my target but lsscis doesn’t show any new
Hi Mike:
I am testing the new version of open-iscsi on SLES 11 SP3 Beta.
This is the update I did to support IPv6, with your help.
I am validating the IPv6 functionality, and I seem to be experiencing
double-discovery of my IPv6 target.
My setup: I have an iscsitarget soft target. The IPv6
On Thursday, May 9, 2013 5:03:44 AM UTC-7, Adheer Chandravanshi wrote:
-Original Message-
From: Mike Christie [mailto:mich...@cs.wisc.edu javascript:]
Sent: Thursday, May 09, 2013 7:31 AM
To: open-...@googlegroups.com javascript:
Cc: The Lee-Man; Vikas Chaudhary; Lalit
Apologies for Subject formatting errors ... I need to wean myself off of OS
X ...
On Tuesday, May 21, 2013 2:15:00 PM UTC-7, The Lee-Man wrote:
I mentioned this before, but I didn't have a good solution at the time.
In usr/iscsi_util.c, nice() is called like this:
if (nice(-10
On Tuesday, December 11, 2012 3:26:46 PM UTC-8, Chris Leech wrote:
...
Thanks, this got me going in the right direction. These unit files
seems to be working much better for me, with the startup and shutdown
ordering between iscsi, iscsid, and remote-fs mounts sorted out. I'm
not sure
On Monday, September 23, 2013 10:33:36 AM UTC-7, The Lee-Man wrote:
...
I just wanted to post a thank you for all of this work, as I was
attempting to do some of it myself and making slow progress.
...
Wanted to mention I also had to port back a couple of systemd-support
patches
On Friday, September 27, 2013 3:41:18 AM UTC-7, Per Jessen wrote:
Per Jessen wrote:
The Lee-Man wrote:
I am trying to get open-iscsi version 2.0-873-suse working on
openSUSE.
In my case open-iscsi-based boot is not working and has not been
working for a while.
Just
Hi Mike:
I have a configuration where discovery is taking a long time because one of
the interfaces is disconnected.
Since it is not possible to reliably detect when an interface is connected,
I thought the best way to speed up discovery in such cases would be for
discovery to take place in
On Thursday, November 14, 2013 11:09:37 PM UTC-8, Uli wrote:
mich...@cs.wisc.edu javascript: schrieb am 15.11.2013 um 00:53 in
Nachricht
1384473233-4711-1-git-send-email-micha...@cs.wisc.edu javascript::
From: Yufei Ren yufe...@stonybrook.edu javascript:
Got can not connect to
On Thursday, January 9, 2014 10:38:15 AM UTC-8, Mike Christie wrote:
...
There are some questions:
1. Why stgt target don't has this issue? Does it support report_opcode
because it has a embeded controller lun0? Or it just returns INVALID in
response?
Don't know. Will let someone
Thanks Mike. Yes, it appears you're right, iscsi_offload is something Hannes
created. Should I add it someplace in your tree for possible use by others?
On Thursday, September 4, 2014 4:18:31 PM UTC-7, Mike Christie wrote:
On 09/04/2014 04:10 PM, Lee Duncan wrote:
I'm attaching 3 patches for
On Tuesday, November 11, 2014 6:11:51 PM UTC-8, Mike Christie wrote:
On 10/30/2014 08:16 PM, The Lee-Man wrote:
0003-fwparam_ibft-Check-iBFT-target-and-NIC-flags.patch
This was the patch that you had problems with last time, and
for good reason, as it checks iBFT flags
On Friday, November 14, 2014 9:12:41 AM UTC-8, Mike Christie wrote:
On Nov 13, 2014, at 5:56 PM, The Lee-Man leeman...@gmail.com
javascript: wrote:
On Tuesday, November 11, 2014 8:25:56 PM UTC-8, Mike Christie wrote:
On 10/30/2014 08:16 PM, The Lee-Man wrote:
0002-Represent-DHCP-origin
Hi Mike:
Here are the updated patches, based on your feedback:
0001-Code-cleanup-no-functional-changes.patch
0002-Represent-DHCP-origin-as-an-enum-not-a-string.patch
0003-fwparam_ibft-Check-iBFT-target-and-NIC-flags.patch
0004-Allow-modifications-for-iface.gateway-and-iface.subn.patch
Changes
On Sunday, November 16, 2014 11:11:59 PM UTC-8, Uli wrote:
Hi!
I don't have the full context: Why is a IQNPREFIX necessary at all? It
mean that there are incomplete IQNs somewhere?
It is used to created the SourceName if not specified. This name is
(usually) an IQN identifying the
On Sunday, November 16, 2014 11:16:17 PM UTC-8, Uli wrote:
Lee Duncan leeman...@gmail.com javascript: schrieb am 15.11.2014
um 02:15 in
Nachricht 1416014130-25502-9-git-send-email-leeman.dun...@gmail.com
javascript::
From: Hannes Reinecke ha...@suse.de javascript:
[...]
diff --git
On Tuesday, November 18, 2014 10:55:31 PM UTC-8, Uli wrote:
Lee Duncan leeman...@gmail.com javascript: schrieb am 18.11.2014
um 22:35 in
Nachricht 1416346536-18198-1-git-seemail-###-duncan@ javascript:###:
The following patch fixes a problem where the CPU becomes compute bound
when
On Wednesday, November 19, 2014 11:23:10 PM UTC-8, Uli wrote:
The Lee-Man leeman...@gmail.com javascript: schrieb am 19.11.2014
um 19:35 in
Nachricht 16860f30-b55c-4106-a4e1-d7badfc36...@googlegroups.com
javascript::
On Tuesday, November 18, 2014 10:55:31 PM UTC-8, Uli wrote
On Friday, November 21, 2014 12:37:59 AM UTC-8, Uli wrote:
The Lee-Man leeman...@gmail.com javascript: schrieb am 20.11.2014
um 18:07 in
Nachricht dc3f5a91-d2a1-41e1-bc93-e5d9f44ba...@googlegroups.com
javascript::
On Wednesday, November 19, 2014 11:23:10 PM UTC-8, Uli wrote
On Friday, November 21, 2014 8:06:55 PM UTC-8, Mike Christie wrote:
On Nov 18, 2014, at 3:35 PM, Lee Duncan leeman...@gmail.com javascript:
wrote:
The following patch fixes a problem where the CPU becomes compute bound
when rediscovering targets, when there are hundreds of sessions.
Okay, I spent most the day yesterday playing with the
code in question, i.e. the open-iscsi code that rescans
the session list looking for the current session.
In particular, I was looking at update_sessions().
One thing I noticed is that this code only gets executed
if
On Monday, November 24, 2014 11:42:31 PM UTC-8, Uli wrote:
The Lee-Man leeman...@gmail.com javascript: schrieb am 24.11.2014
um 18:04 in
Nachricht dfb5172f-05e8-4027-867e-8e2b1969f...@googlegroups.com
javascript::
[...]
Here's the problem: the submitted patch makes this
particular
On Tuesday, November 25, 2014 9:42:59 AM UTC-8, Mike Christie wrote:
On 11/24/2014 11:04 AM, The Lee-Man wrote:
Okay, I spent most the day yesterday playing with the
code in question, i.e. the open-iscsi code that rescans
the session list looking for the current session
On Tuesday, November 25, 2014 2:00:22 PM UTC-8, Mike Christie wrote:
On 11/25/2014 12:49 PM, The Lee-Man wrote:
On Tuesday, November 25, 2014 9:42:59 AM UTC-8, Mike Christie wrote:
On 11/24/2014 11:04 AM, The Lee-Man wrote:
Okay, I spent most the day yesterday playing
Hi Mike:
I am dealing with a problem in Equallogic, and it looks like the Current
Portal and Persistent Portal are different.
As this is something I haven't seen before, I was hoping you could explain
what it is.
I see in the README:
...
Current Portal: portal currently logged into
On Wednesday, November 26, 2014 1:11:46 PM UTC-8, Mike Christie wrote:
On 11/25/2014 05:15 PM, The Lee-Man wrote:
On Tuesday, November 25, 2014 2:00:22 PM UTC-8, Mike Christie wrote:
On 11/25/2014 12:49 PM, The Lee-Man wrote:
On Tuesday, November 25, 2014 9:42:59 AM UTC-8
On Wednesday, November 26, 2014 1:31:30 PM UTC-8, Mike Christie wrote:
On 11/25/2014 06:58 PM, The Lee-Man wrote:
Hi Mike:
I am dealing with a problem in Equallogic, and it looks like the Current
Portal and Persistent Portal are different.
As this is something I haven't seen
On Tuesday, December 2, 2014 6:59:02 PM UTC-8, pilla...@gmail.com wrote:
hi
I am new to iscsi ,have some questions in learning,quite appreciate for
your help and time
This really isn't the place to ask about iSCSI targets, by the way. This
list is for discussion of the open-iscsi iSCSI
On Friday, December 5, 2014 11:42:12 AM UTC-8, Andy Grover wrote:
On 12/04/2014 01:13 PM, The Lee-Man wrote:
On Tuesday, December 2, 2014 6:59:02 PM UTC-8, pilla...@gmail.com
wrote:
1 \ both lio-utils and tgt are pure user space program? Both of them
are using the kernel iscsi
I'm not familiar with CentOS. Does you iscsi-utils package have any systemd
unit files, i.e. is the version of open-iscsi you are using integrated with
systemd?
On Tuesday, December 9, 2014 7:28:52 AM UTC-8, awidde...@hotmail.com wrote:
Setup iSCSI on CentOS7. Mounted a iSCSI disk and am
It seems clear that the I/O error is because iscsi is stopped before the
device is unmounted:
On Tuesday, December 9, 2014 7:28:52 AM UTC-8, awidde...@hotmail.com wrote:
Setup iSCSI on CentOS7. Mounted a iSCSI disk and am running a small MySQL
instance on the disk. The iSCSI disk and MySQL
Okay, I'm no systemd expert, though I play one at work. :)
You might try adding this to your mysql unit file:
[Unit]
Description=MySQL Server
-After=nss-lookup.target network.target remote-fs.target time-sync.target
-Wants=nss-lookup.target network.target remote-fs.target time-sync.target
Hi Mike:
I have started working more with iscsiuio.
I have discovered what I consider a bug in an error message printed during
normal operation of iscsiadm that makes it seem like something bad happened.
As you know, when performing discovery via the bnx2i transport and the
iscsiuio daemon,
On Friday, December 12, 2014 12:26:00 PM UTC-8, Mike Christie wrote:
On 12/12/2014 12:30 PM, Mike Christie wrote:
On 12/11/2014 01:53 PM, The Lee-Man wrote:
Hi Mike:
I have started working more with iscsiuio.
I have discovered what I consider a bug in an error message printed
If corporations can be people I guess google groups can too!
On Monday, December 15, 2014 2:30:54 PM UTC-8, Greg KH wrote:
Hi,
I'm trying to keep track of the different companies that people are
working for, or if people are just doing this as a hobby, or being paid
as a consultant for
Thanks, Chris, for tracking down the systemd problem and reporting it.
--
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
Hi Mike:
Just a heads up that stopping the open-iscsi iscsid daemon using systemd
doesn't seem to be working correctly, at least not on SUSE SLE 12.
When I have one or more sessions present, and their startup value is set to
manual, when I try to stop the iscsid service, I get:
#
On Friday, January 30, 2015 at 2:09:54 PM UTC-8, The Lee-Man wrote:
Hi Mike:
Just a heads up that stopping the open-iscsi iscsid daemon using systemd
doesn't seem to be working correctly, at least not on SUSE SLE 12.
When I have one or more sessions present, and their startup value is set
Hi Mike:
I verified this patch works. Feel free to add a Tested-by:.
By works, I mean that it eliminated the retry that I was seeing when
connecting the first time to the iscsiuio daemon.
On Tuesday, March 10, 2015 at 8:00:54 AM UTC-7, Mike Christie wrote:
On 03/09/2015 08:54 PM, Lee Duncan
Oops. I almost forgot. The patch did not apply cleanly because of a recent
update you did. Please make sure I modified it correctly (attached).
On Monday, March 16, 2015 at 11:56:48 AM UTC-7, The Lee-Man wrote:
Hi Mike:
I verified this patch works. Feel free to add a Tested-by:.
By works, I
On Monday, June 29, 2015 at 1:38:04 PM UTC-7, Christian Iversen wrote:
Hello Open-iSCSI
(please CC as I'm not a regular on the list)
Please join the list if you are going to submit patches.
I've been working with iSCSI lately, and thought I could help with a few
patches.
Here's a
On Thursday, July 2, 2015 at 2:17:12 AM UTC-7, loke...@gmail.com wrote:
I would like to know about the fail over mechanisms used by iSNS for ISCSI
implementation. The RFC states that Note that it is possible to create
multiple physical iSNS servers to form a single logical iSNS server
Note: I fixed this in open-isns in github already, but I thought you might
want to fix
it here in the meantime. It's up to you.
On Friday, August 21, 2015 at 6:01:34 PM UTC-7, The Lee-Man wrote:
The switch statement was falling through after
the server name was set, into the version code. So
:3264
for p in $portals; do
iscsiadm -m discovery -t st -I iser -p $p -l
done
On Mon, Aug 10, 2015 at 10:57 PM, The Lee-Man leeman...@gmail.com
javascript: wrote:
On Tuesday, August 4, 2015 at 8:36:14 AM UTC-7, Mike Christie wrote:
On 08/04/2015 10:33 AM, Mike Christie
Just an update for the list:
I have replied privately to Roi that I have some issue with this patch, but
a bigger issue with fixing the discoveryd problem this way, i.e.
single-threading it.
If I can get a copy of the finer-grained locking code from him I will test
it out. He says that it has
On Wednesday, July 29, 2015 at 9:07:30 PM UTC-7, Mike Christie wrote:
On 7/14/15, 4:01 PM, leeman...@gmail.com javascript: wrote:
From: Lee Duncanldu...@suse.com javascript:
This set of patches tells open-iscsi to use the system-resident
open-isns files instead of the ones in
On Tuesday, August 4, 2015 at 8:36:14 AM UTC-7, Mike Christie wrote:
On 08/04/2015 10:33 AM, Mike Christie wrote:
On 08/04/2015 09:45 AM, Roi Dayan wrote:
On Friday, July 24, 2015 at 3:38:00 AM UTC+3, The Lee-Man wrote:
On Wednesday, July 22, 2015 at 1:43:59 PM UTC-7, Mike
On Tuesday, July 21, 2015 at 9:29:19 PM UTC-7, Mike Christie wrote:
On 07/21/2015 05:47 PM, leeman...@gmail.com javascript: wrote:
From: Lee Duncan ldu...@suse.com javascript:
This patch allows iser transport to be used for the discovery
daemon. Otherwise, iscsid core dumps when
On Wednesday, July 22, 2015 at 1:43:59 PM UTC-7, Mike Christie wrote:
On 07/22/2015 10:24 AM, The Lee-Man wrote:
On Tuesday, July 21, 2015 at 9:29:19 PM UTC-7, Mike Christie wrote:
On 07/21/2015 05:47 PM, leeman...@gmail.com javascript: wrote:
From: Lee Duncan ldu
On Sunday, July 12, 2015 at 9:35:07 PM UTC-7, Adheer Chandravanshi wrote:
-Original Message-
From: open-...@googlegroups.com javascript: [mailto:
open-...@googlegroups.com javascript:]
On Behalf Of Ulrich Windl
Sent: Friday, July 10, 2015 11:32 AM
Cc: open-iscsi
If there are no objections I will commit these changes. Then I'll submit a
set of patches for open-iscsi to use this package instead of it's internal
copy of it.
Sound good Mike?
On Monday, July 13, 2015 at 2:57:45 PM UTC-7, The Lee-Man wrote:
From: Lee Duncan ldun...@suse.com
This group
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
On Friday, July 10, 2015 at 6:12:34 AM UTC-7, lokesharora wrote:
Hi
Thanks for the response. the above mentioned text is a part of the
description given by RFC. Please find below the other part.
So the RFC states the below mentioned text for fail over. And apart from
the method of
Hi All:
I recently patched open-isns. It had an issue getting it's
own IP address reliably.
It was using getsockname(), but the length it was passing
it was not initialized, as it is supposed to be.
On x86 this seemed to be working anyway, though no
telling what memory might be corrupted. But
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
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
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
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
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
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
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
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
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
--
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
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
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
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
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
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
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
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.
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
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
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
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
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
>
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?
>
>
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
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:
>
>
>
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&
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
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
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
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
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,
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:
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?
>>>
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
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
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
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
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
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
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
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
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
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
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
1 - 100 of 255 matches
Mail list logo