Date: Sat, 29 Dec 2012 22:59:46 -0800 From: Artem Belevich <art@freebsd.org> To: Greg Bonett <greg.bonett@gmail.com> Cc: Scot Hetzel <swhetzel@gmail.com>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: how to destroy zfs parent filesystem without destroying children - corrupted file causing kernel panick Message-ID: <CAFqOu6gS-LYAK2rV%2B8_2A-FRrFQsahg==eMWEh3mp_QEJLyB0A@mail.gmail.com> In-Reply-To: <CAPceqYTv%2Bbzb5KvSZUZwGk6jbe-6xYzvXunxrZOodF-X25ML2w@mail.gmail.com> References: <CAPceqYS4QTu=970XUE=KKV-ZdPSO6n5y1Dzuu4HM4yyie=-Gag@mail.gmail.com> <CACdU%2Bf-K5bJ=fdO_kGARv95Hyeu-3mWKToi%2B0kbjFBRJRYQxjQ@mail.gmail.com> <CAPceqYTv%2Bbzb5KvSZUZwGk6jbe-6xYzvXunxrZOodF-X25ML2w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 29, 2012 at 12:35 AM, Greg Bonett <greg.bonett@gmail.com> wrote: > > > > > Does: > > > > cat /dev/null > bad.file > > > > Cause a kernel panic? > > > > > > > ah, sadly that does cause a kernel panic. I hadn't tried it though, thanks > for the suggestion. It's probably a long shot, but you may try removing bad file using illumos (ex opensolaris) system (or liveCD). In the past it used to be a little bit more robust than FreeBSD when it came to dealing with filesystem corruption. In one case I had illumos printed out a message about corrupt pool and remained up and running while FreeBSD would just crash when I tried mounting the pool. --Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFqOu6gS-LYAK2rV%2B8_2A-FRrFQsahg==eMWEh3mp_QEJLyB0A>