From owner-freebsd-current Tue Dec 16 08:48:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA08603 for current-outgoing; Tue, 16 Dec 1997 08:48:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA08596 for ; Tue, 16 Dec 1997 08:48:30 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id IAA13950; Tue, 16 Dec 1997 08:48:06 -0800 (PST) (envelope-from jdp) Message-Id: <199712161648.IAA13950@austin.polstra.com> To: grog@lemis.com Subject: Re: UFS problems on -current (panic: ffs_alloccg: map corrupted) In-Reply-To: <19971215194623.30917@lemis.com> References: <19971215194623.30917@lemis.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Tue, 16 Dec 1997 08:48:05 -0800 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. Shortly after bringing the system back up, the kernel logged two disk errors (recovered). No errors were logged prior to the panic, though they could have been lost in the crash. 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. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth