Date: Tue, 26 Apr 2011 14:25:00 +0100 From: "Conall O'Brien" <conall@conall.net> To: ambrosehuang ambrose <ambrosehua@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: Problems Terminating zpool scrub... Message-ID: <BANLkTi=Jban2q6h0HEpEMhWrfr56k1O_Jw@mail.gmail.com> In-Reply-To: <BANLkTikbPsf1d3p687RDVsaL_FO0KgKbfA@mail.gmail.com> References: <BANLkTinYp674E=96PhMaR0%2BUy9e9B6boVA@mail.gmail.com> <BANLkTimQ4FWnC12O3cDtptJR%2BvA2PcNqYA@mail.gmail.com> <BANLkTikbPsf1d3p687RDVsaL_FO0KgKbfA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26 April 2011 13:15, ambrosehuang ambrose <ambrosehua@gmail.com> wrote: > Could you post your PR number?I was curious about the driver used by > West Digital Disk, cause I use > the WR10EARS? http://www.freebsd.org/cgi/query-pr.cgi?pr=3D156647 I chalked it up to the SATA controller, since only 2 of my 5 identical WD20EARS disks were reporting DMA issues. > > 2011/4/25 Conall O'Brien <conall@conall.net> >> >> On 15 April 2011 15:59, Conall O'Brien <conall@conall.net> wrote: >> > Hello, >> > >> > >> > I've got a NAS box running 8-STABLEW [1] which I'm running with 5x >> > Western Digital 2TB disks. >> > >> > >> > One of the disks was having DMA issues as reported in dmesg, so I >> > began the usual zfs workflow of "zpool offline pool dev", physically >> > removing it and tried to "zpool replace pool dev" but my attempts to >> > do so fail, actually the zpool command keeps ending up in >> > uninterruptable wait (the D state). Before resorting to replacing the >> > disk, a zpool scrub was in progress. Now, I can't kill it using "zpool >> > scrub -s pool", it too ends up in the D state. >> > >> > >> > Is there another way than "zpool scrub -s pool" to terminate a scrub >> > process, so I can proceed with the disk replacement. I care more about >> > resilvering my pool before getting around to scrubbing it. >> > >> > >> > Thanks! >> > >> > >> > [1] For completeness, uname -a reports FreeBSD galvatron.taku.ie >> > 8.2-STABLE FreeBSD 8.2-STABLE #1: Sat Mar 19 13:18:46 UTC 2011 >> > root@galvatron.taku.ie:/usr/src/obj/usr/src/sys/GALVATRON =C2=A0amd64 >> >> I worked out the problem. There's a regression in one of the drivers >> between the kernel I was running and my previous kernel: >> >> FreeBSD galvatron.taku.ie 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #0: >> Wed Dec 29 04:00:27 UTC 2010 >> root@galvatron.taku.ie:/usr/src/obj/usr/src/sys/GALVATRON =C2=A0amd64 >> >> >> I'll file a PR to get it fixed. >> >> -- >> >> Conall O'Brien >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 Conall O'Brien
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=Jban2q6h0HEpEMhWrfr56k1O_Jw>