From owner-freebsd-stable@FreeBSD.ORG Mon Feb 8 13:43:50 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 627811065670 for ; Mon, 8 Feb 2010 13:43:50 +0000 (UTC) (envelope-from dan.naumov@gmail.com) Received: from mail-yw0-f191.google.com (mail-yw0-f191.google.com [209.85.211.191]) by mx1.freebsd.org (Postfix) with ESMTP id 2528B8FC08 for ; Mon, 8 Feb 2010 13:43:49 +0000 (UTC) Received: by ywh29 with SMTP id 29so403121ywh.13 for ; Mon, 08 Feb 2010 05:43:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=LzMI+O+nmZh9MOdF6/OZb2xfkq3EjSIuUChm0nrzjSw=; b=gp6Qfw5YLE8biX6q6CbEmHbIUC5zB1Sl1ZR+KiGAT3T4tp+zVlcM9nws1Bhoamt10l JhMR+ZHJAmvPvI1sYz2aUa6zEDdOw6DbA4WB5AREFalAttVoZkMaoborE1T3eGK9CdAQ ThOgKGSr7m3PKdwBDr4QhIRQF7L47QO9m9BqM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Qaqv0JtlrJCGCf1gpfvI43Mpixj9VfXvZx7yyjtpDBp5t8giDJHu4EreUfGoymCYma nIyipwBenNGzC9jO5IjsWRoxniiiI652DgbE0VDn8wNuq32TI84oIrqYZBy8o8TK2jqT g3d0zfqf+8mDFAyGM0uPUjubrcwwjS/A0vbYs= MIME-Version: 1.0 Received: by 10.101.128.5 with SMTP id f5mr3374035ann.125.1265636626938; Mon, 08 Feb 2010 05:43:46 -0800 (PST) Date: Mon, 8 Feb 2010 15:43:46 +0200 Message-ID: From: Dan Naumov To: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 08 Feb 2010 13:43:50 -0000 >Any further ideas how to get rid of this "feature"? You have several options. 1) The most "clean" solution is probably using the WDIDLE3 utility on your drives to disable automatic parking or in cases where its not possible to complete disable it, you can adjust it to 5 minutes, 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. 2) A less clean solution would be to setup a script that polls the SMART data of all disks affected by the problem every 8-9 seconds and have this script launch on boot. This will keep the affected drives just busy enough to not park their heads. - Sincerely, Dan Naumov