From owner-freebsd-hackers Wed Feb 19 05:20:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA21953 for hackers-outgoing; Wed, 19 Feb 1997 05:20:46 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA21943 for ; Wed, 19 Feb 1997 05:20:43 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA27710; Wed, 19 Feb 1997 08:20:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 19 Feb 1997 08:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id IAA00233; Wed, 19 Feb 1997 08:09:14 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id IAA27926; Wed, 19 Feb 1997 08:14:08 -0500 (EST) Date: Wed, 19 Feb 1997 08:14:08 -0500 (EST) From: Thomas David Rivers Message-Id: <199702191314.IAA27926@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: another dup alloc panic. Cc: ponds!root.com!dg Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just F.Y.I. - my news server (a 386-dx; 8meg, IDE) machine has now re-entered the daily dup-alloc panic... Given the information I was able to discern from my test machine (a 386-dx; 8meg SCSI (aha1542B)) - after yesterday's panic, I had simply cleared the offending inode (inode #270680, in this case). Thinking that it had not been newfs'd properly and contained trash. This morning's panic was inode #177593. (Certainly doesn't seem to be one that would fall on any inodes/group boundary) I'll clear that one and hope for the best. However, when I did the fsck on that file system; two files were associated with that inode - so, it probably was, in fact, already allocated... Maybe the allocation structure is sorta messed up and it's picking up random bits somewhere... I'm beginning to believe some randomness (along the lines of an uninitilized variable) is part of the problem here... - Dave Rivers -