Date: Wed, 17 Dec 1997 17:05:38 +1030 From: Mike Smith <mike@smith.net.au> To: sclawson@bottles.cs.utah.edu (steve clawson) Cc: ivt@gamma.ru (Igor Timkin), tlambert@primenet.com, freebsd-hackers@freebsd.org Subject: Re: panic: blkfree: freeling free block/frag Message-ID: <199712170635.RAA01913@word.smith.net.au> In-Reply-To: Your message of "Tue, 16 Dec 1997 22:13:01 PDT." <199712170513.WAA03545@bottles.cs.utah.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> I've been getting ``freeing free block'' panics fairly often when > our main server is doing a bunch of large compiles. A couple weeks > ago I finally caught it in the act. One of my compiles died and I > found a source file with exactly 8k of gunk, sitting nicely on an 8k > boundary (this was on an 8k/1k filesystem). The interesting thing > about the file was it's list of direct blocks: > > 0: 179bb8 > 1: 179bc0 > 2: 179bc8 > 3: 179bd0 > 4: 179bd8 > 5: 79be0 > 6: 179be8 > 7: 0 > > 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... mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712170635.RAA01913>