Date: Mon, 25 Apr 2011 17:34:30 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-fs@freebsd.org Subject: Re: panic: ext2fs_alloccg: map corrupted Message-ID: <201104251734.30284.jhb@freebsd.org> In-Reply-To: <4DB5CF3C.9030002@FreeBSD.org> References: <4DB5CF3C.9030002@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, April 25, 2011 3:45:00 pm Doug Barton wrote: > I got the following panic on 9-current, r216869, amd64 SMP on a core 2 > duo system. I'm running the older version (from 2011-01-01) to try and > determine where the problem I'm having with stability on -current first > occurred. If this problem was fixed between now and then, no worries. > > This panic happened during heavy disk activity on the ext2fs partition. > The file core.txt.0.216869 is in my home directory on freefall if anyone > wants to take a look. This looks like the panic that you reported earlier (and tested the fix for IIRC). The fix was comitted in 218438: ------------------------------------------------------------------------ r218438 | jhb | 2011-02-08 08:02:25 -0500 (Tue, 08 Feb 2011) | 6 lines After reading a bitmap block for i-nodes or blocks, recheck the count of free i-nodes or blocks to handle a race where another thread might have allocated the last i-node or block while we were waiting for the buffer. Tested by: dougb -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201104251734.30284.jhb>