Date: Thu, 27 Mar 2008 00:23:26 +0100 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen <staale@kristoffersen.ws> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: Strange ZFS behaviour when a drive fail. Message-ID: <20080326232326.GG16062@eschew.pusen.org> In-Reply-To: <20080326151007.GA87075@eos.sc1.parodius.com> References: <20080326142346.GA16062@eschew.pusen.org> <20080326151007.GA87075@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2008-03-26 at 08:10, Jeremy Chadwick wrote: > On Wed, Mar 26, 2008 at 03:23:46PM +0100, Ståle Kristoffersen wrote: > > when I then ran zpool status I got: > > scrub: resilver completed with 0 errors on Wed Mar 26 15:15:50 2008 > > > > Why did it start to resilver onto "nothing", and why can't I replace it with mfid8 (even with -f)? > > I believe this problem was stated back in January (see the 2nd half of > the post), although Joe's problem showed an incremented CHKSUM, not an > actual drive in FAULTED mode: > > http://lists.freebsd.org/pipermail/freebsd-fs/2008-January/004241.html > > Either way, the situation sounds very familiar (failure + reboot > resulting in the pool silvering for strange reasons). Yeah, it looks like it could be the same thing. However, I fixed the last problem by writing over the last part of the drive with dd: dd if=/dev/zero of=/dev/mfid8 bs=1M seek=953300 I could then replace it and it started to resilver. Why didn't this happen automatically when I ran zpool replace -f? -- Ståle Kristoffersen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080326232326.GG16062>