Date: Tue, 7 Jul 2009 17:13:36 -0700 From: "Mahlon E. Smith" <mahlon@martini.nu> To: Freddie Cash <fjwcash@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: ZFS: drive replacement performance Message-ID: <20090708001336.GA95670@martini.nu> In-Reply-To: <b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com> References: <20090707195614.GA24326@martini.nu> <b269bc570907071354r36015689ha362ba83413efc46@mail.gmail.com> <20090707222631.GA70750@martini.nu> <b269bc570907071532ub95af78i6ad3a09e8c6887d7@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Jul 07, 2009, Freddie Cash wrote: > > I think (never tried) you can use "zpool scrub -s store" to stop the > resilver. If not, you should be able to re-do the replace command. Hmm. I think I may be stuck. % zpool scrub -s store % zpool status | grep scrub scrub: resilver in progress for 0h0m, 0.00% done, 745h41m to go % zpool replace store 2025342973333799752 da8 invalid vdev specification use '-f' to override the following errors: /dev/da8 is part of active pool 'store' % zpool replace -f store 2025342973333799752 da8 invalid vdev specification the following errors must be manually repaired: /dev/da8 is part of active pool 'store' % zpool detach store da8 cannot detach da8: no valid replicas % zpool detach store 2025342973333799752 cannot detach 2025342973333799752: no valid replicas 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 now have to wonder if that's really the active da2 it is complaining about (the one claiming to be online with 0 errors) or the one I'm trying to replace with da8. The current da2 doesn't seem to be having any additional problems, like the checksum mismatches or other associated console errors I've come to expect, but of course the old one is no longer attached to the machine. In any event, I'd wager that isn't something I normally want to see, and I may have something else going on here. (Bad controller, etc?) Serves me right for naming a machine 'disobedience', I guess. Next one is getting named 'subservience.' Going to halt and pull da8 under the assumption that will at least stop the resilver, and try the detach again. I'll holler back if I get stuff going again, but this is looking more like a hardware problem. Thanks again for the insight! -Mahlon -- Mahlon E. Smith http://www.martini.nu/contact.html [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iD8DBQFKU+Sw1bsjBDapbeMRAoN1AJ4hnaXAcsumQ4YPl6hgeS8j+b0+swCgq8O0 4X/YnS2iCHK8jd47S0D15SE= =GIVG -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090708001336.GA95670>