Date: Tue, 2 Jun 2009 10:01:19 +0200 From: Thomas Backman <serenity@exscape.org> To: James R. Van Artsdalen <james-freebsd-current@jrv.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ZFS panic under extreme circumstances (2/3 disks corrupted) Message-ID: <4EE92FAD-528E-4154-B608-D822720EAB26@exscape.org> In-Reply-To: <4A248F6E.5020701@jrv.org> References: <4E6E325D-BB18-4478-BCFD-633D6F4CFD88@exscape.org> <D98FEABB-8B8A-48E6-B021-B05816B4C699@exscape.org> <b269bc570905250839r54a0f58fo5474e9e219a222ca@mail.gmail.com> <D817D098-9C36-4B72-9DCB-027CE8A7C564@exscape.org> <4A248F6E.5020701@jrv.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 2, 2009, at 04:33 AM, James R. Van Artsdalen wrote: > Thomas Backman wrote: >> I have another unfortunate thing to note regarding this: after a >> reboot, it's even impossible to tell *which disk* has gone bad, even >> if the pool is "uncleared" but otherwise "healed". It simply says >> that >> a device has failed, with no clue as to which one, since they're all >> "ONLINE"! > > Is there anything recorded in the pool history log about this? > > The pool errlog is documented to be rotated after every scrub. I don't think so, and can't check (the "disks" are long gone from the VM), other than this message that I posted earlier in the thread: http://lists.freebsd.org/pipermail/freebsd-current/2009-May/007259.html Regards, Thomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EE92FAD-528E-4154-B608-D822720EAB26>