Date: Wed, 17 Jun 2009 04:00:05 GMT From: freebsdpr <freebsdpr@satin.sensation.net.au> To: freebsd-amd64@FreeBSD.org Subject: Re: amd64/133977: [panic] [ffs] "panic: ffs_blkfree: freeing free block" after 7.0R->7.1R amd64 src upgrade [regression] Message-ID: <200906170400.n5H40588013039@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR amd64/133977; it has been noted by GNATS. From: freebsdpr <freebsdpr@satin.sensation.net.au> To: bug-followup@FreeBSD.org, freebsdpr@sensation.net.au Cc: Subject: Re: amd64/133977: [panic] [ffs] "panic: ffs_blkfree: freeing free block" after 7.0R->7.1R amd64 src upgrade [regression] Date: Wed, 17 Jun 2009 13:27:20 +1000 (EST) I am also seeing this behaviour on a machine with 7.2-RELEASE (i386) installed. A tech powered off the machine to replace a HD, rather than cleanly shutting it down, so it now appears to be stuck in a reboot - fsck - panic cycle. The file system has a lot of small files (at least a few million) so fsck takes considerable time; I presume the sheer number of blocks fsck is fixing/updating is eventually causing the panic. From vmcore.0: dev = mirror/gm0s1e, block = 424638984, fs = /var panic: ffs_blkfree: freeing free block df -ik: Filesystem 1024-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/mirror/gm0s1e 933330372 490280876 368383068 57% 10280264 110353078 9% /var At this stage there seems to be no option but to disable soft updates for any 7.1+ machine with a large (lots of files and/or large capacity + large occupied capacity) file system...? I can't find any bug fix, but perhaps I'm looking in the wrong places. Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906170400.n5H40588013039>