From root@nfs-2.aros.net  Thu Jul 10 14:53:22 1997
Received: from nfs-2.aros.net ([208.219.16.47])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA00905
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 10 Jul 1997 14:53:21 -0700 (PDT)
Received: (from root@localhost)
	by nfs-2.aros.net (8.8.5/8.8.5) id PAA00272;
	Thu, 10 Jul 1997 15:53:02 -0600 (MDT)
Message-Id: <199707102153.PAA00272@nfs-2.aros.net>
Date: Thu, 10 Jul 1997 15:53:02 -0600 (MDT)
From: sys@aros.net
Reply-To: sys@aros.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: kern
X-Send-Pr-Version: 3.2

>Number:         4074
>Category:       kern
>Synopsis:       Kernel panics when accessing a ccd device
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul 10 15:00:01 PDT 1997
>Closed-Date:    Mon May 4 03:57:44 PDT 1998
>Last-Modified:  Mon May  4 03:58:17 PDT 1998
>Originator:     Steve Sawaya
>Release:        FreeBSD 2.2.2-RELEASE i386
>Organization:
ArosNET 
>Environment:

	

>Description:
       
We're using a damaged disk, mounted r/o as part of a CCD.  When we
try to access certain directories on the CCD, it causes a kernel panic.
This one was found when accessing it over NFS:

Fatal Trap 18:  integer divide fault while in kernel mode
processor eflags     = interrupt enabled, resume, IOPL = 0
current process      = 161 (nfsd)
interrupt mask       = bio
panic: integer divide fault

An nm of the kernel shows that this panic was between ccdclose and ccddump,
occuring at IP = 0x8:0xf0101493

Using stock 2.2.2-RELEASE off of a CD-ROM with two ccd devices configured in 
to the kernel.  There are 4 drives in the RAID, one of which has a very
corrupted directory tree (which can't survive an fsck).  However, .. 
it doesn't seem like this should cause a kernel panic. :)

>How-To-Repeat:

Performing a 'du' in one of the corrupted directories on this drive
will cause the problem to recur.

>Fix:
	
That's what we need. :)
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: gpalmer 
Responsible-Changed-When: Mon Jul 14 15:50:29 PDT 1997 
Responsible-Changed-Why:  
Mis-filed PR 
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Mon May 4 03:57:44 PDT 1998 
State-Changed-Why:  
timed out.  Nobody jumped on this one, and I bet the disk in question 
isn't available anymore. 
>Unformatted:
