Date: Fri, 06 Nov 2009 17:02:23 -0600 From: "James R. Van Artsdalen" <james-freebsd-fs2@jrv.org> To: =?ISO-8859-1?Q?Gerrit_K=FChn?= <gerrit@pmp.uni-hannover.de> Cc: freebsd-fs@freebsd.org Subject: Re: trace for zfs panic mounting fs after crash with RC2 Message-ID: <4AF4AAFF.2080104@jrv.org> In-Reply-To: <20091106231440.4f0f2cbb.gerrit@pmp.uni-hannover.de> References: <20091106094734.4b056899.gerrit@pmp.uni-hannover.de> <4AF4123A.4080301@andric.com> <20091106231440.4f0f2cbb.gerrit@pmp.uni-hannover.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Gerrit K=FChn wrote:
> I recomplied the kernel with ddb support and got the following trace
> (using mount -t zfs instead of zfs mount this time, but getting the sam=
e
> panic):
You may be able to recover your pool by changing the line below, but I
have never tried it: it may clobber the pool. You definitely don't want
this change normally! It may be necessary to avoid calling zil_destroy
here too.
How the ZIL got corrupted - if it did - is a harder question. What kind
of hard disk is this, and how is it connected to the system? Was there
any redundancy (mirror, raidz)?
void
zil_replay(objset_t *os, void *arg, uint64_t *txgp,
zil_replay_func_t *replay_func[TX_MAX_TYPE],
zil_replay_cleaner_t *replay_cleaner)
{
zilog_t *zilog =3D dmu_objset_zil(os);
const zil_header_t *zh =3D zilog->zl_header;
zil_replay_arg_t zr;
=3D=3D> if (1 || zil_empty(zilog)) {
zil_destroy(zilog, B_TRUE);
return;
}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AF4AAFF.2080104>