From owner-freebsd-stable@FreeBSD.ORG  Mon Nov 20 13:47:49 2006
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 F383516A494;
	Mon, 20 Nov 2006 13:47:48 +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 3407743E03;
	Mon, 20 Nov 2006 13:46:39 +0000 (GMT) (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 kAKDknD8051975;
	Mon, 20 Nov 2006 16:46:49 +0300 (MSK) (envelope-from marck@rinet.ru)
Date: Mon, 20 Nov 2006 16:46:49 +0300 (MSK)
From: Dmitry Morozovsky <marck@rinet.ru>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Message-ID: <20061120163300.Y50845@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-2.0.2
	(woozle.rinet.ru [0.0.0.0]); Mon, 20 Nov 2006 16:46:49 +0300 (MSK)
Cc: stable@FreeBSD.org
Subject: g.* device stop while rebuilding
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: Mon, 20 Nov 2006 13:47:49 -0000

Dear Pawel,

is it too difficult to forcibly stop rebuilding of a composite geom instance? 
It is often needed (or at least desirable), but all attemtpt fail:

# graid3 status r0h
     Name    Status  Components
raid3/r0h  DEGRADED  ad0h
                     ad4h
                     ad8h (20%)
# graid3 stop r0h  
Cannot destroy device r0h (error=16).

Even

# graid3 unload  
Could not unload module: Device busy.

I can remove provider which are in rebuild state:

# graid3 remove -n2 r0h 
GEOM_RAID3: Device r0h: provider ad8h disconnected.
GEOM_RAID3: Device r0h: rebuilding provider ad8h stopped.

But this destroys rebuild state completely even when r3 device is read-only.

The same state for gmirror.

Any hints? Thanks in advance.

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