Date: Mon, 25 Apr 2011 14:45:00 -0700 From: Doug Barton <dougb@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: panic: ext2fs_alloccg: map corrupted Message-ID: <4DB5EB5C.6040906@FreeBSD.org> In-Reply-To: <201104251734.30284.jhb@freebsd.org> References: <4DB5CF3C.9030002@FreeBSD.org> <201104251734.30284.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/25/2011 14:34, John Baldwin wrote: > 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: Yeah, I thought it looked familiar. :-/ Sorry for not digging into it deeper myself before reporting, and thanks for looking into it. I'm having massive problems with -current atm, and I'm trying to do a binary search to find out when they started in the middle of also trying to get $REALWORK done. Since I was just able to trigger the problem I'm seeing without heavy access on my ext2fs partition, I'm thinking that what I might do is back all of my sources up to the point in the binary search that I'm testing but then 'cd /sys/fs/ext2fs && svn up', does that sound safe? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DB5EB5C.6040906>