From: Ming Zhang (blackmagic02881_at_gmail.com)
Date: Wed Jan 17 2007 - 14:46:26 CET
From: Ming Zhang <blackmagic02881@gmail.com> Date: Wed, 17 Jan 2007 08:46:26 -0500 Message-Id: <1169041586.2788.4.camel@localhost.localdomain> Subject: RE: [suse-sles-e] iSCSI on SLES10 - open-iscsi vs cisco iscsi
On Wed, 2007-01-17 at 06:11 +0000, Chris Puttick wrote:
> We moved to SLES 10 for a Samba project because linux-iscsi (Cisco
> project) was never patched in SLES 9 to support greater than 2TB
> volumes. Open-iscsi has been fine,
i remember this is one line change.
if any of you have open-iscsi problem, go and ask on open-iscsi mailing
list, should get faster answer than here.
> although the Samba config/support company has been "problematic".
>
> Chris
>
> -----Original Message-----
> From: Alexei_Roudnev [mailto:Alexei_Roudnev@exigengroup.com]
> Sent: Wed 17/01/2007 04:34
> To: blackmagic02881@gmail.com
> Cc: suse-sles-e@suse.com; Mike Christie
> Subject: Re: [suse-sles-e] iSCSI on SLES10 - open-iscsi vs cisco iscsi
>
> I will test it on SLES10 next week with NetApp filers (multipath,
> multiport,
> and so on).
>
>
> ----- Original Message -----
> From: "Ming Zhang" <blackmagic02881@gmail.com>
> To: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com>
> Cc: <suse-sles-e@suse.com>; "Mike Christie" <michaelc@cs.wisc.edu>
> Sent: Tuesday, January 16, 2007 7:08 PM
> Subject: Re: [suse-sles-e] iSCSI on SLES10 - open-iscsi vs cisco iscsi
>
>
> > On Tue, 2007-01-16 at 18:55 -0800, Alexei_Roudnev wrote:
> > > > it is not that easy i feel. for example, u can send your ini
> code to
> IOL
> > > > lab to do interoperability test, you need to test so many
> possibilities.
> > > > all these need many resources. back to one word, money.
> > > >
> > >
> > > This is true. On the other hand, most of the problems was not
> because of
> > > interoperaqbility problems, but because of some kinds of race
> condition
> /
> > > heavy load problems, and this kind of thigs are easier to reveal
> in
> tests
> > > (many techniques do exists, such as artifically slow servers with
> multi
> cpu,
> > > running long performance tests all the time, and so so on...).
> >
> > these needs resource as well. ;)
> >
> > i agree with what u said, it could be done better.
> >
> > >
> > > But I am more interested in open-iscsi quality - old Cisco iSCSI
> initiator
> > > was well tested and was widely used; how new open-iscsi driver
> have been
> > > used in real world? Sometimes, _merge_ means that developers was
> able to
> > > merge primary code from the old system into the utilities from the
> new
> > > system (and then such merge is safe); in other cases, when kernel
> was
> > > changed sugnificantly, there is a high risk of bugs.
> >
> > u can go open-iscsi list for more details. my experience with it is
> ok.
> > newer features are kept added in, which lead to new bugs or
> regression
> > from time to time. I suspect Mike has enough time to do regression
> test
> > for each revision.
> >
> > @Mike, I add you into this discussion, compare with stale
> cisco-iscsi
> > ini, how stable open-iscsi is? Thanks.
> >
> >
> > >
> > >
> > >
> > --
> > http://blackmagic02881.wordpress.com/
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
> For additional commands, e-mail: suse-sles-e-help@suse.com
>
>
>
>
>
>
>
>
>
> This message has been scanned for viruses by BlackSpider MailControl -
> www.blackspider.com
-- http://blackmagic02881.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Wed Jan 17 2007 - 16:50:26 CET