Date: Wed, 08 Jul 2009 21:03:37 -0400 From: Jonathan <jonathan@kc8onw.net> To: "Mahlon E. Smith" <mahlon@martini.nu>, freebsd-stable@freebsd.org Subject: Re: ZFS: drive replacement performance Message-ID: <4A5541E9.2050801@kc8onw.net> In-Reply-To: <20090708001336.GA95670@martini.nu> References: <20090707195614.GA24326@martini.nu> <b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com> <20090707222631.GA70750@martini.nu> <b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com> <20090708001336.GA95670@martini.nu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A5541E9.2050801>