From owner-freebsd-hackers Thu Dec 18 20:11:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA19333 for hackers-outgoing; Thu, 18 Dec 1997 20:11:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA19320 for ; Thu, 18 Dec 1997 20:11:00 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA25416; Thu, 18 Dec 1997 20:10:05 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd025414; Thu Dec 18 20:10:01 1997 Message-ID: <3499F2F4.3F54BC7E@whistle.com> Date: Thu, 18 Dec 1997 20:07:16 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: steve clawson CC: Terry Lambert , mike@smith.net.au, ivt@gamma.ru, freebsd-hackers@FreeBSD.ORG Subject: Re: panic: blkfree: freeling free block/frag References: <199712190321.UAA18957@bottles.cs.utah.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk we just solved the problem terry was seeing. if you are not using ipfw that aint it... julian steve clawson wrote: > > Terry Lambert uttered: > > > > All nicely clustered...except for that sixth one. At first I > > > > thought that the clustering code was at fault, but disk block 79be0 > > > > was untouched, and the `real' disk block (179be0) had the correct data > > > > for the new file. So, the list of blocks in the inode was corrupted > > > > sometime after the data blocks for the file were written. > > > > > > Single-bit memory error, perhaps? Still, keep an eye on it... > > > > If this panic'ed, you need to look at the stack. I would prefer you look > > at the stack for #5. > > I don't have a crash dump of it, since I found the affected files > before someone decided to try and delete them and panic the system. > Not that it would have helped much in this case, since the corruption > happened long before the panic. Basically the problem I'm seeing > leaves these time bombs sitting in the filesystem for you. =( > > > I do not believe this is a single bit error. I believe this is the same > > problem I have been seeing. > > > > Does your ethernet hardware address begin with 00 00? > > Yes. The machine has 3 active ether cards, all of which have > hardware addresses that begin with 00 00. > > > steve > > -- > // stephen clawson sclawson@cs.utah.edu > // university of utah