From nobody@FreeBSD.org  Fri Sep  8 16:15:35 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7CCCE16A4E0
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  8 Sep 2006 16:15:35 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 20D7543D53
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  8 Sep 2006 16:15:35 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k88GFYYi018182
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 8 Sep 2006 16:15:34 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k88GFYLn018181;
	Fri, 8 Sep 2006 16:15:34 GMT
	(envelope-from nobody)
Message-Id: <200609081615.k88GFYLn018181@www.freebsd.org>
Date: Fri, 8 Sep 2006 16:15:34 GMT
From: douglas steinawnd <dzs-pr@dzs.fx.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: graid3 does not rebuild degraded arrays
X-Send-Pr-Version: www-2.3

>Number:         103043
>Category:       kern
>Synopsis:       graid3 does not rebuild degraded arrays
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pjd
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 08 16:20:14 GMT 2006
>Closed-Date:    Fri Sep 08 18:51:24 GMT 2006
>Last-Modified:  Fri Sep 08 18:51:24 GMT 2006
>Originator:     douglas steinawnd
>Release:        6.1-STABLE
>Organization:
>Environment:
FreeBSD paris.fx.org 6.1-STABLE FreeBSD 6.1-STABLE #2: Thu Sep  7 06:52:51 PDT 2006     root@paris.fx.org:/usr/obj/usr/src/sys/HAWK6-SMP  amd64
>Description:
geom_raid3 is not rebuilding stale components. Removing/inserting, using
"graid3 rebuild", etc. commands doesn't help. Syslog shows that rebuild has
started, but the synchronized value stays at 0%:

GEOM_RAID3: Device 0: provider ad12 detected.
GEOM_RAID3: Device 0: rebuilding provider ad12.

dzs@paris:~$ graid3 list
Geom name: 0
State: DEGRADED
Components: 5
Flags: NOAUTOSYNC, VERIFY
GenID: 1
SyncID: 21
ID: 529755383
Zone64kFailed: 5947
Zone64kRequested: 241897
Zone16kFailed: 1671
Zone16kRequested: 76252
Zone4kFailed: 138407
Zone4kRequested: 5499275
Providers:
1. Name: raid3/0
   Mediasize: 1600353826816 (1.5T)
   Sectorsize: 2048
   Mode: r5w4e4
Consumers:
1. Name: ad4
   Mediasize: 400088457216 (373G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Flags: DIRTY
   GenID: 1
   SyncID: 21
   Number: 0
   Type: DATA
2. Name: ad6
   Mediasize: 400088457216 (373G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Flags: DIRTY
   GenID: 1
   SyncID: 21
   Number: 3
   Type: DATA
3. Name: ad8
   Mediasize: 400088457216 (373G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Flags: DIRTY
   GenID: 1
   SyncID: 21
   Number: 1
   Type: DATA
4. Name: ad10
   Mediasize: 400088457216 (373G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Flags: DIRTY
   GenID: 1
   SyncID: 21
   Number: 2
   Type: DATA
5. Name: ad12
   Mediasize: 400088457216 (373G)
   Sectorsize: 512
   Mode: r1w1e1
   State: SYNCHRONIZING
   Flags: DIRTY, SYNCHRONIZING, FORCE_SYNC
   GenID: 1
   SyncID: 21
   Synchronized: 0%
   Number: 4
   Type: PARITY



>How-To-Repeat:
Build a new graid3 array (perhaps using md devices), remove one component,
then insert it again. Rebuild appears to start, but monitoring with "gstat"
shows no real activity. Output of "graid3 list" or "graid3 status" shows 0%.
>Fix:
Revert to rev 1.40.2.12 of src/sys/geom/raid3/g_raid3.c. This problematic
change was apparently MFC'd on Sept 4th.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Fri Sep 8 18:48:19 UTC 2006 
State-Changed-Why:  
The problematic change was backed out by pjd just a few minutes ago.  Change 
to 'kern' since this was not amd64-specific. 


Responsible-Changed-From-To: freebsd-amd64->pjd 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Fri Sep 8 18:48:19 UTC 2006 
Responsible-Changed-Why:  
Let pjd track this since he made the change and then the backout. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=103043 
>Unformatted:
