From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 29 03:45:50 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83DD016A4CE for ; Wed, 29 Sep 2004 03:45:50 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9D8143D1F for ; Wed, 29 Sep 2004 03:45:49 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [127.0.0.1] (i-99.forrie.net. [192.168.1.99]) by forrie.com with ESMTP id i8T3jgRm065790 for ; Tue, 28 Sep 2004 23:45:43 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <415A3060.1060402@forrie.com> Date: Tue, 28 Sep 2004 23:47:44 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 0.8 (Windows/20040928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean Subject: Re: Status of iSCSI X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 03:45:50 -0000 [Scott, sorry about the bounced mail - it was an old IP block I had, it's fixed now.] I'm working on a project that requires a scalable mail store, which is poised to support 25k users initially, but scale to 100's of thousands of users. The budget won't provide for a SAN right now; iSCSI is a little new, but unfortunately it's not supported in FreeBSD at this time. I've been looking into the storage market areas specifically of Linux and/vs FreeBSD. A Linux/NAS/iSCSI model and that of a FreeBSD/NAS/NFS model -- not sure we want to do direct storage at this time, if we did, we'd need to plan how that purchased hardware would fit into a larger plan. NAS has the advantage of being independent; some have their own OS and most have redundancies in place. I'm not sure if it's possible to dual-attach Linux or FreeBSD boxes to a FC fabric; a while ago, that wasn't possible. The front-end servers will be split up into scalable groups - ie: some servers doing SpamAssassin, some antivirus, some MTA-in and MTA-out, etc. The common denomenator, and driving factor of this design, is the backend mail store. I'd like to explore what (realistic) options FreeBSD may have here - as I dread the thought of Linux-anything in this scenario. All input/feedback welcomed. Forrest There was an implementation done by Lucent last year for 4.x, but it has a sticky license and is probably out of date. I and several others see iSCSI as something that really needs to get done, but the 3-4 months of development time is more than can be done on evenings and weekends. I would also want to do it 'right' and implement new infrastructure in CAM to accompany it rather than making it monolithic like the Lucent implementation. What kind of project do you need it for, and what kind of resources do you have right now? Scott Forrest Aldrich wrote: > I read the April 2004 report (on freebsd.org); presuming that's > up-to-date, it may be a while before we have iSCSI support in FreeBSD. > I wanted to verify here, etc. > > I'm involved in a project that will require something of that nature. > > > Thanks, > Forrest >