From owner-freebsd-stable Thu Dec 21 13:51:28 2000 From owner-freebsd-stable@FreeBSD.ORG Thu Dec 21 13:51:26 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id A1AB037B402 for ; Thu, 21 Dec 2000 13:51:25 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id eBLLp2E45376 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Thu, 21 Dec 2000 15:51:08 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <00e901c06b98$2059c910$524c8486@jking> From: "Jim King" To: "Geoffrey Crompton (RMIT Guest)" , "FreeBSD-Stable" References: <20001222084607.A8159@gecko.eric.net.au> Subject: Re: hard read error Date: Thu, 21 Dec 2000 15:51:02 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Geoffrey Crompton (RMIT Guest)" wrote: > I know this issue has come up before. I'm getting hard read errors, > both in 4.1.1 and 4.2. However, it seems there are alot less of them > in 4.2 > I have noticed that now, it basically only occurs during one of the > 2am daily periodic scripts. I don't know which one is triggering this > error, I suspect it would be the updateing of the locate database. > > However, each morning I have about 12 error messages, and over 90% > of them are: > > ad0: HARD READ ERROR blk# 14484670 status=59 error=40 > > Can anyone tell me if there is away to work out which file is sitting > on this block? And also what do the status and error numbers indicate? fwiw, I was getting similar errors under 4.2-stable on an old Conner 1 GB drive. Going back to 4.1.1-RELEASE made the error messages disappear. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message