From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 10:04:47 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89B2016A420 for ; Fri, 24 Feb 2006 10:04:47 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21E1543D49 for ; Fri, 24 Feb 2006 10:04:46 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FCZoa-0007pY-8U; Fri, 24 Feb 2006 11:04:44 +0100 Message-ID: <43FEDBC4.3010103@datafarm.de> Date: Fri, 24 Feb 2006 11:11:16 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Scott Long References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> <43FEC2D9.7090407@samsco.org> In-Reply-To: <43FEC2D9.7090407@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: eniazi@ossmail.com, freebsd-amd64@freebsd.org, Kris Kennaway Subject: Re: anyone successfully using an icp-vortex / iir controller? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2006 10:04:47 -0000 Hello, Scott Long schrieb: > Kris Kennaway wrote: >> On Fri, Feb 24, 2006 at 02:13:56AM -0400, Marc G. Fournier wrote: >>> I run an IIR controller on one of our servers just fine ... 4GB of >>> RAM, FreeBSD 4.x ... haven't tried 6.x on it yet ... >> It's known to be broken on any system with >4GB of RAM. > I'll strengthen that statement and say that it is completely, 100% > unusable with 4GB of RAM or more. You are guaranteed to get data > corruption on the second I/O that you send. Fixing this requires > re-writing much of the driver, unfortunately. If this is true - and I think so, I wasted a lot of time on it already - so why isn't there a little piece of documentation speaking out a warning. We've been happily using a large number of GDT controllers under FreeBSD for years after we have had a couple of bad experiences with other brands. One of those, a mylex 160lp was just tested to be unfunctional with 6.1b2 (8GB RAM), too. Are there any *good* SCSI RAID controllers out there that are known to be working in server setups (amd64, SMP, >4GB RAM)? When thinking it over, I guess I have to be grateful that over many years I never experienced s/th that made me question the "The Power To Serve" slogan. What I really feel unhappy about right now is that there was no information available so I could take appropriate measures in order to avoid the current situation (at least none that I could find). Well, what's the plan regarding the iir driver now? I would suspect that letting folks rendering their servers unfunctional by upgrading memory is not really a good strategy. The manpage lists two authors/maintainers, I emailed both early this week. Achim Leubner will be back from vacation the 27th. So maybe he can contribute s/th constructive. Kind regards, vt