From owner-freebsd-alpha Tue Apr 20 14:19:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C844314CA5 for ; Tue, 20 Apr 1999 14:19:44 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA96297; Tue, 20 Apr 1999 22:22:33 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 22:22:33 +0100 (BST) From: Doug Rabson To: "Alain G. Fabry" Cc: freebsd-alpha@freebsd.org Subject: Re: panic: ffs_valloc: dup alloc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 20 Apr 1999, Alain G. Fabry wrote: > Hello, > > I'm trying to install 3.1-19990326 on my Dec Workstation 200 4/166. > Everything seems to be working fine. I go through the whole installation > process, but at the end of extracting the bin code to the / directory, I > get the following error. > > panic: ffs_valloc: dup alloc > panic > Stopped at Debugger..Ng+0x24: ldq ra.0(sp) > > and then it takes me to the db> > > I also noticed that if I go through a reinstall, it seems to have a > problem creating the partitions on the harddrive since it does not show > the partitions during the reinstall. > I hope this makes sense and can anybody please help me. > TIA That seems unusual for a freshly newfs'ed filesystem. That kind of error normally only appears after an unclean shutdown where there is un-synced data. Were there any other error messages on the console before this happened? Does this happen every time you install? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message