From owner-freebsd-current@FreeBSD.ORG Fri Jul 17 10:50:03 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 253FB106566B for ; Fri, 17 Jul 2009 10:50:03 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from atmail-6.bnguk.net (atmail-6.bnguk.net [80.74.253.20]) by mx1.freebsd.org (Postfix) with ESMTP id A77468FC1A for ; Fri, 17 Jul 2009 10:50:02 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com) by atmail-6.bnguk.net with esmtp (Exim 4.69) (envelope-from ) id 1MQR1P-0002ER-8Y for current@freebsd.org; Mon, 13 Jul 2009 20:17:07 +0100 Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id 64B3E65219 for ; Mon, 13 Jul 2009 20:17:04 +0100 (BST) X-Virus-Scanned: amavisd-new at chrishedley.com Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id s7+-H2qLtxAb for ; Mon, 13 Jul 2009 20:17:01 +0100 (BST) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id E9D1765200 for ; Mon, 13 Jul 2009 20:17:00 +0100 (BST) Date: Mon, 13 Jul 2009 20:17:00 +0100 (BST) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: current@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Subject: ZFS pool corrupted on upgrade of -current 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: Fri, 17 Jul 2009 10:50:03 -0000 I seem to have a bit of a problem; or rather an extremely large problem. When updating FreeBSD from -current circa mid February to a -current as of a couple of days ago, I've just noticed some very serious problems with my ZFS pool. I've been using a raidz2 pool spread across 8 sata discs, numbered ad0 - ad7. It's been working fine across numerous system updates until now; it may have something to do with the device numbering changing (i.e. ad0, ad1 etc becoming ad4, ad6 and so on) so perhaps I should have exercised more care, but my pool has become badly degraded: two discs are reporting data errors (though at exactly the same block numbers, and I doubt the discs became faulty at exactly the same time as my update) and two have fallen off the pool altogether: I've no idea what's happened to them or whether or not it's quietly using them. They're still listed in /dev, just not in zpool status. I've attempted to replace one of the discs reporting data errors with my hot spare but it only gets about 5MB into the resilvering process when it starts over, and it's done that repeatedly. My other option was to use the hot spare as a simple UFS backup and copy as much data to it as possible, rebuilding the pool, but now it won't let go; so I now have an unstable pool, I can't rebuild it, and I have no means of backing it up. I even tried going back to my old February build, but it can no longer see the ZFS pool. Can anybody recommend a solution...? Chris.