From owner-freebsd-questions@FreeBSD.ORG Mon Nov 10 07:48:01 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0682716A4CE for ; Mon, 10 Nov 2003 07:48:01 -0800 (PST) Received: from lakemtao04.cox.net (lakemtao04.cox.net [68.1.17.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id E789943FB1 for ; Mon, 10 Nov 2003 07:47:59 -0800 (PST) (envelope-from jwm@sentinelchicken.net) Received: from sentinelchicken.net ([68.226.91.117]) by lakemtao04.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20031110154759.SATY19895.lakemtao04.cox.net@sentinelchicken.net> for ; Mon, 10 Nov 2003 10:47:59 -0500 Received: (qmail 82598 invoked by uid 1000); 10 Nov 2003 15:51:42 -0000 Date: Mon, 10 Nov 2003 10:51:42 -0500 From: Jason Morgan To: freebsd-questions@freebsd.org Message-ID: <20031110155141.GC11191@sentinelchicken.net> References: <20031109203729.GA11191@sentinelchicken.net> <20031109212858.GB99275@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031109212858.GB99275@xor.obsecurity.org> User-Agent: Mutt/1.4.1i Subject: Re: 5.1 RELEASE - Panic X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2003 15:48:01 -0000 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.