From owner-freebsd-stable@FreeBSD.ORG  Thu Mar 10 18:11:26 2011
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E66181065709;
	Thu, 10 Mar 2011 18:11:26 +0000 (UTC) (envelope-from marck@rinet.ru)
Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68])
	by mx1.freebsd.org (Postfix) with ESMTP id 75E678FC13;
	Thu, 10 Mar 2011 18:11:22 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by woozle.rinet.ru (8.14.4/8.14.4) with ESMTP id p2AIBLTx060746;
	Thu, 10 Mar 2011 21:11:21 +0300 (MSK) (envelope-from marck@rinet.ru)
Date: Thu, 10 Mar 2011 21:11:21 +0300 (MSK)
From: Dmitry Morozovsky <marck@rinet.ru>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Message-ID: <alpine.BSF.2.00.1103102105480.57402@woozle.rinet.ru>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
X-NCC-RegID: ru.rinet
X-OpenPGP-Key-ID: 6B691B03
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6
	(woozle.rinet.ru [0.0.0.0]); Thu, 10 Mar 2011 21:11:21 +0300 (MSK)
Cc: stable@FreeBSD.org
Subject: gmirror start bug?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2011 18:11:27 -0000

Dear Pawel,

it seems thet gmirror is entering the endless loop if one inserted disk with 
previously configured mirror part in syncronyzing state:

root@moose:/media/sata# gmirror list m0g
Geom name: m0g
State: STARTING
Components: 2
Balance: split
Slice: 4096
Flags: NONE
GenID: 0
SyncID: 0
ID: 2992987948
Consumers:
1. Name: ad22g
   Mediasize: 272441875968 (254G)
   Sectorsize: 512
   Mode: r1w1e1
   State: NEW
   Priority: 0
   Flags: SYNCHRONIZING
   GenID: 0
   SyncID: 2
   ID: 3619189671

root@moose:/media/sata# gmirror stop m0g ; gmirror clear ad22g
Can't clear metadata on ad22g: Operation not permitted.
gmirror: Not fully done.

from kernel log:

Mar 10 21:04:31 <kern.crit> moose kernel: GEOM_MIRROR: Force device m0g start 
due to timeout.
Mar 10 21:04:31 <kern.crit> moose kernel: GEOM_MIRROR: Device m0g destroyed.
Mar 10 21:04:35 <kern.crit> moose kernel: GEOM_MIRROR: Force device m0g start 
due to timeout.
Mar 10 21:04:35 <kern.crit> moose kernel: GEOM_MIRROR: Device m0g destroyed.
Mar 10 21:04:39 <kern.crit> moose kernel: GEOM_MIRROR: Force device m0g start 
due to timeout.
Mar 10 21:04:39 <kern.crit> moose kernel: GEOM_MIRROR: Device m0g destroyed.

...

In my case, a workaround was: detach broken disk, configure mirror with the 
same name (I did it over md), then gmirror clear ad22g -- but I suppose this 
situation should be somehow detected and loop broken.

Thanks!



-- 
Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer:                                 marck@FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------