Date: Wed, 18 Oct 2006 07:11:55 +1000 From: Norberto Meijome <freebsd@meijome.net> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-stable@freebsd.org Subject: Re: kernel panic mounting /tmp - 6.2-PRERELEASE Message-ID: <20061018071155.4331765a@localhost> In-Reply-To: <20061017145946.GB68977@lor.one-eyed-alien.net> References: <20061018002558.3a2bcdf6@localhost> <20061017145946.GB68977@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Oct 2006 09:59:46 -0500
Brooks Davis <brooks@one-eyed-alien.net> wrote:
> > Is there a bigger issue here? anything I can do to help diagnose / debug
> > this?
>
> Possibly and no. By recreating the file system you've destroyed
> the information needed to isolate the cause. It's known that an
> appropriately corrupt file system can do this, but the causes (there are
> probably several) are not yet known. There is some speculation that the
> only solution is to add checksums to all key data sections.
>
> -- Brooks
Gotcha - i thought as much... i hoped a dump -0 would save enough info though.
I just needed to have /tmp back in place asap....
i'll keep the files around for a week or so in case something comes up.
_________________________
{Beto|Norberto|Numard} Meijome
Without vision you may find that you make your way through life by bumping into
things.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061018071155.4331765a>