From owner-freebsd-stable@FreeBSD.ORG Tue Feb 9 00:35:47 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 21CDB1065670 for ; Tue, 9 Feb 2010 00:35:47 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-iw0-f198.google.com (mail-iw0-f198.google.com [209.85.223.198]) by mx1.freebsd.org (Postfix) with ESMTP id DD7E58FC08 for ; Tue, 9 Feb 2010 00:35:46 +0000 (UTC) Received: by iwn36 with SMTP id 36so1646303iwn.3 for ; Mon, 08 Feb 2010 16:35:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=2iJvvuaDkg2//QSBTIzO+XE9LaoPYG6YOgxiPFko5c0=; b=vliCz+uyxDn3AJ4UnN3XGwJkXyLaqWHY99cKGfjy5qepZ91daNPxbQ1k+/x5AnuaJZ 5bMud/Uwgm8nRo/6tZzrOzeWbKM0n647kJ+hArZ2HjiSSviW3rpeybm0kyEjTknRR4Fr 5XIQtWHTfK9ipHcs+HOuX3vyW+YUtftinY/C8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=bNQQ1qsH4DCO6ntEDtV+yi3FUqm0cWDet4J0UTh8guwUb9eGAzRpfS1EvWrpGgb6y6 1kYnYxECnc7eDcbSzoPjKTpIwtJUW0NnxYe3zWy0XgUwTCKcWy1p23YINNWJeWymET0V 6bv23e8f3drKJkiXrzMjX61qr6o1YyJtRgWuk= MIME-Version: 1.0 Received: by 10.231.85.198 with SMTP id p6mr356432ibl.65.1265675746128; Mon, 08 Feb 2010 16:35:46 -0800 (PST) In-Reply-To: <201002091059.28625.doconnor@gsoft.com.au> References: <201002091059.28625.doconnor@gsoft.com.au> Date: Mon, 8 Feb 2010 16:35:46 -0800 Message-ID: From: Freddie Cash To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: one more load-cycle-count problem 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, 09 Feb 2010 00:35:47 -0000 On Mon, Feb 8, 2010 at 4:29 PM, Daniel O'Connor wrote: > On Tue, 9 Feb 2010, Dan Naumov wrote: > > which essentially solves the problem. Note that going this route will > > probably involve rebuilding your entire array from scratch, because > > applying WDIDLE3 to the disk is likely to very slightly affect disk > > geometry, but just enough for hardware raid or ZFS or whatever to > > bark at you and refuse to continue using the drive in an existing > > pool (the affected disk can become very slightly smaller in > > capacity). Backup data, apply WDIDLE3 to all disks. Recreate the > > pool, restore backups. This will also void your warranty if used on > > the new WD drives, although it will still work just fine. > > Errm.. Why would it change the geometry? > > I have used this tool to change the settings on all my disks and it did > not in any way cause a problem booting later. > > My disks are WDC WD10EADS-00L5B1/01.01A01 > > (1Tb "green" disks) > > I just did this to 8 of the 1.5 TB Caviar Green disks, without ZFS complaining in any way. I did test it on a spare drive before doing it to the 7 live drives. And I did replace them while the server was turned off, just to be safe (and to prevent a resilver from occuring). wdidle3 doesn't actually disable the idle timeout on these drives. Using /d just sets the timeout to 62 minutes. Effectively the same, but don't be surprised when it continues to say "idel 3 available and enabled". :) So far, things are running much smoother. Load_Cycle_Count has stopped increasing (50,000 in 8 weeks on 1 drive). Re-silver throughput for these drives has jumped from 7 MBps to over 40 MBps (90% full pool, so it's slower than normal right now, which is why we're swapping these drive into the pool). -- Freddie Cash fjwcash@gmail.com