On Sat, Aug 1, 2009 at 6:31 AM, Mike Christiemicha...@cs.wisc.edu wrote:
Mike Christie wrote:
Mike Christie wrote:
Mike Christie wrote:
Mike Christie wrote:
On 07/31/2009 07:43 AM, Erez Zilber wrote:
I thought that this patch just reduces the timeout from 15 to 3. Does
it also fix the 3
Hi All,
I would like to knw if i can present same volume to two hosts?
I am using Stonefly Voyager as SAN and the host would be Xen.
Thanks in Advance
Nick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hi All,
i would like to know if i can assign the same volume to hosts?
I am using Stonefly Voyager as SAN and the host is Xen Server.
Thanks in Advance
Nick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
On Monday 03 August 2009, Stefani Seibold wrote:
This is a proposal of a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to many
constrains. Only 13 files in the current 2.6.30 used it. FIFO's are
like list are a very basic thing
On 08/03/2009 02:31 AM, Erez Zilber wrote:
On Sat, Aug 1, 2009 at 6:31 AM, Mike Christiemicha...@cs.wisc.edu wrote:
Mike Christie wrote:
Mike Christie wrote:
Mike Christie wrote:
Mike Christie wrote:
On 07/31/2009 07:43 AM, Erez Zilber wrote:
I thought that this patch just reduces the
On 08/03/2009 09:42 AM, Arnd Bergmann wrote:
On Monday 03 August 2009, Stefani Seibold wrote:
This is a proposal of a new generic kernel FIFO implementation.
The current kernel fifo API is not very widely used, because it has to many
constrains. Only 13 files in the current 2.6.30 used it.
On 07/30/2009 10:37 AM, shyam_i...@dell.com wrote:
1) With the first patch we should be able to do the following -
#iscsiadm -m discovery -t isns -l
And all the target portals will get logged in.
It also adds iface support to be able to login through multiple
initiator portals.
The iSNS
On 07/30/2009 01:08 AM, Ulrich Windl wrote:
On 29 Jul 2009 at 21:50, Anil Veerabhadrappa wrote:
+bnx2i_ep-ep_iscsi_cid = (u16) -1;
As a matter of style: Wouldn't it be more logical to write (u16) ~0 instead?
Casting a negative value to unsigned seems strange to me.
Is there a MAX_U16
On 08/03/2009 12:37 PM, Erez Zilber wrote:
On Mon, Aug 3, 2009 at 7:27 PM, Mike Christiemicha...@cs.wisc.edu wrote:
On 08/03/2009 02:31 AM, Erez Zilber wrote:
On Sat, Aug 1, 2009 at 6:31 AM, Mike Christiemicha...@cs.wisc.edu
wrote:
Mike Christie wrote:
Mike Christie wrote:
Mike
-Original Message-
From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
On Behalf Of Mike Christie
Sent: Monday, August 03, 2009 10:46 PM
To: open-iscsi@googlegroups.com
Subject: Re: [PATCH 0/2] iSNS enhancements
On 07/30/2009 10:37 AM, shyam_i...@dell.com
Hello Nick,
While an iSCSI SAN will not have any problem allowing multiple hosts to
connect to the same volume, what it doesn't do is protect you from the
resultant corruption. Each host will believe it owns that volume
exclusively. Writes from one host won't be seen by the other host. They
Hello,
I'm not sure what your question really is. Yes, you can have 6x GbE
interfaces on different subnets and run iSCSI over them. What target are you
using? Typically, your iSCSI SAN is on one subnet. It avoids the need to
do IP routing. Which adds latency and can reduce performance.
12 matches
Mail list logo