Date: Tue, 20 Apr 1999 22:22:33 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: "Alain G. Fabry" <fabry@coserve.org> Cc: freebsd-alpha@freebsd.org Subject: Re: panic: ffs_valloc: dup alloc Message-ID: <Pine.BSF.4.05.9904202219320.85882-100000@herring.nlsystems.com> In-Reply-To: <Pine.BSF.4.01.9904200758240.9195-100000@3rdrock.coserve.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9904202219320.85882-100000>