Date: Fri, 10 Sep 2010 12:14:04 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: rick-freebsd2009@kiwi-computer.com Cc: freebsd-geom@freebsd.org Subject: Re: it's a race between gmirror and UFS labels and gjournal Message-ID: <4C8A04EC.3090409@quip.cz> In-Reply-To: <20100910031851.GA7066@rix.kiwi-computer.com> References: <20100910031851.GA7066@rix.kiwi-computer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C8A04EC.3090409>