On 06/23/2009 11:11 AM, Stefan wrote:
Am Montag 22 Juni 2009 13:51:17 schrieb Stefan:
Hello all,
sorry, its half solved. Its now running on ubuntu jaunty but not on debian
lenny.
I did what did on the ubuntu machine:
aptitude install open-iscsi
untar new package
make user
Click Here to Watch This Video
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to
Click Here to Watch This Video
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to
Hi ,
First of all, please correct me if you can prove that i need more education !!
My question is, is IP-SAN just a dream ? how far iSCSI reached that
goal ? Whats features that iSCSI have, which force to call it a SAN ?
I wish to argue that its just a client-server protocol that access
Click Here to Watch This Video
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to
Hi all,
during heavy I/O the iSCSI initiator starts spitting out receive timeouts and
connection failures, even though the connection itself is not faulty.
I managed to trace it down to the way open-iscsi treats SCSI commands.
During queuecommand we're just taking the scmd, add it to the
During heavy I/O we might hit a receive timeout as the
xmitworker is still busy sending PDUs. Even as we strictly
speaking didn't receive a reply during the receive timeout,
we didn't actually gave the target a chance to reply as
we're constantly hitting it with requests.
So it's better to
During heavy I/O the scsi cmd might be stuck in the cmdqueue
and hasn't even been sent at the time the command timeout
strikes. So we should be resetting the command timer here
and not aborting the command.
Signed-off-by: Hannes Reinecke h...@suse.de
---
drivers/scsi/libiscsi.c |8
Click Here to Watch This Video
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to
There seems to be a lot of spam coming through the open-iscsi mail list.
Any chance of getting something done about this?
--
Alvin Starr || voice: (416)585-9971x690
Interlink Connectivity|| fax: (416)585-9974
al...@iplink.net ||
Am Mittwoch 24 Juni 2009 11:47:55 schrieb Boaz Harrosh:
This is very old what Kernel is this ?
okay I copiled new kernel: 2.6.30
uname -a
Linux willy 2.6.30 #1 SMP Wed Jun 24 15:18:23 CEST 2009 i686 GNU/Linux
doing:
/etc/init.d/open-iscsi stop
Disconnecting iSCSI targets:.
Stopping iSCSI
On 06/24/2009 06:41 AM, dushy wrote:
Hey guys,
Iam usign linux-iscsi currently on a centos 4.5 box (kernel
2.6.9-67.0.22.ELsmp). The target is a Hitachi WMS 100 with three
logical drives. Iam trying to find teh best upgrade path to open-isci
for the below setup.
* So to upgrade to
On 06/24/2009 12:31 PM, Alvin Starr wrote:
There seems to be a lot of spam coming through the open-iscsi mail list.
Any chance of getting something done about this?
Right now only members can post and if a non member posts I have to
manually allow it. I guess that had worked ok for a
On 06/24/2009 09:40 AM, Hannes Reinecke wrote:
During heavy I/O the scsi cmd might be stuck in the cmdqueue
and hasn't even been sent at the time the command timeout
strikes. So we should be resetting the command timer here
and not aborting the command.
Signed-off-by: Hannes
On 06/24/2009 03:52 PM, Mike Christie wrote:
On 06/24/2009 09:40 AM, Hannes Reinecke wrote:
During heavy I/O the scsi cmd might be stuck in the cmdqueue
and hasn't even been sent at the time the command timeout
strikes. So we should be resetting the command timer here
and not aborting the
On 06/24/2009 09:40 AM, Hannes Reinecke wrote:
During heavy I/O we might hit a receive timeout as the
xmitworker is still busy sending PDUs. Even as we strictly
speaking didn't receive a reply during the receive timeout,
we didn't actually gave the target a chance to reply as
we're constantly
Mike,
Many thanks for seeking clarification on it. Hopefully it will be a favorable
result :)
Jon.
Sent from my iPhone
On 9 Jun 2009, at 17:20, Mike Christie micha...@cs.wisc.edu wrote:
dougee wrote:
Coming in late on this one will there likely be any movement on this,
would be really
-Original Message-
From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
On Behalf Of Mike Christie
Sent: Thursday, June 11, 2009 11:11 PM
To: open-iscsi
Subject: RFC: do we need a new list for kernel patches
Hey,
It seems like we have a lot of members on
On Sat, 2009-06-13 at 14:29 -0700, k...@chelsio.com wrote:
[PATCH 1/2 2.6.30-rc] cxgb3i -- add a refcnt to track ddp usage
From: Karen Xie k...@chelsio.com
The iscsi ddp functionality could be used by multiple iscsi entities,
add a refcnt to keep track of it, so we would not release it
On Tue, 2009-06-23 at 09:34 -0700, Mike Christie wrote:
Michael Chan wrote:
On Mon, 2009-06-22 at 16:51 -0700, Benjamin Li wrote:
On Mon, 2009-06-22 at 05:59 -0700, Rakesh Ranjan wrote:
4. Get rid of ISCSI_NL_GRP_UIP netlink message and use
ISCSI_NL_GRP_ISCSID instead. Move the
FUJITA Tomonori wrote:
On Wed, 24 Jun 2009 14:46:23 -0500
Mike Christie micha...@cs.wisc.edu wrote:
On 06/24/2009 12:31 PM, Alvin Starr wrote:
There seems to be a lot of spam coming through the open-iscsi mail list.
Any chance of getting something done about this?
Right now only members
-Original Message-
From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
On Behalf Of shyam_i...@dell.com
Sent: Thursday, June 11, 2009 11:39 PM
To: open-iscsi@googlegroups.com
Subject: RE: do we need a new list for kernel patches
-Original Message-
shyam_i...@dell.com wrote:
-Original Message-
From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
On Behalf Of shyam_i...@dell.com
Sent: Thursday, June 11, 2009 11:39 PM
To: open-iscsi@googlegroups.com
Subject: RE: do we need a new list for kernel patches
On Wednesday 24 June 2009, FUJITA Tomonori wrote:
On Wed, 24 Jun 2009 14:46:23 -0500
Mike Christie micha...@cs.wisc.edu wrote:
On 06/24/2009 12:31 PM, Alvin Starr wrote:
There seems to be a lot of spam coming through the open-iscsi mail list.
Any chance of getting something
Establish a connection to an MD3000i (use CHAP and Rev. CHAP)
- Disconnect the iSCSI session
iscsiadm -m node -p ip_addr -T iqn -u
- Reconnect the iSCSI session
iscsiadm -m node -p ip_addr -T iqn -l
-Fails because iscsid gets killed
25 matches
Mail list logo
