From owner-freebsd-scsi Mon Mar 1 2:45:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20]) by hub.freebsd.org (Postfix) with SMTP id 6B9B91533A for ; Mon, 1 Mar 1999 02:45:19 -0800 (PST) (envelope-from sinbin.demos.su!bag@kremvax.demos.su) Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.5.31] with ESMTP id NAA03507; Mon, 1 Mar 1999 13:39:07 +0300 Received: by sinbin.demos.su id NAA11096; (8.6.12/D) Mon, 1 Mar 1999 13:38:37 +0300 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199903011038.NAA11096@sinbin.demos.su> Subject: Re: RAID saga In-Reply-To: from spork at "Feb 26, 1999 2:43:23 pm" To: spork@super-g.com (spork) Date: Mon, 1 Mar 1999 13:38:37 +0300 (MSK) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2652 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > We've just about given up on CMD as a SCSI-SCSI controller, so now we're > looking around to see what else is out there. So far I've heard good > things about two others: > > Mylex DAC960-S(X/U)I (Does anyone see what the differences in these two > controllers are? The specs seem the same) > See www.mylex.com - this is intel 960-based > > Infortrend ??A Lots of models there, not real detailed info. See > www.infortrend.com.tw for more info. This one > is 486 based. we use several IFT3102 without problems, it can work with fbsd cam as is or with path to scsi_da.c 127,135d126 < * Infortrend RAID controller doesn't like the < * synchronize cache command. < */ < {T_DIRECT, SIP_MEDIA_FIXED, "IFT", "3102", "01*"}, < /*quirks*/ DA_Q_NO_SYNC_CACHE < < }, < { < /* we dont check new firmware that support growing, firmware in our controllers is 1-1.5 years old > > Anyone have any experience with either of these? I know one of the Mylex > models is being used for wcarchive, I assume under CAM. It appears each > of these controllers support growing the array, which is something not > possible with the CMD. Of course the most important factor is whether any > quirks show up under FreeBSD (in this case a 2.2.7 SNAP with CAM patches). > > Our issue with the CMD is that under load we get timeouts unless I disable > disconnection in the Adaptec card (2940UW) bios. Checked cabling, > termination, swapped cables, etc... > > > CMD has been incredibly lame in dealing with this as well, the ol' "I > never heard of that OS" line after we buy the product specifically because > it "works with any OS". At this point they are telling us to go to our > reseller for support, which is kind of silly as the problem seems beyond > tech support and more like something that needs some developer attention. > If anyone else is running the CRD-5440 with two host channels and two > drive channels, please contact me so we can compare notes. The drive side > seems OK, the only thing the cmd logs is the reset that the scsi layer > sends to wack it back into shape... > > > Thanks, > > Charles > > --- > Charles Sprickman > spork@super-g.com > --- > "...there's no idea that's so good you can't > ruin it with a few well-placed idiots." > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message