From owner-freebsd-stable@FreeBSD.ORG Thu Jul 9 04:43:35 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3333B106566C for ; Thu, 9 Jul 2009 04:43:35 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from vps.kc8onw.net (kc8onw.net [69.31.85.203]) by mx1.freebsd.org (Postfix) with ESMTP id 0B9B28FC12 for ; Thu, 9 Jul 2009 04:43:34 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from [10.70.3.194] (in-67-236-240-112.dhcp.embarqhsd.net [67.236.240.112]) by vps.kc8onw.net (Postfix) with ESMTPSA id B94EF17031; Wed, 8 Jul 2009 21:03:51 -0400 (EDT) Message-ID: <4A5541E9.2050801@kc8onw.net> Date: Wed, 08 Jul 2009 21:03:37 -0400 From: Jonathan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: "Mahlon E. Smith" , freebsd-stable@freebsd.org References: <20090707195614.GA24326@martini.nu> <20090707222631.GA70750@martini.nu> <20090708001336.GA95670@martini.nu> In-Reply-To: <20090708001336.GA95670@martini.nu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ZFS: drive replacement performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2009 04:43:35 -0000 On 7/7/2009 8:13 PM, Mahlon E. Smith wrote: > I also tried another export/import cycle, in the random hope that would > stop the active replace -- no dice. *However*, on the import, now I see > this flooding my console (wasn't there previously, strangely): > > Jul 7 16:50:15 disobedience root: ZFS: vdev I/O failure, zpool=store path=/dev/da2 offset=262144 size=8192 error=6 > Jul 7 16:50:15 disobedience root: ZFS: vdev I/O failure, zpool=store path=/dev/da2 offset=499988824064 size=8192 error=6 I actually just had this exact issue with a dead drive, controller renumbering, and vdev I/O failure. I eventually shut the system down completely, pulled the new drive, checked all the drive connections, powered the machine back up without the new drive. Then I inserted the new drive and initiated a scan for it. Apparently ZFS doesn't realize when a resilver is partially done because it resilvered in a matter of seconds at this point. I then did a scrub which found several million checksum errors but successfully corrected the pool without any vdev I/O failure errors. I hope this helps, Jonathan Stewart