Date: Sat, 29 Dec 2012 01:46:58 -0600 From: Scot Hetzel <swhetzel@gmail.com> To: Greg Bonett <greg.bonett@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: how to destroy zfs parent filesystem without destroying children - corrupted file causing kernel panick Message-ID: <CACdU%2Bf-K5bJ=fdO_kGARv95Hyeu-3mWKToi%2B0kbjFBRJRYQxjQ@mail.gmail.com> In-Reply-To: <CAPceqYS4QTu=970XUE=KKV-ZdPSO6n5y1Dzuu4HM4yyie=-Gag@mail.gmail.com> References: <CAPceqYS4QTu=970XUE=KKV-ZdPSO6n5y1Dzuu4HM4yyie=-Gag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 28, 2012 at 2:46 PM, Greg Bonett <greg.bonett@gmail.com> wrote: > Many months ago, I believe some *very bad hardware* caused corruption of a > file on one of my zfs file systems. I've isolated the corrupted file and > can reliably induce a kernel panic with "touch bad.file", "rm bad.file", or > "ls -l" in the bad.file's directory (ls in bad.file's dir doesn't cause > panic, but "ls bad.file" does). > Does: cat /dev/null > bad.file Cause a kernel panic? -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACdU%2Bf-K5bJ=fdO_kGARv95Hyeu-3mWKToi%2B0kbjFBRJRYQxjQ>