From owner-freebsd-current@FreeBSD.ORG Mon May 25 15:39:16 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 C634C106564A for ; Mon, 25 May 2009 15:39:16 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gx0-f169.google.com (mail-gx0-f169.google.com [209.85.217.169]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0538FC16 for ; Mon, 25 May 2009 15:39:16 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by gxk17 with SMTP id 17so600066gxk.19 for ; Mon, 25 May 2009 08:39:15 -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 :content-transfer-encoding; bh=cNmT3Jpla+ZvYxU3B/+fEbVsOHXJc9NoLa8NkhwRsjA=; b=KwJKaje6bR1H5hA4E+C2CyNKwzbvnliIBzbZUnkMA4GzbY1xqq00zFMWwe7Twdj6KE WgoIeGPe+TbAsktQ2qXaj4oHLN5fyG597GwmKaZh/xGFd3lhyHCCNo9gDGnTf5n4ZzjE xvLSrYfJzfQADfi37EZ11rvx/HUDBulGUM5wI= 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:content-transfer-encoding; b=ihMU0nAz775vmPD6o/OfvM/CGvDonlBY2xaX3SDSwDa8fvjSiqw4tVavD6y1l1qoz9 sfrbiw+NEfSEvcNtGto7xabmT3G8m4gX8Ut0If0JJ8kiqVEysJMVsoPTvTGWeYV/1u9u 64GIv/WFHjvAMhK0/5hp8wd7Fv/oGTgG6ZEM8= MIME-Version: 1.0 Received: by 10.150.134.18 with SMTP id h18mr14416588ybd.317.1243265953749; Mon, 25 May 2009 08:39:13 -0700 (PDT) In-Reply-To: References: <4E6E325D-BB18-4478-BCFD-633D6F4CFD88@exscape.org> Date: Mon, 25 May 2009 08:39:13 -0700 Message-ID: From: Freddie Cash To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: ZFS panic under extreme circumstances (2/3 disks corrupted) 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: Mon, 25 May 2009 15:39:17 -0000 On Mon, May 25, 2009 at 2:13 AM, Thomas Backman wrote: > On May 24, 2009, at 09:02 PM, Thomas Backman wrote: > >> So, I was playing around with RAID-Z and self-healing... > > Yet another follow-up to this. > It appears that all traces of errors vanish after a reboot. So, say you have > a dying disk; ZFS repairs the data for you, and you don't notice (unless you > check zpool status). Then you reboot, and there's NO (easy?) way that I can > tell to find out that something is wrong with your hardware! On our storage server that was initially configured using 1 large 24-drive raidz2 vdev (don't do that, by the way), we had 1 drive go south. "zpool status" was full of errors. And the error counts survived reboots. Either that, or the drive was so bad that the error counts started increasing right away after a boot. After a week of fighting with it to get the new drive to resilver and get added to the vdev, we nuked it and re-created it using 3 raidz2 vdevs each comprised of 8 drives. (Un)fortunately, that was the only failure we've had so far, so can't really confirm/deny the "error counts reset after reboot". -- Freddie Cash fjwcash@gmail.com