From owner-freebsd-current Tue Dec 16 14:03:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA04118 for current-outgoing; Tue, 16 Dec 1997 14:03:47 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA04045 for ; Tue, 16 Dec 1997 14:03:28 -0800 (PST) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id IAA26973; Wed, 17 Dec 1997 08:33:12 +1030 (CST) (envelope-from grog) Message-ID: <19971217083312.13948@lemis.com> Date: Wed, 17 Dec 1997 08:33:12 +1030 From: Greg Lehey To: John Polstra Cc: current@freebsd.org Subject: Re: UFS problems on -current (panic: ffs_alloccg: map corrupted) References: <19971215194623.30917@lemis.com> <199712161648.IAA13950@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199712161648.IAA13950@austin.polstra.com>; from John Polstra on Tue, Dec 16, 1997 at 08:48:05AM -0800 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Dec 16, 1997 at 08:48:05AM -0800, John Polstra wrote: > In article <19971215194623.30917@lemis.com>, > Greg Lehey wrote: >> I've been having a large number of these panics in the last few days >> after replacing significant parts of my system. In each case, the >> system appears to die when writing a large file (the text of "The >> Complete FreeBSD", about 40 MB). > > I had that same panic a few days ago on a 2.2-stable machine. If I > remember correctly, it happened during an open(2) call when spooling > an incoming mail file. In my case, they occurred during write() calls. > I don't know whether there was any connection between the disk errors > and the panic. It doesn't seem like a disk error should cause this > kind of panic. Agreed. It's beginning to look like my problem is hardware after all. I removed the SDRAMs and ran with only 64 MB, and all is fine, despite more work than usual yesterday. Greg