From owner-freebsd-hackers Thu Nov 7 14:47:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA24073 for hackers-outgoing; Thu, 7 Nov 1996 14:47:25 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA24045 for ; Thu, 7 Nov 1996 14:47:21 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id FAA16290 for ; Thu, 7 Nov 1996 05:47:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id FAA03394; Thu, 7 Nov 1996 05:45:31 -0800 (PST) Message-Id: <199611071345.FAA03394@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Thomas David Rivers cc: hackers@freebsd.org Subject: Re: More info on the daily panics... In-reply-to: Your message of "Thu, 07 Nov 1996 07:54:29 EST." <199611071254.HAA02561@lakes.water.net> From: David Greenman Reply-To: dg@root.com Date: Thu, 07 Nov 1996 05:45:31 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well - in case you missed it - this fix didn't solve my problem >after all; I just got a panic: ffs_valloc: dup alloc. BTW, this sounds very similar to a problem that Peter Wemm was having when he had a news filesystem made with 4K blocks. I seem to recall that he changed the filesystem to 8K blocks and the problem went away. It appears that there is a bug in the FFS block allocation/free code that is tickled by 4K blocks. Are any of your filesystems built with a 4K blocksize? BTW, your UUCP software re-writes of the email headers into bang-path format is very annoying. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project