From owner-freebsd-stable@FreeBSD.ORG  Sun Feb 18 19:03:56 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: stable@FreeBSD.org
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 2DB1B16A406
	for <stable@FreeBSD.org>; Sun, 18 Feb 2007 19:03:56 +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 98C0E13C4A3
	for <stable@FreeBSD.org>; Sun, 18 Feb 2007 19:03:55 +0000 (UTC)
	(envelope-from marck@rinet.ru)
Received: from localhost (localhost [127.0.0.1])
	by woozle.rinet.ru (8.13.8/8.13.8) with ESMTP id l1IIrE3t013906
	for <stable@FreeBSD.org>; Sun, 18 Feb 2007 21:53:14 +0300 (MSK)
	(envelope-from marck@rinet.ru)
Date: Sun, 18 Feb 2007 21:53:14 +0300 (MSK)
From: Dmitry Morozovsky <marck@rinet.ru>
To: stable@FreeBSD.org
Message-ID: <20070218214731.G9968@woozle.rinet.ru>
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-3.0
	(woozle.rinet.ru [0.0.0.0]); Sun, 18 Feb 2007 21:53:14 +0300 (MSK)
Cc: 
Subject: gmirror: degraded @ 100%
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: Sun, 18 Feb 2007 19:03:56 -0000

Dear colleagues,

today I've found that one of two disks had been removed from a couple of 
gmirror'ed partiotions dur to read timeout. I have done `gmirror forget' and 
`gmirror insert', and it works for relatively small partitions; however, on 
rather large partiotion it did sync, and then stalls at very strage state:

root@office:/usr/local/etc# gmirror status m0g
      Name    Status  Components
mirror/m0g  DEGRADED  ad4g
                      ad6g (100%)
root@office:/usr/local/etc# gmirror list m0g
Geom name: m0g
State: DEGRADED
Components: 2
Balance: load
Slice: 4096
Flags: NONE
GenID: 2
SyncID: 5
ID: 2249072617
Providers:
1. Name: mirror/m0g
   Mediasize: 225734095872 (210G)
   Sectorsize: 512
   Mode: r2w1e1
Consumers:
1. Name: ad4g
   Mediasize: 225734096384 (210G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Priority: 0
   Flags: BROKEN
   GenID: 2
   SyncID: 5
   ID: 2403640489
2. Name: ad6g
   Mediasize: 225734096384 (210G)
   Sectorsize: 512
   Mode: r1w1e1
   State: SYNCHRONIZING
   Priority: 0
   Flags: DIRTY, SYNCHRONIZING
   GenID: 2
   SyncID: 5
   Synchronized: 100%
   ID: 2137028155

There is no activity on ad6g.


Any hints?



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