Date: Tue, 16 Nov 2010 07:47:10 -0800 From: Michael DeMan <freebsd@deman.com> To: freebsd-fs@freebsd.org Subject: Re: ZFS panic after replacing log device Message-ID: <D316D362-4963-4B43-A2CA-DF516B4D5F5F@deman.com> In-Reply-To: <816D59CD-1BAF-4331-BEAD-67CEADCE4EF9@deman.com> References: <01NUB1F8POL000BNN4@tmk.com> <01NUB3IOMZJW00BNN4@tmk.com> <816D59CD-1BAF-4331-BEAD-67CEADCE4EF9@deman.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I just re-read my last post, after some rest and first cup of morning = coffee. Actually, removing the ZIL is a DUMB idea, not sure why I was = thinking that. And since you have replaced it already it would probably = not be the problem? I presume the machine as ECC memory? On Nov 15, 2010, at 11:48 PM, Michael DeMan wrote: > Hi, sorry for not completely digesting your original post. >=20 > I would say it is definitely very odd that writes are a problem. = Sounds like it might be a hardware problem. Is it possible to export = the pool, remove the ZIL and re-import it? I myself would be pretty = nervous trying that, but it would help isolate the problem? If you can = risk it. >=20 >=20 >=20 > On Nov 15, 2010, at 11:01 PM, Terry Kennedy wrote: >=20 >> Also note that multiple scrubs pass with no errors detected - it is = only >> writes that trigger the panic. It looks like something isn't being = cleaned >> up in the clear / replace path. >=20 > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D316D362-4963-4B43-A2CA-DF516B4D5F5F>