From owner-freebsd-stable Fri Nov 22 01:44:38 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA09119 for stable-outgoing; Fri, 22 Nov 1996 01:44:38 -0800 (PST) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA09100; Fri, 22 Nov 1996 01:44:27 -0800 (PST) Received: (from guido@localhost) by gvr.win.tue.nl (8.8.2 with smtp patch/8.8.2) id KAA16976; Fri, 22 Nov 1996 10:43:53 +0100 (MET) From: Guido van Rooij Message-Id: <199611220943.KAA16976@gvr.win.tue.nl> Subject: Re: panic: ffs_valloc: dup alloc In-Reply-To: <199611220033.TAA21459@orion.webspan.net> from Gary Palmer at "Nov 21, 96 07:33:26 pm" To: gpalmer@FreeBSD.org (Gary Palmer) Date: Fri, 22 Nov 1996 10:43:53 +0100 (MET) Cc: ponds!rivers@dg-rtp.dg.com, freebsd-stable@freefall.freebsd.org, freebsd-hackers@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Question: > > it's always the same FS with me that bites the dust. Perhaps a > previous crash of the machine caused a FS corruption fsck isn't > picking up on. Has anyone who is being bothered by this dumped the fs > with *tar* (not dump) and resored to see if that fixes the problem? > I might have ased this already, but you do run the latest fsck, including a patch I installed the other day? Further if it is an FS problem, a tar won't help. The dump would. -Guido