From owner-freebsd-stable@FreeBSD.ORG Tue Jan 19 12:48:31 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 E8FE0106566B for ; Tue, 19 Jan 2010 12:48:30 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 71BB18FC14 for ; Tue, 19 Jan 2010 12:48:30 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id o0JCmRob016204; Tue, 19 Jan 2010 13:48:28 +0100 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 8D47C24; Tue, 19 Jan 2010 13:48:27 +0100 (CET) Date: Tue, 19 Jan 2010 13:48:27 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Jeremy Chadwick Message-Id: <20100119134827.250abc50.gerrit@pmp.uni-hannover.de> In-Reply-To: <20100119112449.GA73052@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> <20100119095736.GA71824@icarus.home.lan> <20100119110724.ec01a3ed.gerrit@pmp.uni-hannover.de> <20100119112449.GA73052@icarus.home.lan> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.4; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.1.19.123620 Cc: freebsd-stable@freebsd.org 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 12:48:31 -0000 On Tue, 19 Jan 2010 03:24:49 -0800 Jeremy Chadwick wrote about Re: immense delayed write to file system (ZFS and UFS2), performance issues: JC> > JC> If you want a consumer-edition drive that's better tuned for JC> > JC> server work, you should really be looking at the WD Caviar Black JC> > JC> series or their RE/RE2 series. JC> > That's exactly what I did. I have WD-RE2 drives here that show JC> > exactly this problem (RE2/GP)! The model number is WD1000FYPS-01ZKB0. JC> I should have been more specific. WD makes RE-series drives which JC> don't have GP applied to them; those are what I was referring to. Well, when I bought these drives I was not aware of this issue. Buying a drive intended for 24/7 use in RAID configurations is basically the right idea, I think. From what was written about the GP feature back then I could not anticipate such problems. I would have liked to buy the 2TB drives without GP lately, but they have lead times into April here. So I went for the GP model, which now shows the same problem as the 1TB drive... :-( JC> WD1000FYPS - WD RE2-GP, 1TB, 16MB, variable rpm JC> WD2002FYPS - WD RE4-GP, 2TB, 64MB, variable rpm JC> So which drive models above are experiencing a continual increase in JC> SMART attribute 193 (Load Cycle Count)? My guess is that some of the JC> WD Caviar Green models, and possibly all of the RE2-GP and RE4-GP JC> models are experiencing this problem. I can confirm that the two models above show this problem. Furthermore I can confirm that at least in my setup here this drive type works fine: WD5001ABYS I have some of the RE3 drives sitting around here and will probably try them later. Can anyone here report anything about the fixed firmware from ? Does this remedy the problem for the 1TB RE2 drive? JC> I say "some" with regards to WD Caviar Green since I have some which do JC> not appear to exhibit the heads/actuator arm moved into the JC> landing/park zone. I'm at work right now, but when I get home I can JC> verify what models I've used which didn't experience this problem, as JC> well as what the manufacturing date and F/W revisions are. I should JC> note I don't have said Green drives in use (I use WD1001FALS drives JC> now). Thanks for sharing this information. cu Gerrit