From owner-freebsd-current@FreeBSD.ORG Fri Nov 16 16:33:08 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 904302CE; Fri, 16 Nov 2012 16:33:08 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id 403D18FC16; Fri, 16 Nov 2012 16:33:08 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3Y34k96mjBzFTDB; Fri, 16 Nov 2012 17:33:05 +0100 (CET) X-Virus-Scanned: amavisd-new at madpilot.net Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkZxEZEpMvWe; Fri, 16 Nov 2012 17:33:01 +0100 (CET) Received: from vwg82.hq.ignesti.it (unknown [80.74.176.55]) by winston.madpilot.net (Postfix) with ESMTPSA; Fri, 16 Nov 2012 17:33:01 +0100 (CET) Message-ID: <50A66ABE.5030108@madpilot.net> Date: Fri, 16 Nov 2012 17:33:02 +0100 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121114 Thunderbird/16.0.2 MIME-Version: 1.0 To: Niclas Zeising Subject: Re: problem booting to multi-vdev root pool [Was: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot] References: <509D1DEC.6040505@FreeBSD.org> <50A27243.408@madpilot.net> <50A65F83.5000604@FreeBSD.org> <50A66615.9060906@daemonic.se> In-Reply-To: <50A66615.9060906@daemonic.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Bartosz Stec , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Nov 2012 16:33:08 -0000 On 11/16/12 17:13, Niclas Zeising wrote: > > Just to confirm, since I am holding back an update pending on this. > If I have a raidz root pool, with three disks, like this: > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > gpt/disk0 ONLINE 0 0 0 > gpt/disk1 ONLINE 0 0 0 > gpt/disk2 ONLINE 0 0 0 > > Then I'm fine to update without issues. the problem is only if, as an > example, you have a mirror with striped disks, or a stripe with mirrored > disks, which it seems to me the original poster had. > Am I correct, and therefore ok to update? Yes, looks like that. The affected system pool looks like this: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 ada2p2 ONLINE 0 0 0 gpt/disk3 ONLINE 0 0 0 other systems I have with simple mirror pools or single disks have shown no problems. BTW I don't know why the system insists on identifying the third disk as ada2p2, it has a gpt label defined just like the others. -- Guido Falsi