Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Oct 2007 18:41:36 -0700
From:      "pete wright" <nomadlogic@gmail.com>
To:        "Kurt Buff" <kurt.buff@gmail.com>
Cc:        questions@freebsd.org
Subject:   Re: iSCSI and multi-terabyte support?
Message-ID:  <57d710000710101841h6376b1a5v8f070b2a4eae0ff4@mail.gmail.com>
In-Reply-To: <a9f4a3860710101220s5a0c6dd9sc179eca3ba495434@mail.gmail.com>
References:  <a9f4a3860710101220s5a0c6dd9sc179eca3ba495434@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/10/07, Kurt Buff <kurt.buff@gmail.com> wrote:
> At my place of work, we're looking at implementing a SAN, most likely
> with iSCSI, some time next year, and likely about 5-10TBytes.
>
> I was wondering if FreeBSD could provide this on COTS hardware, but my
> googling hasn't been successful.
>
> >From my reading of this list over the past couple of years, it seems
> that both parts of the solution - iSCSI support and large disk support
> - are still problematic, but I'd like to hear more informed opinion,
> as the potential cost savings is quite large.
>
> Anyone have recent-ish experience putting something like this together?
>

IMHO opinion I do not think FreeBSD is there...yet.  ZFS is addressing
many of the enterprise filesystem features that would be needed to
implement something on this scale, and there is the iSCSI target from
NetBSD available in the ports tree.

I think 7-RELEASE is going to be a solid foundation for building
solutions like this - but in the mean time it may be worth considering
OpenSolaris if are considering going the COTS path.

or - you can take a look at a company like Isilon Systems
(http://www.isilon.com/) which builds very scalable filers based on
FreeBSD.  I have beta tested their iSCSI implementation and it does
look good.

HTH
-pete


-- 
~~o0OO0o~~
Pete Wright
www.nycbug.org
NYC's *BSD User Group



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57d710000710101841h6376b1a5v8f070b2a4eae0ff4>