From owner-freebsd-current@FreeBSD.ORG Sun Jun 14 08:27:23 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDD02106566B for ; Sun, 14 Jun 2009 08:27:23 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gx0-f207.google.com (mail-gx0-f207.google.com [209.85.217.207]) by mx1.freebsd.org (Postfix) with ESMTP id A65628FC08 for ; Sun, 14 Jun 2009 08:27:23 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by gxk3 with SMTP id 3so4898153gxk.19 for ; Sun, 14 Jun 2009 01:27:22 -0700 (PDT) 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=SWs4zupim+dzL4Isi/BeHOe/urXMhMgo7LWijlrCgCU=; b=lEyO5uXMzvbk5M87IL0wO/U8I5hfzeAbgkqtOA4fENOLt2vb+j15ASisG/hwXvKSeg 5iZOb3tfWpauaDD2AvsF88z5Qbwx7rNfroqT/Hs3qGgyecjw0IlV+f+4zWrMr6auwJGP K9O9xjlTVNWSfGIevuvdD9Gww9r3Q+8aWq/dY= 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=gr3eEe8yP0xOZVxUfeChvLJmCg8pDGOziVjkZ5HhpFShmuPfqFxgIaAn8YSjPi18tb hTysnTaqL8gWgRL0Xl66zivOdyL0QHT7btsQtXWTzJhhya1rjrIaVnlwS9Le1RCIZMPm D2G6YU+mWrr+ZVGJOzY14Suj2tlw7qtJyKWOs= MIME-Version: 1.0 Received: by 10.151.130.1 with SMTP id h1mr10845321ybn.172.1244968042582; Sun, 14 Jun 2009 01:27:22 -0700 (PDT) In-Reply-To: <200906132311.15359.ianjhart@ntlworld.com> References: <200906132311.15359.ianjhart@ntlworld.com> Date: Sun, 14 Jun 2009 01:27:22 -0700 Message-ID: From: Freddie Cash To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: zpool scrub errors on 3ware 9550SXU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jun 2009 08:27:24 -0000 On Sat, Jun 13, 2009 at 3:11 PM, ian j hart wrote: > [long post with long lines, sorry] > > I have the following old hardware which I'm trying to make into a storage > server (back story elided). > > Tyan Thunder K8WE with dual Opteron 270 > 8GB REG ECC RAM > 3ware/AMCC 9550SXU-16 SATA controller > Adaptec 29160 SCSI card -> Quantum LTO3 tape > ChenBro case and backplanes. > 'don't remember' PSU. I do remember paying =C2=A398 3 years ago, so not c= heap! > floppy > > Some Seagate Barracuda drives. Two old 500GB for the O/S and 14 new 1.5TB > for > data (plus some spares). > > Astute readers will know that the 1.5TB units have a chequered history. > > I went to considerable effort to avoid being stuck with a bricked unit, s= o > imagine my dismay when, just before I was about to post this, I discovere= d > there's a new issue with these drives where they reallocate sectors, from > new. > > I don't want to get sucked into a discussion about whether these disks ar= e > faulty or not. I want to examine what seems to be a regression between > 7.2-RELEASE and 8-CURRENT. If you can't resist, start a thread in chat an= d > CC > me. > > Anyway, here's the full story (from memory I'm afraid). > > All disks exported as single drives (no JBOD anymore). > Install current snapshot on da0 and gmirror with da1, both 500GB disks. > Create a pool with the 14 1.5TB disks. Raidz2. > Are you using a single raidz2 vdev using all 14 drives? If so, that's probably (one of) the source of the issues. You really shouldn't use more than 8 or 9 drives in a singel raidz vdev. Bad things happen. Especially during resilvers and scrubs. We learned this the hard way, trying to replace a drive in a 24-drive raidz2 vdev. If possible, try to rebuild the pool using multiple, smaller raidz (1 or 2) vdevs. --=20 Freddie Cash fjwcash@gmail.com