gileno wrote:
Hello people...
I´m a newbie on iscsi stuff, I´m using the fedora core 7 distro that
already comes with the iscsi daemon. I configured a target (on a fedora
core 7 too) and connected with a Windows XP, and it seems all ok!
But when try to connect to it with a fedora box as an
Erez Zilber wrote:
Mike,
I'm still investigating the performance problems in open-iscsi over iSER, and
I think that I see the cause of the problem:
I've added an outstanding commands counter. It's incremented when
iscsi_queuecommand is called and decremented when iscsi_complete_command
Mike Christie wrote:
Andreas Bergstrøm wrote:
On 8. jan.. 2008, at 10:29, Mike Christie wrote:
I am not sure if that will work for you because I am not sure what the
ubuntu scripts do. The shutdown -h workaround is for a RHEL/Fedora
scripts issue.
What are the last messages printed out
Mike Christie wrote:
Hey Broadcom guys and iscsi list,
I put up all my changes to the bnx2i driver in the bnx2i branches of the
open-iscsi git tree and linux-2.6-iscsi.
It hooks bnx2i into the iscsi layers like how iser and iscsi_tcp is,
except that it allocates a scsi_host per net
Anil Veerabhadrappa wrote:
On Thu, 2008-01-10 at 14:41 -0600, Mike Christie wrote:
Anil Veerabhadrappa wrote:
On Thu, 2008-01-10 at 07:22 -0600, Mike Christie wrote:
Hey Broadcom guys and iscsi list,
I put up all my changes to the bnx2i driver in the bnx2i branches of the
open-iscsi git
Wilton wrote:
Hi all,
I've been running a CentOS server connected to a Promise VTrak m500i
via open-iscsi quite successfully for over a year now. A few days ago
the performance plummeted on the drive and I'm seeing the following
messages in my log file:
Jan 14 09:06:13 flax kernel:
Wilton wrote:
OK I changed the Ping_Timeout on that Discovery Address to 20.
When I asked iscsi to reload (by typing service iscsid reload) it
rescanned the devices but now I'm getting the following lines in my
logfile...
Jan 14 13:28:54 flax kernel: iscsi-sfnet: Could not find session
-by: Mike Christie [EMAIL PROTECTED]
One thing you will also want to do is hook iser in the session creation
command that sets this at creation time. In userspace westore the queue
depths we want to use for specific targets, and then have the session's
host cmd_per_lun use that that value
Doron Shoham wrote:
While stopping open-iscsi, the initd script removes
the modules by running 'modprobe -r'. The retval of
modprobe must be tested.
Signed-off-by: Doron Shoham [EMAIL PROTECTED]
---
etc/initd/initd.debian |9 -
etc/initd/initd.redhat | 13 -
Miguel Gonzalez Castaños wrote:
Erez Zilber escribió:
Hi,
I'm running some performance tests with open-iscsi (iops throughput).
With open-iscsi over TCP, I see very low numbers:
* iops: READ - 2, WRITE - 13000
* throughput: READ - 185, WRITE - 185
In open-iscsi.org, I see
[EMAIL PROTECTED] wrote:
Hi. I'm getting the following whenever I write a substantial amount:
Feb 1 09:48:04 fraunhofer kernel: [62669.987811] connection1:0:
iscsi: detected conn error (1012)
Feb 1 09:48:04 fraunhofer kernel: [62670.233507] sd 6:0:0:0: [sdc]
Result:
Hey,
When the iscsi scripts run they assume the network is ready to go. This
may not be the case for lots of different reasons, and to get around
this we have the login retry param in iscsi.conf. What we really want is
the login retry param, combined with the ability to know that the
network
Doron Shoham wrote:
Doron Shoham wrote:
Hi,
I want to check open-iscsi with kernel 2.6.25-rc2,
what version of open-iscsi should I use?
I meant, which version of open-iscsi user space should I use.
For userspace tools you can use
Micha? Miros?aw wrote:
On Wed, Feb 20, 2008 at 12:03:21PM -0600, Mike Christie wrote:
Micha? Miros?aw wrote:
I found a deadlock in iSCSI while tearing down connection of an
actively used device (as one of dm-multipath paths). Connection is
made between Linux 2.6.24.2 (from kernel.org
Sorry for the delay. When I did the last release, I put it out a little
early and then did several refinements and some bug fixes really quickly
after posting it. This is why we went from 865.0 to 865.X so quickly. In
the hope of not creating as much confusion, I am going to do some
release
Andrew Moise wrote:
forwarded 466954 open-iscsi@googlegroups.com
thanks
Hi all.
I'm having a bit of trouble with open-iscsi on kernel 2.6.22.18 from
Debian backports; I seem to be able to log in to my storage array, but
when I log out, iscsiadm (and later modprobe) seem to hang
Sparqz wrote:
On Feb 29, 9:41 am, Mike Christie [EMAIL PROTECTED] wrote:
Sparqz wrote:
On Feb 28, 12:09 pm, Sparqz [EMAIL PROTECTED] wrote:
I can repeat the problem with bonnie on SuSE 10 SP1
I can also repeat the problem with HP's open-
iscsi-2.0.707-0.25b.src.rpm (supplied from
Sparqz wrote:
The default run for bonnie++ on a server with 32GB of memory takes
forever...! But it looks like the performance is up on the production
server (Still SLES10 SP1) with the semi-stable release from the open-
iscsi website.
Version 1.03 --Sequential Output--
Andrew Moise wrote:
On 2/28/08, Mike Christie [EMAIL PROTECTED] wrote:
Andrew Moise wrote:
Okay, excellent. If you want a more proper doc snippet (with exact
commands and whatnot), say the word and I'll write one up.
Yeah, please do. I know very little about debian (just that apt
Sparqz wrote:
On Feb 28, 8:46 pm, Mike Christie [EMAIL PROTECTED] wrote:
Sparqz wrote:
Hi,
There appears to be a bug in test/regression.sh
It only applies when using the -f option:
test x$1 = x fatal target name parameter error
test x$2 = x fatal ipnumber parameter error
test x$3
Victor Engle wrote:
Just curious, is any work planned or in progress to implement SNIA'a
IMA for managing iSCSI initiators on linux?
I started cleaning up the iterator functions in idbm.c and
iscsi_sysfs.c, but got busy trying to close up what we have for the rc I
just posted.
The TODO:
Erik Bussink wrote:
On Mon, 2008-02-25 at 12:41 -0800, Sparqz wrote:
Hi Erik,
Why have you hijacked my thread? Please don't... start a new thread/
topic.
Whoa, you need to calm down. For one, I had not read any of the post for
the iSCSI errors SLES10 post that where here recently, and
Mike Christie wrote:
Sparqz wrote:
On Feb 29, 9:41 am, Mike Christie [EMAIL PROTECTED] wrote:
Sparqz wrote:
On Feb 28, 12:09 pm, Sparqz [EMAIL PROTECTED] wrote:
I can repeat the problem with bonnie on SuSE 10 SP1
I can also repeat the problem with HP's open-
iscsi-2.0.707-0.25b.src.rpm
on the SNIA API. It will not give us everything we
want for some of the wierd iface stuff we do, so maybe we could have the
lower level API which is similar to what is in iscsiadm.c. Then I can
build the SNIA API over that for other usrs that needed it.
Thanks,
Gerry
Mike
Lauri Lubi wrote:
Hello again,
Sorry for not getting back earlier - I had some high-prio personal things to
take care of.
Last week OpenSuse released open-iscsi 2.0.866-15.2 via their update tool,
but this did not solve the problem.
We are not worried about the userspace package. We
Doron Shoham wrote:
Divide node parameters into 3 categories:
a. Immutable - properties that are not allowed to change at all.
b. Immediate - properties that are allowed to change and take effect
immediately.
c. Deferred - properties that are allowed to change but will take effect
CymBa wrote:
Mar 25 01:34:52 srv1 iscsid: connect failed (113)
Mar 25 01:34:56 srv1 iscsid: connect failed (113)
Mar 25 01:34:56 srv1 kernel: Loading iSCSI transport class v2.0-724.
Mar 25 01:34:56 srv1 kernel: iscsi: registered transport (tcp)
Mar 25 01:34:56 srv1 kernel: iscsi: registered
[EMAIL PROTECTED] wrote:
i installed open-iscsi-2.0-868-rc1 in kernel 2.6.21-2950.fc8xen.
and getting the following error::
[EMAIL PROTECTED] init.d]# ./open-iscsi start
Starting iSCSI initiator service: FATAL: Error inserting ib_iser
Doron Shoham wrote:
Divide node parameters into 3 categories:
a. Immutable - properties that are not allowed to change at all.
b. Immediate - properties that are allowed to change and take effect
immediately.
c. Deferred - properties that are allowed to change but will take effect
Doron Shoham wrote:
Mike Christie wrote:
Doron Shoham wrote:
Divide node parameters into 3 categories:
a. Immutable - properties that are not allowed to change at all.
b. Immediate - properties that are allowed to change and take effect
immediately.
c. Deferred - properties
Pasi Kärkkäinen wrote:
On Wed, Mar 12, 2008 at 10:59:26AM +0200, Pasi Kärkkäinen wrote:
On Tue, Mar 11, 2008 at 05:07:46PM -0400, [EMAIL PROTECTED] wrote:
- Update iSCSI
- Added iSNS client: isns-utils
- Added iSCSI Boot Firmware Table (iBFT) support to boot
Bart Van Assche wrote:
Hello,
Has anyone here experience with letting the open-iscsi initiator
connect to an iSCSI target system on which many (hundreds) of target
have been configured ? From a certain number of targets on the
open-iscsi initiator starts complaining that the buffer size is
[EMAIL PROTECTED] wrote:
On Wed, Mar 26, 2008 at 05:20:32PM +0530, [EMAIL PROTECTED] wrote:
i installed open-iscsi-2.0-868-rc1 in kernel 2.6.21-2950.fc8xen.
Did you also install the new kernel modules that came with
2.0-868-rc1 ?
how to install them?
If you do a make install
Rudy Gevaert wrote:
Andrew Moise wrote:
On Mon, Mar 31, 2008 at 10:01 AM, Rudy Gevaert [EMAIL PROTECTED] wrote:
I'm stopping with init script of debian:
jlyj43j:~# /etc/init.d/open-iscsi stop
Disconnecting iSCSI targets:.
Stopping iSCSI initiator service:.
Iscsid is still running:
Rudy Gevaert wrote:
Konrad Rzeszutek wrote:
On Mon, Mar 31, 2008 at 02:42:24PM +0200, Rudy Gevaert wrote:
Hello,
I have installed 2.0.865 on a Debian Etch system.
I can use my targets withyout any problem.
However when I stop open-iscsi my devices (/dev/sdb e.g.) aren't removed
from the
Mike Christie wrote:
We can make it so the transport type is not changable while logged in.
We do that today already in the git tree.
Oh yeah, we were probably both right :)
iface.transport_name is checked, but node.transport_name is not, so like
we said before we need to update
Rudy Gevaert wrote:
Hi Mike,
Mike Christie wrote:
Rudy Gevaert wrote:
Hi Mike
Mike Christie wrote:
What is the version of your kernel?
2.6.18-6-xen-amd64
Make sure you are using the kernel modules from the open-iscsi.org
release, start up iscsi, then run:
I'm not sure I
Bart Van Assche wrote:
On Mon, Mar 31, 2008 at 9:14 PM, Mike Christie [EMAIL PROTECTED] wrote:
Bart Van Assche wrote:
Has anyone here experience with letting the open-iscsi initiator
connect to an iSCSI target system on which many (hundreds) of target
have been configured ? From
Jesper Krogh wrote:
This morning my filesystems were turned read-only with these messages
in the log.. ? Is that a network outtake? Or?
Jesper
[375615.617710] iscsi: cmd 0x28 is not queued (8)
[375615.619492] sd 5:0:0:0: [sdf] Result: hostbyte=DID_NO_CONNECT
Doron Shoham wrote:
Mike Christie wrote:
Doron Shoham wrote:
Mike Christie wrote:
Doron Shoham wrote:
Divide node parameters into 3 categories:
a. Immutable - properties that are not allowed to change at all.
b. Immediate - properties that are allowed to change and take effect
Rudy Gevaert wrote:
Hello,
So it seems that running 2.6.18 (stock Debian kernel) with open-iscsi
2.0.730-1etch1 doesn't give me any problems regarding the start and
stopping. (Although one iscsid process is still running when I stop it
with the init script.)
That is a bug in iscsid
Erez Zilber wrote:
Mike,
We're trying to solve a problem, but first the motivation: a user may
want to stop the InfiniBand modules (/etc/init.d/openibd stop) while
open-iscsi is running. In order to do that, we must remove ib_iser.
Now, the question: is it ok to modprobe -r ib_iser (or
Erez Zilber wrote:
Mike Christie wrote:
Erez Zilber wrote:
Mike,
We're trying to solve a problem, but first the motivation: a user may
want to stop the InfiniBand modules (/etc/init.d/openibd stop) while
open-iscsi is running. In order to do that, we must remove ib_iser.
Now
Doron Shoham wrote:
The following patches contain several bug fixes and add-ons
to the iscsi_discovery script.
Thanks for the patches. Merged them all, so they will be in the next rc.
You should do a git pull or rebase your tree before sending patches, so
you know you are diffing against
Doron Shoham wrote:
Add -f flag (force) to iscsiadm when changing node parameters
that are defined as ATTR_DEFERRED.
When using this flag, changing of ATTR_DEFERRED parameter
while in active session can take place.
The change itself will take effect only in the next session.
A warning
fischerman wrote:
I have installed the open-iscsi and I can see my sessions just fine.
I can log into the sessions just fine.
When I run iscsiadm -m session -P 1 i get:
You need to run
iscsiadm -m session -P 3
to see the disks that were found through each session.
Like others have
Hannes Reinecke wrote:
For boot from iSCSI we need to the fwparam_ibft program
to setup the network correctly. This patch moves the
fwparam_ibft files into a library and adds a new program
fwparam_ibft to print out the network parameter.
Why do you need a new program to print out the
Hannes Reinecke wrote:
Hi Mike,
these have been all patches I had in my queue. So now you
can go ahead and do the release :-)
Thanks Hannes.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
Mike Christie wrote:
Hannes Reinecke wrote:
For boot from iSCSI we need to the fwparam_ibft program
to setup the network correctly. This patch moves the
fwparam_ibft files into a library and adds a new program
fwparam_ibft to print out the network parameter.
Why do you need a new program
Hannes Reinecke wrote:
These are some updates to the SUSE init scripts, plus a new
boot.open-iscsi script for SUSE. The latter is used for
root on iscsi, to start iscsid as early as possible to
avoid deadlocks on the root fs.
Merged. bf7425f6539ffb63cca7b61ce8ef949ec79ac28a
This one had
Bart Van Assche wrote:
Hello,
An iSCSI initiator logout in a Xen dom0 triggered a kernel bug. Is
this an open-iscsi issue or something I should post in a Xen mailing
list ?
$cat /etc/issue.net
Ubuntu 7.10
$ uname -a
Linux qsan002 2.6.22-14-xen #1 SMP Tue Feb 12 04:26:15 UTC 2008
v i n c e wrote:
Hello all,
I finally configured a proof-of-concept iSCSI target to export a root-
FS and have an iSCSI initiator PXE boot into the root image ... all
done in CentOS 5.1 for both target and root.
I have been trying to read the docs and mans for the target as well as
v i n c e wrote:
Hello all,
I added edited my /etc/ietd.conf in my target and restarted - now it
has a different target-lun exported; I try to stop and start my iscsi-
initiator, and it is unable to read the NEW target, but seems like
there is some log it is reading and persistently wants
Erez Zilber wrote:
The problem with calling it from iscsi_if_transport_lookup is that
iscsi_if_transport_lookup calls iscsi_trans_error that calls
iscsi_if_transport_lookup again. This sounds strange...
Uggh, right the priv-daemon pid. I will fix that up later when we fix
the daemon pid
노성후 wrote:
Hello,
While I was mounting a target,
I unbinded what I was mounting and I found the mounted file system turn
into readonly mode about 2 minutes later.
[EMAIL PROTECTED] ~]# tgtadm --lld iscsi --op bind --mode target --tid 2 -I
10.1.1.0/24
[EMAIL PROTECTED]
노성후 wrote:
Apr 16 20:49:47 OSS1 kernel: iser: iscsi_iser_ib_conn_lookup:no conn exists
for eph
This eph looks weird. Erez, have you seen this before?
Apr 16 20:49:49 OSS1 iscsid: connection2:0 is operational after recovery (2
attempts)
Apr 16 20:49:53 OSS1
Konrad Rzeszutek wrote:
With the 869-rc4 and a SLES10 SP2 kernel with the 869-rc4 drivers compiled
out of
the tree I can get:
iscsid[27598]: segfault at 2b4327f11000 rip 0040981b rsp
7fff826f61a0 error 4
when I run the 'iscsiadm -k 0' command.
I haven't dug deep in
Konrad Rzeszutek wrote:
Firstly, I haven't dug in this yet but this is more of a call:
have-you-seen-this-too?
This is probably on the list 20 times :)
When I reboot the machine without logging off from iSCSI targets I can
hang the reboot sequence. This is with 869-rc4 userspace, SLES 10
Simone Morellato wrote:
When I have 255 targets configured on my iscsi target, openiscsi can only
discover 160 of them.
Windows initiator can discover all of them.
Have you seen this problem before?
I am using open-iscsi-2.0-865.15.tar.gz
Try
David Lee Lambert wrote:
I'm trying to get open-iscsi to work on some systems that run kernel
2.6.16. I'm using the open-iscsi-2.0-865.15 release. I can build
the source, but the iscsi_tcp module won't load.
On a production system where we only have very short windows for
maintenance,
Erez Zilber wrote:
Mike Christie wrote:
Erez Zilber wrote:
This new thread summarizes and continues a discussion that we (Mike, Or
and myself) had outside the list. This is what we have so far:
* Having a parent device: commit
62786b526687db54c6dc22a1786d6df8b03da3f3
Boaz Harrosh wrote:
On Mon, Apr 28 2008 at 20:15 +0300, Mike Christie [EMAIL PROTECTED] wrote:
ptashek wrote:
I have looked around the web, but haven't found a similar issue which
suggests that this may be a simple config issue, which I have just not
found yet. However, if anyone has any
Santi Saez wrote:
Dear Srs,
I'm getting this error when trying to connect to a Infortrend A16E-
G2130-4 storage vía iSCSI.
Apr 29 10:24:40 vz-10 kernel: scsi1 : iSCSI Initiator over TCP/IP
Apr 29 10:24:41 vz-10 kernel: Vendor: IFT Model: A16E-
G2130-4 Rev: 361F
Apr 29
Santi Saez wrote:
El 29/04/2008, a las 18:23, Mike Christie escribió:
The problem appears to be related to udevd-event? The system is
running CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, and iscsi-
initiator-utils-6.2.0.865-0.8.el5.
The target does not like our nops. If you set
aspasia wrote:
Hello again,
I followed the recommendation to create the record, so I added the
following in my initrd:
iscsiadm -m node -T iqn.2008-04.com.mycompany:storage.ubuntu8_x86_test
-p 192.168.17.3:3260 -o new
iscsiadm -m node -T
Pete Wyckoff wrote:
[EMAIL PROTECTED] wrote on Mon, 28 Apr 2008 11:20 -0500:
Erez Zilber wrote:
Mike Christie wrote:
Erez Zilber wrote:
This new thread summarizes and continues a discussion that we (Mike, Or
and myself) had outside the list. This is what we have so far:
* Having
Padmanabhan wrote:
Hello All,
I have a case where both initiator and target are configured with IPv4
and IPv6 address. The target listens ob both sockets.
When i login to the target without mentioning the portal , it logins
and creates two sessions for the same target.
Questions
1.How
Erez Zilber wrote:
Erez Zilber wrote:
Mike Christie wrote:
Erez Zilber wrote:
Fix indentation and remove trailing spaces.
Signed-off-by: Erez Zilber [EMAIL PROTECTED]
Mike? Are you ok with this patch?
It is already broken. Did you run
Pete Wyckoff wrote:
I need this on top of git head to be able to get status
from iscsi using 2.6.25-rc1. You'll probably want
to go looking for host in both sysfs paths, to handle
old and new kernels. Here's an example of how it works
in a recent one.
Others testing recent kernels may
info-dtnet wrote:
Hi,
while looking around in google, if found a logfile
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467390, where the
iscsi LUN cache is enabled, read+write:
Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Write cache:
enabled, read
cache: enabled, supports DPO
swejis wrote:
Hello everyone. I'm not very experienced with iscsi, so please excuse
me if asking stupid questions.
I'm evaluation opensuse 11 (Beta1) for my servers and have found some
worrying errors in the log. The following error quite frequently shows
up.
May 5 21:15:05 manjula
swejis wrote:
Hello everyone. I'm not very experienced with iscsi, so please excuse
me if asking stupid questions.
I'm evaluation opensuse 11 (Beta1) for my servers and have found some
worrying errors in the log. The following error quite frequently shows
up.
May 5 21:15:05 manjula
Padmanabhan wrote:
Hello Mike,
Here again, let me try to explain the problem
Initiator Target
10.1.1.210.1.1.1
2001::2 2001::1
node.startup=automatic
you can set the node.startup value for each portal on the target.
When the
swejis wrote:
I have now changed the following, correct ?
## node.conn[0].timeo.noop_out_interval = 5
node.conn[0].timeo.noop_out_interval = 0
node.conn[1].timeo.noop_out_interval = 0
# node.conn[0].timeo.noop_out_timeout = 5
node.conn[0].timeo.noop_out_timeout = 0
Maysara wrote:
Hello,
I'm usinsg iscsiadm from iscsi-initiator-utils version
6.2.0.865-0.8.el5, and i also tried opne-iscsi 2.0.730-1etch1in a line
like this:
iscsiadm -m discovery -t sendtargets -p iscsi-storage| cut -f2 -d\ |
xargs -l -I '{}' iscsiadm -m node -T {} -p iscsi-storage -l
a s p a s i a wrote:
Hi Mike,
In a prior version, seems like the iscsi.conf file has the values of:
node.conn[0].timeo.login_timeout = 15
# To specify the time to wait for logout to complete, edit the line.
# The value is in seconds and the default is 15 seconds.
Bjoern Metzdorf wrote:
Hello everybody,
for 2 hours now I receive LOTs of errors in my syslog:
May 8 19:43:03 xenhost2 last message repeated 2 times
May 8 19:43:03 xenhost2 iscsid: connection9:0 is operational after
recovery (1 attempts)
May 8 19:43:14 xenhost2 iscsid: Nop-out
aspasia wrote:
Hello all,
After seeing the announcement on the regression of the current
release, I looked more closely into my /var/log/messages and noticed
that once in a while my iscsi connections get the following:
May 8 08:55:48 r05s23 kernel: connection1:0: iscsi: detected conn
Konrad Rzeszutek wrote:
2). If is a EqualLogic, send a AsyncMsg telling the initiator that the
block
device is going to be off-line.
What is this? I do not think we handle this. Is it a verndor specific
async iscsi event?
Yes. To be exact attached is a TCP dump, look for seq no
a s p a s i a wrote:
Are you using 869 and do you also see the nop out timeout messages or do
you just see these connection error messages?
just the above connections errors...
865 version:
[EMAIL PROTECTED] ~]# iscsiadm -V
iscsiadm version 2.0-865
[EMAIL PROTECTED] ~]# iscsistart
Fred Blaise wrote:
Hello all,
I am using open-e DSS storage (http://open-e.com). I usually have 1 lun
per target, but for backup purposes, I take snapshots for each lun. This
snapshot then becomes a part of the parent LUN target, so that TargetX
has LunA and LunS (snapshot).
When I
MAKHU wrote:
Conclusion: What is moral of the story i got is that in our target-
initiator pair,Persistent connection is not possible.After target/
Initiator iscsi-target daemon restart(code given below),connection
is lost causing disks to be unusable.
What you should have taken from the
[EMAIL PROTECTED] wrote:
Hi,
What are the disadvantages of increasing the replacement_timeout to
large values?
If you use multipath you want this value short. If you do not use
multipath you want this longer. See the README on open-iscsi.org for how
to tune. The non-multipath case and
Padmanabhan wrote:
Hello
So if you do
iscsiadm -m node -T target -p ip:port -o update -n node.startup -v manual
for just one portal, then restart the system that portal will not get auto
logged into. The other portal on that taget will still get auto logged
into. Does that make sense?
HIMANSHU wrote:
I) How to increase replacement_timeout on initiator?
echo 82400 /sys/block/sdh/device/timeout
or
Yeah, the timeout above is not the replacement_timeout so writing to
that sysfs file will not help.
After discovery,nodes sendtargets are created.In nodes,there is
Albert Pauw wrote:
I am using the current open-iscsi git version (as of May 9th) on Fedora 8
(2.6.24.5-85.fc8 kernel) with the Wasabi target (version 4.01). It used to
take a fraction of a second to login. Since I haven't worked on it for a few
months while away I started again, and now it
Or Gerlitz wrote:
Hi Erez, Mike,
testing with 2.6.26-rc2 I get the below nice oops with iser but not with tcp
:(
attached is my compressed .config, also I am using some derivative of 2.0-865,
so I will move tomorrow to -869 but I wonder if you have any insight for
this trace. The two
HIMANSHU wrote:
Hi..
It is probably not the problem of replacement_timer.
Did you try what I asked? Did you do the same timing in the tests?
In your log you had this:
session13: iscsi: session recovery timed out after 120 secs
When this is is printed out it means the replacment timer
An Oneironaut wrote:
I gave this a try but now when I set the timeout for a really long
period and disconnect my iSCSI device to test it, after about 2
minutes I get this:
28May 13 13:15:48 localhost iscsid: Kernel reported iSCSI connection
4:0 error (1011) state (3)
31May 13 13:15:48
Stefan de Konink wrote:
Hi,
In the libvirt project we have stumbled upon a problem related to name
changes of sys-fs. Looking at the Makefiles of open-iscsi and its
usertools, I wonder if we can make it more easy for other projects using
open-iscsi.
I propose to move the shared
Stefan de Konink wrote:
What was the reason for adding the block device name to the block symlink
if this symlink already provides this name?
iscsi has not control over the block device naming and symlinks. You
would want to ask lkml.
It probably breaks everything that uses this block path
Shrey wrote:
Hi all,
Further update on this topic:
Thanks once again :) - If I manage to find/assert it, I will surely
post back.
I tried to do an experiment to confirm the maximum number of available
targets and LUNs with an initiator. I did:
On the target machine:
1. I created
Shrey wrote:
Hi Mike,
Thanks for you reply. Please find my reply inline.
On May 19, 11:04 pm, Mike Christie [EMAIL PROTECTED] wrote:
Shrey wrote:
Dear All,
I started using/studying open-iscsi recently. I was wondering if there
is any hard-coded limit to number of targets devices
HIMANSHU wrote:
Yeah..I am using IET.
I was getting session recovery timed out after 120 secs when it was
120.
Now as it is 86400,I never observed after 86400sec. that
session recovery timed out after 86400 secs.
Otherwise is it NORMAL behavior of IET that the connection is lost of
hg wrote:
I go this message wihle compiling 869.2
I didn't had problem with previous kernel
version 865.4 865.8 865.12 865.15 have the same result
Any ideas ?
I think you need the attached patch. I have not merged it because it
ends up breaking other builds. We need someone with some
:
commit 0f1e48cfc07ac5031bf9a4a60487fcb46a46b791
Author: Mike Christie [EMAIL PROTECTED]
Date: Sun Apr 20 22:15:32 2008 -0500
Do not allow iface setting to be changed in node mode.
This temporarily breaks iscsi_discovery and probably other apps
for distros
Mike Christie wrote:
Pete Wyckoff wrote:
I confess to having lost the plot on the iface rearrangements. I'm
trying to mount up a remote iser target using 2.6.26-rc3 and
open-iscsi git HEAD userspace plus hacks to read the new sysfs
layout.
The old style, before login, was to modify
Pete Wyckoff wrote:
Are you talking about Doron's parameter categorization work?
I'm having a hard time finding that again. Any suggestions
for a quick fix to play with iser in 2.6.26-rc3?
Oh yeah the userspace tools from 869.2 should work with 2.6.26-rc3.
Pete Wyckoff wrote:
This is important, thanks. Userspace git head fails with stock
2.6.26-rc3 due to the introduction of
ISCSI_UEVENT_CREATE_BOUND_SESSION in pass ep to session
creation. Guess I should pull in your git kernel tree too.
Oh fudge. Yeah, it looks like I only fixed the
Mike Christie wrote:
[in another mail]
Oh yeah the userspace tools from 869.2 should work with
2.6.26-rc3.
This is important, thanks. Userspace git head fails with stock
2.6.26-rc3 due to the introduction of
ISCSI_UEVENT_CREATE_BOUND_SESSION in pass ep to session
creation. Guess I should
1 - 100 of 2076 matches
Mail list logo