From owner-freebsd-questions  Thu Aug  8 22:50:19 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA13012
          for questions-outgoing; Thu, 8 Aug 1996 22:50:19 -0700 (PDT)
Received: from gdi.uoregon.edu (cisco-ts7-line3.uoregon.edu [128.223.150.50])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA13007
          for <questions@FreeBSD.ORG>; Thu, 8 Aug 1996 22:50:16 -0700 (PDT)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id WAA00232; Thu, 8 Aug 1996 22:49:43 -0700 (PDT)
Date: Thu, 8 Aug 1996 22:49:42 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: dwhite@resnet.uoregon.edu
To: "Amir Y. Rosenblatt" <amir@neuron.net>
cc: questions@FreeBSD.ORG
Subject: Re: [2.1.0] Disk errors
In-Reply-To: <199608082050.QAA26927@prozac.neuron.net>
Message-ID: <Pine.BSI.3.94.960808224738.222A-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 8 Aug 1996, Amir Y. Rosenblatt wrote:

> My office machine, a 486/66, running 2.1.0-RELEASE has been having some
> weird disk problems and before I can get the folks here to reoplace the
> disk, I need to be able to tell them more clearly what sort of errors I'm
> getting.  The following is from /var/log/messages:
> 
> Aug  3 03:30:59 wax /kernel: wd1s1f: hard error reading fsbn 630755 of
> 630752-63
> 0767 (wd1s1 bn 835555; cn 828 tn 14 sn 49)wd1: status 59<seekdone,drq,err>
> error 40<uncorr>
> Aug  3 03:31:28 wax /kernel: wd1s1f: hard error reading fsbn 630755 of
> 630752-63
> 0767 (wd1s1 bn 835555; cn 828 tn 14 sn 49)wd1: status 59<seekdone,drq,err>
> error 40<uncorr>
> 
> I get dozens of these when /etc/daily runs and they happen during the day
> as well, usually causing the disk access ligth to remain on for a couple
> minutes at a time and basically locking up the console X session I'm using
> for that period (I can telnet in fine and with minimal lag, top shows the
> machine as being mostly idle).  Any suggestions or clarifications on what
> the problem is and how to remedy it (I already tried fscking the disk).

I'd say that you've filled up your disk and you're running into the
translated media errors.  At this point, either you'll have to back off
your disk usage or buy a new, larger disk. 

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major