From adhir@iagi.net  Tue Feb 14 06:41:28 1995
Received: from bigdipper.iagi.net (bigdipper.iagi.net [198.6.14.10]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA26178 for <FreeBSD-gnats-submit@freebsd.org>; Tue, 14 Feb 1995 06:41:28 -0800
Received: from littledipper.iagi.net (littledipper.iagi.net [198.6.14.11]) by bigdipper.iagi.net (8.6.8/8.6.6) with ESMTP id JAA23528 for <FreeBSD-gnats-submit@freebsd.org>; Tue, 14 Feb 1995 09:41:22 -0500
Received: (from adhir@localhost) by littledipper.iagi.net (8.6.9/8.6.9) id JAA08240; Tue, 14 Feb 1995 09:41:21 -0500
Message-Id: <199502141441.JAA08240@littledipper.iagi.net>
Date: Tue, 14 Feb 1995 09:41:21 -0500
From: "Alok K. Dhir" <adhir@iagi.net>
Reply-To: adhir@iagi.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: /kernel: panic: ffs_alloccg: map corrupted
X-Send-Pr-Version: 3.2

>Number:         216
>Category:       kern
>Synopsis:       /kernel: panic: ffs_alloccg: map corrupted
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    davidg
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 14 06:50:01 1995
>Closed-Date:    Sat Apr 11 03:37:00 PDT 1998
>Last-Modified:  Sat Apr 11 03:37:35 PDT 1998
>Originator:     Alok K. Dhir
>Release:        FreeBSD 2.1.0-Development i386
>Organization:
Internet Access Group, Inc.
>Environment:

Running FreeBSD-current (supped and built 2/11/95 from freefall.cdrom.com) 
on ASUS SP3G board (486/66, 32mb ram).  Using onboard NCR PCI SCSI and two 
SCSI disks - DEC 1 gig and Seagate Hawk 4 gig.

>Description:

This machine is our news server and during the expire run last night, the 
kernel paniced with the message in the "synopsis" section above, and rebooted
itself.  The machine came up OK though...

I have split news into two partitions, news1 and news2.  News1 contains the
comp, alt, and misc hierarchies, and news2 has everything else, with symlinks
to /news1/comp, etc.  We're running INND1.4 and have had few problems with
this machine until now.

Here are the relevant lines...

Feb 14 03:42:07 littledipper /kernel: start = 0, len = 2536, fs = /news1 
Feb 14 03:42:07 littledipper /kernel: panic: ffs_alloccg: map corrupted
Feb 14 03:42:07 littledipper /kernel: 
Feb 14 03:42:07 littledipper /kernel: syncing disks... [...]
Feb 14 03:42:07 littledipper /kernel: Automatic Reboot in 15 sec [...]
Feb 14 03:42:07 littledipper /kernel: Rebooting...

>How-To-Repeat:

Dono...

>Fix:
	
Dono...
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->davidg 
Responsible-Changed-By: pst 
Responsible-Changed-When: Wed Feb 7 15:39:00 PST 1996 
Responsible-Changed-Why:  
State-Changed-From-To: open->closed 
State-Changed-By: scrappy 
State-Changed-When: Fri Apr 5 12:02:12 PST 1996 
State-Changed-Why:  

Confirmed with submitter that problem no longer exists 
State-Changed-From-To: closed->open 
State-Changed-By: peter 
State-Changed-When: Sun Jul 21 07:02:09 PDT 1996 
State-Changed-Why:  

I've reopened this PR rather than submit a new duplicate, This is the 
same problem that I've been having that's been crashing our news server 
every few days for the last few months (and possibly longer). 

Like the original report, it's on a lowly 486-66, but with 48M of ram and 
an AHA-1542CP scsi controller.  It's with a 1G and a little over 2G spool 
drive. Running -current.

On a few occasions, fsck has not been able to repair the filesystem, and 
it's recently been newfs'ed in case there was hidden corruption. 

From: Dave Littell <dlittell@iphase.com>
To: freebsd-gnats-submit@freebsd.org, adhir@iagi.net
Cc:  Subject: Re: kern/216: /kernel: panic: ffs_alloccg: map corrupted
Date: Mon, 24 Feb 1997 16:27:33 -0600

 We've found that completely filling a filesystem on a SCSI ZIP drive
 will panic in the same manner.  This is with 2.1.6.1.

From: Robert Dick <rdick@junction.net>
To: freebsd-gnats-submit@freebsd.org, dlittell@iphase.com
Cc:  Subject: Re: kern/216: /kernel: panic: ffs_alloccg: map corrupted
Date: Sun, 11 Jan 1998 14:49:44 -0800

 I have the same problem happening on the ATTEMPTED installation of
 FreeBSD 2.2.5 on a Pentium 166MMX system (MTech M539 motherboard, 32MB
 SDRAM, Panasonic 24X cdrom (IDE), Quantum 2.1GB Fireball (IDE), 3Com
 5C905XL PCI NIC).
 
 No matter how I lay out the drive I get the panic during the system
 installation.  It makes no difference if I have a DOS partition or not,
 nor does it make a difference if I try the install from DOS or direct
 boot from the CDROM.
 
 Anyone have any ideas?
 
 Robert
 
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Sat Apr 11 03:37:00 PDT 1998 
State-Changed-Why:  
dead PR. 
>Unformatted:


