From owner-freebsd-geom@FreeBSD.ORG Fri Sep 10 10:30:29 2010 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE45D106564A for ; Fri, 10 Sep 2010 10:30:29 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9C1C98FC13 for ; Fri, 10 Sep 2010 10:30:29 +0000 (UTC) Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 42FEB19E02A; Fri, 10 Sep 2010 12:14:12 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id A09F619E027; Fri, 10 Sep 2010 12:14:09 +0200 (CEST) Message-ID: <4C8A04EC.3090409@quip.cz> Date: Fri, 10 Sep 2010 12:14:04 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6 MIME-Version: 1.0 To: rick-freebsd2009@kiwi-computer.com References: <20100910031851.GA7066@rix.kiwi-computer.com> In-Reply-To: <20100910031851.GA7066@rix.kiwi-computer.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: it's a race between gmirror and UFS labels and gjournal X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 10:30:29 -0000 Rick C. Petty wrote: > I've been struggling with GEOM_MIRROR over-aggressively dropping drives > and it's causing some issues. I'm running 8.1-stable. > > Essentially I have gmirror'd disks, gpart partitions inside the mirror, > and UFS labels on all my gpartitioned filesystems. Everything is fine > as long as the mirror probes the disks first (which it does). > > The problem is that after kernel panics, gmirror often drops a disk: > > GEOM_MIRROR: Component ada0 (device fs0) broken, skipping. > > If it drops ada1, I have no problems, but if it drops ada0, then ada0 > is subsequently probed for its GPT partitions, of which the secondary > table is corrupt (probably because it's looking at the GEOM_MIRROR > metadata). Unfortunately, it proceeds and then mounts all the UFS > filesystems by label from /dev/ada0 instead of those in /dev/mirror/fs0 > which is bad. The same problem is with gjournal on gmirror. If gmirror drops the disk, then gjournal is (sometimes) detected on the first "broken disk" and this disk cannot be re-inserted in to gmirror again. (I have this experience on 7.x). One must reboot in to single-user without gjournal module loaded and re-insert the disk in to gmirror. Miroslav Lachman