From nobody  Mon Oct 13 23:25:41 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA26100;
          Mon, 13 Oct 1997 23:25:41 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199710140625.XAA26100@hub.freebsd.org>
Date: Mon, 13 Oct 1997 23:25:41 -0700 (PDT)
From: josh@oystersoft.com
To: freebsd-gnats-submit@freebsd.org
Subject: fsuk dumps core
X-Send-Pr-Version: www-1.0

>Number:         4761
>Category:       bin
>Synopsis:       fsuk dumps core
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 13 23:30:00 PDT 1997
>Closed-Date:    Fri Apr 17 11:17:30 PDT 1998
>Last-Modified:  Fri Apr 17 11:18:56 PDT 1998
>Originator:     Joshua Mehlman
>Release:        2.2.2
>Organization:
>Environment:
>Description:
The file system that is bad is /usr so I cant do uname.

I filed up /var ( on the same dive as /usr) so I relocated a 24 meg file 
to a diferent hd (I think that when I did this the file was being written)
then the system hung. when I rebooted I got every indication that I had a head
crash on the /usr disk, with the one glaring exeption that /var was fine
and when I try to fsck I always get a core file
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: steve 
State-Changed-When: Thu Nov 13 18:07:56 PST 1997 
State-Changed-Why:  
Contacted originator and he stated that he still has 
the core file around, so he will try to get some more 
info on where fsck was falling over. 

From: Josh Mehlman <josh@oystersoft.com>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: bin/4761 fsuk dumps core
Date: Fri, 17 Apr 1998 10:19:24 -0700

 I am verry sorry that I have been so long in responding 
 I am not still experiancing that problem beculs western digital wanted
 the hd back whene thaey sent me a new one so I can't reproduce.
 	sorry
 		jb
State-Changed-From-To: feedback->closed 
State-Changed-By: steve 
State-Changed-When: Fri Apr 17 11:17:30 PDT 1998 
State-Changed-Why:  
Originator replaced the drive and is unable to repoduce 
the problem. 
>Unformatted:
