From owner-freebsd-fs@FreeBSD.ORG Sat Dec 27 03:22:14 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E59521065670 for ; Sat, 27 Dec 2008 03:22:14 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 031788FC1A for ; Sat, 27 Dec 2008 03:22:14 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (unknown [74.193.182.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 96702A31A159 for ; Fri, 26 Dec 2008 21:22:12 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id mBR3M9pk002366 for ; Fri, 26 Dec 2008 21:22:10 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Fri, 26 Dec 2008 21:22:09 -0600 (CST) From: Wes Morgan To: freebsd-fs@freebsd.org In-Reply-To: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> Message-ID: References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: zpool resilver restarting X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Dec 2008 03:22:15 -0000 I just did a zpool replace on a new drive, and now it's resilvering. Only, when it gets about 20mb resilvered it restarts. I can see all the drive activity simply halting for a period then resuming in gstat. I see some bugs in the opensolaris tracker about this, but no resolutions. It doesn't seem to be related to calling "zpool status" because I can watch gstat and see it restarting... Anyone seen this before, and hopefully have a workaround...? The pool lost a drive on Wednesday and was running with a device missing, however due to the device numbering changing on the scsi bus, I had to export/import the pool to get it to come up, the same for after replacing it. [morganw@volatile:~$]: zpool status media (hangs a bit) pool: media state: DEGRADED status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scrub: resilver in progress for 0h1m, 0.01% done, 368h10m to go config: NAME STATE READ WRITE CKSUM media DEGRADED 0 0 0 raidz2 DEGRADED 0 0 0 da2 ONLINE 0 0 0 20.3M resilvered da6 ONLINE 0 0 0 20.3M resilvered da0 ONLINE 0 0 0 20.3M resilvered da7 ONLINE 0 0 0 17.0M resilvered da1 ONLINE 0 0 0 20.2M resilvered da3 ONLINE 0 0 0 20.2M resilvered da5 ONLINE 0 0 0 19.2M resilvered replacing DEGRADED 0 0 0 17628927049345412941 UNAVAIL 3 3.91K 0 was /dev/da4 da4 ONLINE 0 0 0 22.6M resilvered errors: No known data errors [morganw@volatile:~$]: zpool status media pool: media state: DEGRADED status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scrub: resilver in progress for 0h0m, 0.00% done, 766h21m to go config: NAME STATE READ WRITE CKSUM media DEGRADED 0 0 0 raidz2 DEGRADED 0 0 0 da2 ONLINE 0 0 0 738K resilvered da6 ONLINE 0 0 0 742K resilvered da0 ONLINE 0 0 0 739K resilvered da7 ONLINE 0 0 0 563K resilvered da1 ONLINE 0 0 0 732K resilvered da3 ONLINE 0 0 0 734K resilvered da5 ONLINE 0 0 0 738K resilvered replacing DEGRADED 0 0 0 17628927049345412941 UNAVAIL 3 4.67K 0 was /dev/da4 da4 ONLINE 0 0 0 848K resilvered errors: No known data errors