From owner-freebsd-stable@FreeBSD.ORG Mon Jun 14 16:30:22 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3B4C16A4D0 for ; Mon, 14 Jun 2004 16:30:22 +0000 (GMT) Received: from mandarin.fruitsalad.org (pc117.net160.koping.net [81.16.160.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D76F43D60 for ; Mon, 14 Jun 2004 16:30:21 +0000 (GMT) (envelope-from matt@hasta.se) Received: from [192.168.15.68] (helo=fmd) by mandarin.fruitsalad.org with smtp (Exim 4.30; FreeBSD) id 1BZuLM-000NEb-I5; Mon, 14 Jun 2004 18:29:56 +0200 From: "Matt Douhan" To: "Jason Thomson" , Date: Mon, 14 Jun 2004 18:29:54 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <40CDAA9A.1090507@mintel.com> Importance: Normal cc: vkayshap@amcc.com cc: freebsd-stable@freebsd.org Subject: SV: 3ware 7506, FreeBSD 4.x, Maxtor Disks & SMART Problems. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 16:30:23 -0000 >-----Ursprungligt meddelande----- >Fran: owner-freebsd-stable@freebsd.org >[mailto:owner-freebsd-stable@freebsd.org]For Jason Thomson >Skickat: den 14 juni 2004 15:40 >Till: so14k@so14k.com >Kopia: vkayshap@amcc.com; freebsd-stable@freebsd.org >Amne: Re: 3ware 7506, FreeBSD 4.x, Maxtor Disks & SMART Problems. > > >We're not using the ata driver - it's the twe driver - I believe the >SMART events are supposed to be handled by the controller firmware. > >(Which should then report back to the FreeBSD driver when things go wrong). > >Hmmm - I've just done a little more research, and it appears that my >understanding of SMART is flawed - the drive just makes the information >available - and doesn't actively signal the controller. The controller >/ OS / SMART software has to read the SMART status and then act accordingly. > >Maybe it's nothing to do with SMART, and instead it's just something >wrong with Maxtor disks. > >Is anyone else aware of problems with Maxtor disks? Hi We are running 160 GB Maxtors on our 3ware controllers and they all run great under heavy load, we use 3ware ATA for our main 1.2 TB NFS arrays at fruitsalad.org and I have never seen what you are describing even under failure conditions it has worked great until we have downed the server and installed a new HDD, and the rebuild of the array has been done during prodution hours with the standard slowdown cause of the rebuilding. BUt if you are looking to get new controllers I would HIGHLY recommend the 3ware SATA controllers, they rock bigtime and I cannot tell you enough how happy we are with them, and the performance is absolutely outstanding, we are seing similar or better results from our 3ware SATA controllers when we compare them towards our storageworks HG* controllers, the largest servers we have are running 3 3ware SATA controllers, for a total ov 24 HD's and at max speed the I/O is just tremendous. rgds Matt