Date: Mon, 10 Nov 2003 10:51:42 -0500 From: Jason Morgan <jwm-freebsd@sentinelchicken.net> To: freebsd-questions@freebsd.org Subject: Re: 5.1 RELEASE - Panic Message-ID: <20031110155141.GC11191@sentinelchicken.net> In-Reply-To: <20031109212858.GB99275@xor.obsecurity.org> References: <20031109203729.GA11191@sentinelchicken.net> <20031109212858.GB99275@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 09, 2003 at 01:28:58PM -0800, Kris Kennaway wrote:
> On Sun, Nov 09, 2003 at 03:37:29PM -0500, freebsd@sentinelchicken.net wrote:
> > I am currently running 5.1 RELEASE, as system I recently 'downgraded' from CURRENT. Since I moved back to RELEASE, the system has been giving me file
> > system errors from time to time. I've run fsck - though I know very little of what I'm going with this utility. And now, I'm getting a PANIC, with
> > the following error:
> >
> > mode = 041777, inum = 3, fs = /usr
> > panic: ffs_valloc: dup alloc
> > Debugger("panic")
> > Stoped at Debugger+0x4d: xchgl %ebx,in_Debugger.0
> >
> > I ran CURRENT on this system for 6-8 months and never got a panic - the system is not used all that often.
> >
> > Anyone have any suggestions as to what I can do?
>
> I usually get this on marginal (IBM deathstar) disks..it means you had
> some kind of data corruption.
>
> There's not much you can do about it except for trying different disk
> hardware if it happens a lot.
I moved back to CURRENT and all is now working fine. Very strange error.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031110155141.GC11191>