Date: Sun, 30 Dec 2012 15:38:41 -0800 From: Greg Bonett <greg.bonett@gmail.com> To: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: how to destroy zfs parent filesystem without destroying children - corrupted file causing kernel panick Message-ID: <CAPceqYQxxPapJQq4=Hs6WMMoVoszNg3gY%2BdLSqq9u1xuzzTZyQ@mail.gmail.com> In-Reply-To: <20121230123213.2312fb47@fabiankeil.de> References: <CAPceqYS4QTu=970XUE=KKV-ZdPSO6n5y1Dzuu4HM4yyie=-Gag@mail.gmail.com> <20121230123213.2312fb47@fabiankeil.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > My next plan would be reporting the problem with sufficient > information so the bug can be fixed. > > Destroying the dataset or the whole pool seems like papering over the > real issue to me and you could still do it if the PR gets ignored for > too long or a developer agrees that this is the only option. > > ok, that's a good idea - do you know where I should report this problem? unfortunately, I don't know how I can provide the problematic file because any read, cp, or mv causes kernel panic.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPceqYQxxPapJQq4=Hs6WMMoVoszNg3gY%2BdLSqq9u1xuzzTZyQ>