From owner-freebsd-stable@FreeBSD.ORG Tue Jan 19 09:57:38 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9BFA10656A5 for ; Tue, 19 Jan 2010 09:57:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3B18FC0A for ; Tue, 19 Jan 2010 09:57:38 +0000 (UTC) Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta01.emeryville.ca.mail.comcast.net with comcast id XMxT1d0010QkzPwA1MxeFm; Tue, 19 Jan 2010 09:57:38 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta02.emeryville.ca.mail.comcast.net with comcast id XMxe1d0013S48mS8NMxeMR; Tue, 19 Jan 2010 09:57:38 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E0CD71E3033; Tue, 19 Jan 2010 01:57:36 -0800 (PST) Date: Tue, 19 Jan 2010 01:57:36 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20100119095736.GA71824@icarus.home.lan> References: <4B54C100.9080906@mail.zedat.fu-berlin.de> <4B54C5EE.5070305@pp.dyndns.biz> <201001191250.23625.doconnor@gsoft.com.au> <7346c5c61001181841j3653a7c3m32bc033c8c146a92@mail.gmail.com> <4B557B5A.8040902@pp.dyndns.biz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4B557B5A.8040902@pp.dyndns.biz> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: immense delayed write to file system (ZFS and UFS2), performance issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2010 09:57:38 -0000 On Tue, Jan 19, 2010 at 10:28:58AM +0100, Morgan Wesström wrote: > Garrett Moore wrote: > > The drives being discussed in my related thread (regarding poor performance) > > are all WD Green drives. I have used wdidle3 to set all of my drive timeouts > > to 5 minutes. I'll see what sort of difference this makes for performance. > > > > Even if it makes no difference to performance, thank you for pointing it out > > -- my drives have less than 2,000 hours on them and were all over 90,000 > > load cycles due to this moronic factory setting. Since changing the timeout, > > they haven't parked (which is what I would expect). > > You're welcome. I just feel as bad for you as for everyone else who has > bought these obviously Windoze optimized harddrives. Unfortunately > neither wdidle3 nor an updated firmware is available or functioning on > the latest models in the Green series. At least that's what I've read > from other people having this issue. WD only claims they don't support > Linux and they probably have never heard of FreeBSD. No offence intended by this statement, but: the Green drives are specifically intended for workstations. I don't believe in the whole "segregation of drive model" thing, but the fact of the matter is, the Green drives are variable-RPM and have numerous firmware-level features which intend for them to be used in workstation environments -- that means not constant I/O or heavy workload. Windows has nothing to do with this. If you want a consumer-edition drive that's better tuned for server work, you should really be looking at the WD Caviar Black series or their RE/RE2 series. I have both the Green and Black drives, and I've done my share of benchmarking. Sustained transfer rates on the Black models exceed that of the Greens by almost 20-25MB/sec. Average seek times are slightly lower, and I/O concurrency is handled much better. The Black drives also have a feature called TLER[1], which can be toggled using a utility from Western Digital. Those using these drives in a RAID or ZFS array will be very interested in disabling this feature to ensure quick timeouts from the drive in the case of I/O errors. Other manufacturers have the same feature, just called something else (ex. Samsung's is called CCTL). Now, admittedly WD doesn't give this utility out any more (which is silly), and some people have reported that recent-day (circa mid-to-late 2009) Black drives refuse to let you toggle TLER. The latter claim is absurd -- I purchased 4 Black drives (2 with manufacturing dates of October 2009, and 2 with September 2009) and all of them let me toggle TLER without any problem. Keep in mind you your SATA controller has to be set to non-AHCI mode (sometimes called "Enhanced mode") or Compatibility mode (e.g. IDE emulation) for the utility work. If you have qualms/concerns/issues with Western Digital drives or their mentality behind their drives, simply don't buy them. Really. People often ask me (and others) "what brand of hard disk is good?" and I always tell them the same thing: "there's no correct answer. Everyone has their own experience with different vendors, models, etc." [1]: http://en.wikipedia.org/wiki/Time-Limited_Error_Recovery > If anyone successfully has fixed their WD15EADS drives this way I'd be > interested in hearing from you. One of my drives has 216,000 load cycles > accumulated over 8 months. That's one every 2nd minute... and I was hit > by the Seagate 7200.11 fiasco too. Running on Samsungs now :-) Aren't Samsung's drives known for firmware bugs/quirks? The documentation associated with smartmontools discusses this quite a bit. This is one reason why I stay away from them. Fujitsu is another vendor I want absolutely nothing to do with (very high failure rates in addition to bad sectors with their SCSI-3 disks at my workplace). -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |